From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Edward Wingate <edwingate8@gmail.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: kernel defconfig configuration
Date: Fri, 30 Oct 2015 08:39:13 -0400 [thread overview]
Message-ID: <563364F1.1050901@windriver.com> (raw)
In-Reply-To: <CAGMdoF=2QJd1DEH7f7p7sRcMP56vz_pGx8VFUOANWt+fiMShTQ@mail.gmail.com>
On 15-10-29 03:06 PM, Edward Wingate wrote:
> On Thu, Oct 29, 2015 at 6:10 AM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> That's the kernel's configuration subsystem at play, it still has to
>> process the the defconfig (which was placed as .config before starting
>> the kernel build). Invalid options are removed, others are selected
>> by Kconfigs, etc. So what you end up with is the processed .config and
>> your old one in .config.old.
>
> Ah, OK, it's possible the option I wanted (CONFIG_REMOTEPROC) is not
> available for my machine (imx6/wandboard) and so removed. Where can I
> look to see if a config option is valid for a particular
> machine/architecture?
I'm working on some patches that will show you that as part of the
configuration audit task (there's potentially a library I can
leverage) .. but for now, either looking at the Kconfig's or running
menuconfig are the best (brute force) way to find what is missing.
Bruce
>
> Thanks for the help.
>
next prev parent reply other threads:[~2015-10-30 12:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 19:41 kernel defconfig configuration Edward Wingate
2015-10-26 8:03 ` Paul Eggleton
2015-10-27 4:46 ` Edward Wingate
2015-10-27 12:36 ` Daniel.
2015-10-29 7:22 ` Edward Wingate
2015-10-29 13:10 ` Bruce Ashfield
2015-10-29 19:06 ` Edward Wingate
2015-10-30 12:39 ` Bruce Ashfield [this message]
2015-10-30 15:10 ` Daniel.
2015-10-30 15:48 ` Edward Wingate
-- strict thread matches above, loose matches on Subject: below --
2015-10-19 6:37 Edward Wingate
2015-10-19 16:29 ` Daniel.
2015-10-24 20:43 ` Edward Wingate
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=563364F1.1050901@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=edwingate8@gmail.com \
--cc=paul.eggleton@linux.intel.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.