* Why do some config options return limited info from a search?
@ 2018-03-19 0:08 John Whitmore
2018-03-19 0:49 ` valdis.kletnieks at vt.edu
0 siblings, 1 reply; 3+ messages in thread
From: John Whitmore @ 2018-03-19 0:08 UTC (permalink / raw)
To: kernelnewbies
I'm trying to build the required options for my Laptop into the kernel, so not modules. When you search, in make menuconfig, for a config option you usually get very useful info about where it is, in the menus, and what its prompt is. This makes them easier to find.
Sometimes however you get a module which don't give this information. Is this intentional, signify something, or just an oversight for that config option? For example SND_HDA_CORE:
Symbol: SND_HDA_CORE [=m]
Type : tristate
Defined at sound/hda/Kconfig:1
Depends on: SOUND [=y] && !UML && SND [=y]
Selects: REGMAP [=y]
Selected by:
- SND_HDA_EXT_CORE [=m] && SOUND [=y] && !UML && SND [=y]
- SND_HDA [=m] && SOUND [=y] && !UML && SND [=y]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Why do some config options return limited info from a search?
2018-03-19 0:08 Why do some config options return limited info from a search? John Whitmore
@ 2018-03-19 0:49 ` valdis.kletnieks at vt.edu
2018-03-20 21:19 ` John Whitmore
0 siblings, 1 reply; 3+ messages in thread
From: valdis.kletnieks at vt.edu @ 2018-03-19 0:49 UTC (permalink / raw)
To: kernelnewbies
On Mon, 19 Mar 2018 00:08:10 -0000, John Whitmore said:
> Sometimes however you get a module which don't give this information. Is this
> intentional, signify something, or just an oversight for that config option?
> For example SND_HDA_CORE:
> Symbol: SND_HDA_CORE [=m]
> Type : tristate
> Defined at sound/hda/Kconfig:1
> Depends on: SOUND [=y] && !UML && SND [=y]
> Selects: REGMAP [=y]
> Selected by:
> - SND_HDA_EXT_CORE [=m] && SOUND [=y] && !UML && SND [=y]
> - SND_HDA [=m] && SOUND [=y] && !UML && SND [=y]
Some internal symbols don't have any visible menu-selects, because they are
intended to be turned on only via other things doing 'SELECT'. After all,
SND_HDA_CORE has little to no reason to be enabled unless your kernel build
config asks for SND_HDA or SND_HDA_EXT_CORE (and *that* symbol is 'm', which is
why SND_HDA_CORE is also ''m'. Switching EXT_CORE to 'y' will then auto-switch
this one to 'y' as well).
^ permalink raw reply [flat|nested] 3+ messages in thread
* Why do some config options return limited info from a search?
2018-03-19 0:49 ` valdis.kletnieks at vt.edu
@ 2018-03-20 21:19 ` John Whitmore
0 siblings, 0 replies; 3+ messages in thread
From: John Whitmore @ 2018-03-20 21:19 UTC (permalink / raw)
To: kernelnewbies
On Sun, Mar 18, 2018 at 08:49:52PM -0400, valdis.kletnieks at vt.edu wrote:
> On Mon, 19 Mar 2018 00:08:10 -0000, John Whitmore said:
>
> > Sometimes however you get a module which don't give this information. Is this
> > intentional, signify something, or just an oversight for that config option?
> > For example SND_HDA_CORE:
>
> > Symbol: SND_HDA_CORE [=m]
> > Type : tristate
> > Defined at sound/hda/Kconfig:1
> > Depends on: SOUND [=y] && !UML && SND [=y]
> > Selects: REGMAP [=y]
> > Selected by:
> > - SND_HDA_EXT_CORE [=m] && SOUND [=y] && !UML && SND [=y]
> > - SND_HDA [=m] && SOUND [=y] && !UML && SND [=y]
>
> Some internal symbols don't have any visible menu-selects, because they are
> intended to be turned on only via other things doing 'SELECT'. After all,
> SND_HDA_CORE has little to no reason to be enabled unless your kernel build
> config asks for SND_HDA or SND_HDA_EXT_CORE (and *that* symbol is 'm', which is
> why SND_HDA_CORE is also ''m'. Switching EXT_CORE to 'y' will then auto-switch
> this one to 'y' as well).
>
Perfectly logical and simple. Thanks for your answer that now all makes sense.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-03-20 21:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-03-19 0:08 Why do some config options return limited info from a search? John Whitmore
2018-03-19 0:49 ` valdis.kletnieks at vt.edu
2018-03-20 21:19 ` John Whitmore
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).