Re: [yocto] [kernel config]: specified values did not make it into the kernel's final configuration

2015-04-04 Thread Bruce Ashfield
On Fri, Apr 3, 2015 at 4:34 PM, Liam Maps cca_liam_m...@mail.com wrote: Hi, During the build of a core-image-base for BeagleBone using the master branch I was presented with the following warning: WARNING: [kernel config]: specified values did not make it into the kernel's final

Re: [yocto] [kernel config]: specified values did not make it into the kernel's final configuration

2015-04-04 Thread Liam Maps
Thank you for the info. But who sets the .config Requested value of a configuration variable and who then overrides it and sets the Actual value set? (The quoted text is from the [kernel config] warning.) After a bit of research this is what I think I know: For my example when working with the

Re: [yocto] [kernel config]: specified values did not make it into the kernel's final configuration

2015-04-04 Thread Bruce Ashfield
On Sat, Apr 4, 2015 at 3:55 PM, Liam Maps cca_liam_m...@mail.com wrote: Thank you for the info. But who sets the .config Requested value of a configuration variable and who then overrides it and sets the Actual value set? (The quoted text is from the [kernel config] warning.) The kernel

[yocto] [kernel config]: specified values did not make it into the kernel's final configuration

2015-04-03 Thread Liam Maps
Hi, During the build of a core-image-base for BeagleBone using the master branch I was presented with the following warning: WARNING: [kernel config]: specified values did not make it into the kernel's final configuration: The full list of configuration values, which did not make it into