From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: how can i figure out where a particular kernel config option came from?
Date: Wed, 9 Dec 2015 08:39:15 -0500 [thread overview]
Message-ID: <56682F03.3050501@windriver.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1512090532270.21086@localhost>
On 12/09/2015 05:36 AM, Robert P. J. Day wrote:
>
> short version: with a short BSP layer i've been handed, the eventual
> kernel .config file ends up with the setting:
>
> CONFIG_WIRELESS=y
>
> which makes no sense as the target board has no wireless and the BSP
> itself doesn't set that, so how can i start tracking back to figure
> out where that particular setting came from?
>
> long version: i'm actually using Wind River Linux 7, but the
> question remains the same. it turns out that CONFIG_WIRELESS is
> selected by CONFIG_WLAN, so i'm really after what sets CONFIG_WLAN. i
> don't see it in the BSP layer, so i'm tracing back to the WR kernel
> recipe, and possibly features templates and any other kernel .cfg
> snippets i can find, so far with no luck.
>
> in either case, is there a log file that lists *precisely* which
> kernel config snippets contributed to the final .config file? thanks.
The meta-series in the kernel source directory has all the details.
If you locate the kernel source for your build, it'll be in a 'meta'
or '.meta' directory (depending on the version of the tools), and be
called ... 'meta-series'.
Bruce
>
> rday
>
next prev parent reply other threads:[~2015-12-09 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 10:36 how can i figure out where a particular kernel config option came from? Robert P. J. Day
2015-12-09 13:39 ` Bruce Ashfield [this message]
2015-12-09 13:59 ` Robert P. J. Day
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=56682F03.3050501@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=rpjday@crashcourse.ca \
--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.