All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Reconfiguring the kernel
Date: Tue, 10 Apr 2012 16:50:17 -0400	[thread overview]
Message-ID: <4F849D09.7070806@windriver.com> (raw)
In-Reply-To: <8F9BD230-D053-4D52-AD15-97E27C84013D@keylevel.com>

On 12-04-10 04:40 PM, Chris Tapp wrote:
> I think this is a summary of the steps needed to reconfigure the kernel,based on the instructions in the 6.0.1 dev manual:
>
> 1) bitbake linux-yocto -c clean
> 2) bitbake linux-yocto -c menuconfig
> 3) bitbake linux-yocto -c compile -f
> 4) bitbake linux-yocto
>
> However, the bzimage in tmp/deploy/images is the same as the one that I had before I executed the above. I'm not sure if the md5sum is the same (will check next time round the loop), but it certainly doesn't seem to pick up the new configuration that I'm generating within menuconfig.
>
> If I use 'cleanall' in step 1 (as shown in the manual) then I do get a new image, but at the expense of having to download the kernel branch again (even with a DL_DIR set). Can I get away with just using 'clean' if I do something else as well ?

This is likely:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=2256

Which is still pending resolution.

Cheers,

Bruce

>
> Chris Tapp
>
> opensource@keylevel.com
> www.keylevel.com
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



  reply	other threads:[~2012-04-10 20:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 20:40 Reconfiguring the kernel Chris Tapp
2012-04-10 20:50 ` Bruce Ashfield [this message]
2012-04-10 21:01   ` Chris Tapp
2012-04-10 21:28 ` Bob Cochran
2012-04-10 21:40   ` Chris Tapp

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=4F849D09.7070806@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=opensource@keylevel.com \
    --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.