From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Chung-Yeh Wang <chungyehwang@gmail.com>, <yocto@yoctoproject.org>
Subject: Re: Question: Yocto 1.7.1 kernel config defconfig will not be used?
Date: Mon, 9 Mar 2015 09:02:15 -0400 [thread overview]
Message-ID: <54FD99D7.4090708@windriver.com> (raw)
In-Reply-To: <CANBg2hKqzN6kR4=7rpA3O+Ar=Y0rEOMWYgEYXsu78hfq1ZwbdQ@mail.gmail.com>
On 15-03-09 04:36 AM, Chung-Yeh Wang wrote:
> Hi List,
>
> I am using Yocto 1.7.1 to build linux-mainline. I found defconfig will
> not be used when using linux-yocto-custom.bb
> <http://linux-yocto-custom.bb/> (maybe also happens on linux-yocto).
>
> I think below is the reason,
>
> 1. kernel_do_configure is run after do_kernel_configme.The last line of
> do_kernel_configme is echo
> "CONFIG_LOCALVERSION="\"${LINUX_VERSION_EXTENSION}\" >> ${B}/.config
>
> 2. Following are the code to use defconfig,
The linux-yocto kernel_configme task takes the defconfig into account,
and uses it along with kernel configuration fragment processing.
The skipping of the blind defconfig copy is completely intentional.
Cheers,
Bruce
>
> # Copy defconfig to .config if .config does not exist. This allows
> # recipes to manage the .config themselves in do_configure_prepend().
> if [ -f "${WORKDIR}/defconfig" ] && [ ! -f "${B}/.config" ]; then
> cp "${WORKDIR}/defconfig" "${B}/.config"
>
> The condition '[ ! -f "${B}/.config"]' will not be true, so
> recepe-kernel/linux/linux-yocto-custom/defconfig will nerver be used.
>
>
> To use defconfig is one of the method suggested in Kernel developer manual.
>
> Thanks and Regards,
> Chungyeh
>
>
next prev parent reply other threads:[~2015-03-09 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 8:36 Question: Yocto 1.7.1 kernel config defconfig will not be used? Chung-Yeh Wang
2015-03-09 13:02 ` Bruce Ashfield [this message]
2015-03-10 2:02 ` Chung-Yeh Wang
2015-03-10 3:47 ` 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=54FD99D7.4090708@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=chungyehwang@gmail.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.