From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: wireless <linux-wireless@vger.kernel.org>
Subject: Can't turn off SSB (CONFIG_SSB)?
Date: Sun, 20 Dec 2009 17:16:34 -0800 [thread overview]
Message-ID: <4B2ECC72.40703@redfish-solutions.com> (raw)
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.
next reply other threads:[~2009-12-21 1:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 1:16 Philip A. Prindeville [this message]
2009-12-21 1:50 ` Can't turn off SSB (CONFIG_SSB)? 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
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=4B2ECC72.40703@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=linux-wireless@vger.kernel.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.