In a preemptive attempt to stay up-to-date, we tried pulling kirkstone-next into our build and noticed 8ee32b7 breaks it. We can mask the append, but does this need to be in the board-support layer at all? Can it go into a distro or software-compatibility layer instead?
Hi,
In a preemptive attempt to stay up-to-date, we tried pulling
kirkstone-next
into our build and noticed8ee32b7
breaks it. We can mask the append, but does this need to be in the board-support layer at all? Can it go into a distro or software-compatibility layer instead?Thanks, Logan