menuconfig vs. config fragments?

menuconfig vs. config fragments?

[James Abernathy]

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"

I can see from the tmp/work directory that bitbake found my myconfig file and copied it over, but the .config file used in the building of the kernel didn't have the parameters listed and obviously, the drivers didn't make it.

Is there something else to do to get these config parameters included as config fragments?  Is there some tool reviewing the config parameters and throwing my 2 out for some reason?  

The only way I've gotten this to work is with the bitbake linux-yocto -c menuconfig command and manually adding the parameters.

Jim A

Re: menuconfig vs. config fragments?

[Andrei Gherzan]

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

On Mon, Jul 9, 2012 at 1:39 PM, James Abernathy <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

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

Re: 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@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

--

Re: menuconfig vs. config fragments?

[Bruce Ashfield]

On Mon, Jul 9, 2012 at 6:42 AM, Andrei Gherzan <andrei@gherzan.ro> wrote:
> On Mon, Jul 9, 2012 at 1:39 PM, James Abernathy <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.

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@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



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

Re: menuconfig vs. config fragments?

[James Abernathy]

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

On Mon, Jul 9, 2012 at 8:07 AM, Bruce Ashfield <bruce.ashfield@gmail.com>wrote:

> On Mon, Jul 9, 2012 at 6:42 AM, Andrei Gherzan <andrei@gherzan.ro> wrote:
> > On Mon, Jul 9, 2012 at 1:39 PM, James Abernathy <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.
>
> 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
>
> I'm testing it now, but it sound like the problem.  So the Developer
Manual uses the .cfg in the example, but the BSP Guide does not.  That's an
area to fix.  Since this is critical,it needs to be pointed out, in my mind.

JIm A

>
> > @g
> >
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
>

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

Re: menuconfig vs. config fragments?

[James Abernathy]

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

On Mon, Jul 9, 2012 at 8:13 AM, James Abernathy <jfabernathy@gmail.com>wrote:

>
>
> On Mon, Jul 9, 2012 at 8:07 AM, Bruce Ashfield <bruce.ashfield@gmail.com>wrote:
>
>> On Mon, Jul 9, 2012 at 6:42 AM, Andrei Gherzan <andrei@gherzan.ro> wrote:
>> > On Mon, Jul 9, 2012 at 1:39 PM, James Abernathy <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.
>>
>> 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
>>
>> I'm testing it now, but it sound like the problem.  So the Developer
> Manual uses the .cfg in the example, but the BSP Guide does not.  That's an
> area to fix.  Since this is critical,it needs to be pointed out, in my mind.
>
> JIm A
>
> Adding the .cfg extension does indeed fix my problem. Thanks for the help.

Jim A



> >
>> > @g
>> >
>> > _______________________________________________
>> > yocto mailing list
>> > yocto@yoctoproject.org
>> > https://lists.yoctoproject.org/listinfo/yocto
>> >
>>
>>
>>
>> --
>> "Thou shalt not follow the NULL pointer, for chaos and madness await
>> thee at its end"
>>
>
>

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

Re: menuconfig vs. config fragments?

[Rifenbark, Scott M]

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

Jim,

This needs to be fixed in the BSP Guide.  I will handle that.

Thanks,
Scott

From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of James Abernathy
Sent: Monday, July 09, 2012 5:52 AM
To: Bruce Ashfield
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] menuconfig vs. config fragments?


On Mon, Jul 9, 2012 at 8:13 AM, James Abernathy <jfabernathy@gmail.com<mailto:jfabernathy@gmail.com>> wrote:

On Mon, Jul 9, 2012 at 8:07 AM, Bruce Ashfield <bruce.ashfield@gmail.com<mailto:bruce.ashfield@gmail.com>> wrote:
On Mon, Jul 9, 2012 at 6:42 AM, Andrei Gherzan <andrei@gherzan.ro<mailto:andrei@gherzan.ro>> 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.
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

I'm testing it now, but it sound like the problem.  So the Developer Manual uses the .cfg in the example, but the BSP Guide does not.  That's an area to fix.  Since this is critical,it needs to be pointed out, in my mind.

JIm A
Adding the .cfg extension does indeed fix my problem. Thanks for the help.

Jim A


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


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



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