All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Adami <andrea.adami@gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Rudolf Streif <rstreif@linuxfoundation.org>
Subject: Re: Custom defconfig is not used
Date: Thu, 17 Oct 2013 15:51:35 +0200	[thread overview]
Message-ID: <CAAQYJAtzSheOwBecK+SqgnRFQd8Uhq4RZHhEi855fVurirjOZQ@mail.gmail.com> (raw)
In-Reply-To: <525FE3C9.3070003@windriver.com>

On Thu, Oct 17, 2013 at 3:19 PM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> On 13-10-17 09:15 AM, Diego Sueiro wrote:
>>
>>
>> 2013/10/17 Bruce Ashfield <bruce.ashfield@windriver.com
>> <mailto:bruce.ashfield@windriver.com>>
>>
>>
>>
>>
>>         I expected to get this working "out-of-box".
>>
>>
>>     Did you do a  "bitbake -e <your kernel recipe>" ? and then look at
>>     the SRC_URI ? That will tell us if for some reason the beagle layer's
>>     defconfig is on there twice.
>>
>> I'll do it after my current build gets finished.
>>
>>
>>
>>         Why config fragments did not worked too?
>>
>>
>>     recipes must inherit linux-yocto to get that support, since it is
>>     optional and not something we force on all kernel recipes. So if you
>>     want fragment support, creating your own kernel recipe, based on the
>>     one in the layers you are using, which inherits linux-yocto is one
>>     route to take.
>>
>> Can I do it on bbappend, or do I need to copy the entirely
>> linux-mainline_3.8.bb <http://linux-mainline_3.8.bb> from
>>
>> meta-bleagleboard to my layer and add "inherit linux-yocto"?
>> Do I need to "inherit linux-yocto", "require
>> recipes-kernel/linux/linux-yocto.inc" or "inherit kernel-yocto"?
>
>
> Look at oe-core/meta-skeleton for the custom kernel recipe example.
> It has the inherit/include combinations that you need to follow.
>
>
>> My concern is: if doing this to just have the config fragment feature,
>> I'll possibly mess up the kernel build.
>
>
> It shouldn't. It only adds to existing phases, and doesn't make
> any changes. I've tested it in many combinations and it should
> work fine.
>
> If something breaks, I'd like to know, so we can fix it.
>
> Bruce
>
>
>>
>>
>> Regards,
>>
>> --
>> *dS
>> Diego Sueiro
>>
>> /*long live rock 'n roll*/
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

As a final note, the defconfig is overwritten by the
do_configure_prepend() code in linux.inc.
This is how kernel recipes did work before linux-yocto.

Cheers

Andrea


  reply	other threads:[~2013-10-17 13:51 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 21:07 Custom defconfig is not used Diego Sueiro
2013-10-15 21:29 ` Katu Txakur
2013-10-15 21:49 ` Rudolf Streif
2013-10-15 21:55   ` Andrea Adami
2013-10-16 17:25     ` Diego Sueiro
2013-10-16 18:19       ` Diego Sueiro
2013-10-17  3:56         ` Bruce Ashfield
2013-10-17 10:39           ` Diego Sueiro
2013-10-17 12:50             ` Bruce Ashfield
2013-10-17 13:15               ` Diego Sueiro
2013-10-17 13:19                 ` Bruce Ashfield
2013-10-17 13:51                   ` Andrea Adami [this message]
2013-10-17 15:47                   ` Diego Sueiro
2013-10-18  4:48                     ` Bruce Ashfield
2013-10-18  9:17                       ` Diego Sueiro
2013-10-18 20:17                         ` Bruce Ashfield
2013-10-22 16:23                           ` Mike Lewis
2013-10-22 22:10                             ` Bruce Ashfield
2013-10-24  0:17                             ` Bruce Ashfield
2013-10-25 11:43                               ` Diego Sueiro
2013-10-25 18:44                                 ` Bruce Ashfield
2013-10-26  1:19                                   ` Mike Lewis
2013-10-26 10:57                                     ` Diego Sueiro
2013-10-26 14:54                                       ` Bruce Ashfield
2013-10-28 20:58                                       ` Bruce Ashfield
2013-10-28 21:41                                         ` Mike Lewis
2013-10-29 10:33                                         ` Diego Sueiro
2013-10-29 11:00                                           ` Andrea Adami
2013-10-29 14:55                                             ` Diego Sueiro
2013-10-29 15:31                                               ` Diego Sueiro
2013-10-30 13:04                                                 ` Bruce Ashfield
2013-10-30 13:54                                                 ` Bruce Ashfield
2013-10-30 14:08                                                   ` Diego Sueiro
2013-10-30 14:26                                                 ` Bruce Ashfield
2013-11-04  3:14                                                 ` Bruce Ashfield
2013-11-28 15:37                                                   ` Diego Sueiro
2013-11-28 15:49                                                     ` Bruce Ashfield
2013-11-28 16:26                                                       ` Diego Sueiro
2013-11-28 16:28                                                         ` Bruce Ashfield
2013-11-28 16:41                                                           ` Paul Eggleton
2013-11-28 17:26                                                             ` Bruce Ashfield
2013-10-30  7:57 ` Jukka Rissanen
2013-10-30 12:27   ` Bruce Ashfield

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=CAAQYJAtzSheOwBecK+SqgnRFQd8Uhq4RZHhEi855fVurirjOZQ@mail.gmail.com \
    --to=andrea.adami@gmail.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=rstreif@linuxfoundation.org \
    --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.