[yocto] menuconfig vs. config fragments?

[Bruce Ashfield]

On Mon, Jul 9, 2012 at 6:42 AM, Andrei Gherzan <andrei at gherzan.ro> wrote:
> On Mon, Jul 9, 2012 at 1:39 PM, James Abernathy <jfabernathy at gmail.com>
> wrote:
>>
>> my goal of this test was to see if I could use the n450 BSP as a starting
>> point for a BSP to support my Acer Aspire One n450 based netbook.  The
>> core-image-sato will boot from USB key on the netbook if I use the ZIP drive
>> format for the USB key, but the current n450 BSP doesn't include the drivers
>> for the networking hardware in the netbook.
>>
>> I found by testing, using the menuconfig option documented in the
>> Developer Manual Appendix B example, that I needed to add 2 parameters to
>> the .config:
>>
>> CONFIG_ATH9K_PCI
>> CONFIG_ATL1C
>>
>> To make this change easier to manage and more permanent, I thought about
>> creating a config fragment.  I put the config parameters in a file,
>> myconfig, in the linux-yocto directory at the same level as the
>> linux-yocto_3.2.bbappend file, where I added:
>>
>> SRC_URI += "file//myconfig"
>>
>
> Try to use myconfig.cfg.

This would be the key part, since as a few noted, .cfg is what
triggers the fragment
processing to actually notice the file and stack it after the base /
defined configuration.

Cheers,

Bruce

>
> @g
>
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"