From: Jack Mitchell <ml@communistcode.co.uk>
To: yocto@yoctoproject.org
Subject: Re: menuconfig vs. config fragments?
Date: Mon, 09 Jul 2012 12:12:02 +0100 [thread overview]
Message-ID: <4FFABC82.8080601@communistcode.co.uk> (raw)
In-Reply-To: <CAK18fxGJzFanh5UY-nrj_hVReCGeGSVv5c7=PaH_KRXhZ2BNwA@mail.gmail.com>
On 09/07/12 11:42, Andrei Gherzan wrote:
> On Mon, Jul 9, 2012 at 1:39 PM, James Abernathy <jfabernathy@gmail.com
> <mailto:jfabernathy@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@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@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next prev parent reply other threads:[~2012-07-09 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 10:39 menuconfig vs. config fragments? James Abernathy
2012-07-09 10:42 ` Andrei Gherzan
2012-07-09 11:12 ` Jack Mitchell [this message]
2012-07-09 12:07 ` Bruce Ashfield
2012-07-09 12:13 ` James Abernathy
2012-07-09 12:52 ` James Abernathy
2012-07-12 15:04 ` Rifenbark, Scott M
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FFABC82.8080601@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.