meta-freescale.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
* kernel-localversion, removing custom def configs, with linux-boundary #meta-freescale #compilation #yocto
@ 2021-04-16 12:55 daniel.cox
  2021-04-17  0:55 ` [meta-freescale] " Otavio Salvador
  0 siblings, 1 reply; 3+ messages in thread
From: daniel.cox @ 2021-04-16 12:55 UTC (permalink / raw)
  To: meta-freescale

[-- Attachment #1: Type: text/plain, Size: 602 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 825 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [meta-freescale] kernel-localversion, removing custom def configs, with linux-boundary #meta-freescale #compilation #yocto
  2021-04-16 12:55 kernel-localversion, removing custom def configs, with linux-boundary #meta-freescale #compilation #yocto daniel.cox
@ 2021-04-17  0:55 ` Otavio Salvador
  2021-04-18 11:16   ` daniel.cox
  0 siblings, 1 reply; 3+ messages in thread
From: Otavio Salvador @ 2021-04-17  0:55 UTC (permalink / raw)
  To: daniel.cox; +Cc: meta-freescale

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: kernel-localversion, removing custom def configs, with linux-boundary #meta-freescale #compilation #yocto
  2021-04-17  0:55 ` [meta-freescale] " Otavio Salvador
@ 2021-04-18 11:16   ` daniel.cox
  0 siblings, 0 replies; 3+ messages in thread
From: daniel.cox @ 2021-04-18 11:16 UTC (permalink / raw)
  To: meta-freescale

[-- Attachment #1: Type: text/plain, Size: 74 bytes --]

Thank you for your efforts,

The latest commit has resolved the issue.

[-- Attachment #2: Type: text/html, Size: 88 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-04-18 11:16 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-16 12:55 kernel-localversion, removing custom def configs, with linux-boundary #meta-freescale #compilation #yocto daniel.cox
2021-04-17  0:55 ` [meta-freescale] " Otavio Salvador
2021-04-18 11:16   ` daniel.cox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).