All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: how can i figure out where a particular kernel config option came from?
Date: Wed, 9 Dec 2015 05:36:19 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1512090532270.21086@localhost> (raw)


  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.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



             reply	other threads:[~2015-12-09 10:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 10:36 Robert P. J. Day [this message]
2015-12-09 13:39 ` how can i figure out where a particular kernel config option came from? Bruce Ashfield
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=alpine.LFD.2.20.1512090532270.21086@localhost \
    --to=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.