[yocto] menuconfig vs. config fragments?

[Jack Mitchell]

On 09/07/12 11:42, Andrei Gherzan wrote:
> On Mon, Jul 9, 2012 at 1:39 PM, James Abernathy <jfabernathy at gmail.com 
> <mailto: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.
>
> @g
>
>
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

I agree, something in the back of my mind is shouting that config 
fragments should have a .cfg extension.

Regards,

-- 

   Jack Mitchell (jack at embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--