kernel-localversion, removing custom def configs, with linux-boundary #yocto #compilation #meta-freescale


Daniel Cox
 

Thank you for your efforts, 

The latest commit has resolved the issue.


Otavio Salvador
 

Hello,

Em sex., 16 de abr. de 2021 às 09:55, <daniel.cox@cranepi.com> escreveu:
We have seen an issue in a recent update to the dunfell branch.
Our image uses the linux-boundary, which requires the linux-imx.inc files.

What we have found thought with the latest dunfull branch. the changes made in commit. d6cb0a63d1a77da21e7f9cb7ca6561371b3fc896

Have caused custom configuration fragments to no longer be applied, these have been places in the linux-boundary bbappend file, as described in section 2.3.3 of the Kernel Development Manual.

We would like to understand if we are doing something wrong, or is there an issue with the aforementioned commit.
Reported here https://github.com/Freescale/meta-freescale/issues/733


--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750


Daniel Cox
 

Hi, 

We have seen an issue in a recent update to the dunfell branch.
Our image uses the linux-boundary, which requires the linux-imx.inc files. 

What we have found thought with the latest dunfull branch. the changes made in commit. d6cb0a63d1a77da21e7f9cb7ca6561371b3fc896 

Have caused custom configuration fragments to no longer be applied, these have been places in the linux-boundary bbappend file, as described in section 2.3.3 of the Kernel Development Manual. 

We would like to understand if we are doing something wrong, or is there an issue with the aforementioned commit.

Regards