From: Michael Buesch <mb@bu3sch.de>
To: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: Can't turn off SSB (CONFIG_SSB)?
Date: Mon, 21 Dec 2009 13:28:51 +0100 [thread overview]
Message-ID: <200912211328.53552.mb@bu3sch.de> (raw)
In-Reply-To: <4B2ECC72.40703@redfish-solutions.com>
On Monday 21 December 2009 02:16:34 Philip A. Prindeville wrote:
> I'm building images for an EMBEDDED platform, and forcing CONFIG_SSB_POSSIBLE=n, but I'm still seeing:
>
> *
> * Sonics Silicon Backplane
> *
> Sonics Silicon Backplane support (SSB) [M/y/?] (NEW) n
>
> Support for the Sonics Silicon Backplane bus.
> You only need to enable this option, if you are
> configuring a kernel for an embedded system with
> this bus.
> It will be auto-selected if needed in other
> environments.
>
> The module will be called ssb.
>
> If unsure, say N.
>
> Sonics Silicon Backplane support (SSB) [M/y/?] (NEW) n
>
> Support for the Sonics Silicon Backplane bus.
> You only need to enable this option, if you are
> configuring a kernel for an embedded system with
> this bus.
> It will be auto-selected if needed in other
> environments.
>
> The module will be called ssb.
>
> If unsure, say N.
>
> Sonics Silicon Backplane support (SSB) [M/y/?] (NEW)
>
>
>
> And why does arch/x86/configs/i386_defconfig nail up CONFIG_SSB_POSSIBLE?
>
> This is with 2.6.27.38.
>
> And what are the steps to figuring out the dependency that keeps forcing it on? Something must be doing a "select SSB" but I'm not sure what.
CONFIG_SSB_POSSIBLE is just a management config entry that does not affect compilation.
It's just used to get the dependencies right. As long as CONFIG_SSB is n, no SSB code will
be built. CONFIG_SSB_POSSIBLE does just indicate whether it's possible to enable SSB. No more
and no less. It's just used as a dependency for the other modules that do a "select SSB".
The drivers that automatically select CONFIG_SSB are:
- bcm47xx MIPS platform
- bcm63xx MIPS platform
- b43 driver
- b43legacy driver
- b44 driver
--
Greetings, Michael.
next prev parent reply other threads:[~2009-12-21 12:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 1:16 Can't turn off SSB (CONFIG_SSB)? Philip A. Prindeville
2009-12-21 1:50 ` Randy Dunlap
2009-12-21 4:22 ` Philip A. Prindeville
2009-12-21 16:09 ` Randy Dunlap
2009-12-21 18:31 ` Philip A. Prindeville
2009-12-21 18:45 ` Michael Buesch
2009-12-21 19:06 ` Philip A. Prindeville
2009-12-21 19:09 ` Michael Buesch
2009-12-21 19:11 ` Randy Dunlap
2009-12-21 8:24 ` Holger Schurig
2009-12-21 18:51 ` Philip A. Prindeville
2009-12-21 18:59 ` John W. Linville
2009-12-21 19:07 ` Philip A. Prindeville
2009-12-21 19:11 ` Michael Buesch
2009-12-21 19:03 ` Randy Dunlap
2009-12-21 12:28 ` Michael Buesch [this message]
2009-12-21 12:35 ` Michael Buesch
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=200912211328.53552.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-wireless@vger.kernel.org \
--cc=philipp_subx@redfish-solutions.com \
/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 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).