From: Michael Buesch <mb@bu3sch.de>
To: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Can't turn off SSB (CONFIG_SSB)?
Date: Mon, 21 Dec 2009 20:09:39 +0100 [thread overview]
Message-ID: <200912212009.41152.mb@bu3sch.de> (raw)
In-Reply-To: <4B2FC725.400@redfish-solutions.com>
On Monday 21 December 2009 20:06:13 Philip A. Prindeville wrote:
> On 12/21/2009 10:45 AM, Michael Buesch wrote:
> > On Monday 21 December 2009 19:31:06 Philip A. Prindeville wrote:
> >> Here's what we have.
> >
> > # CONFIG_SSB is not set
> >
>
> Ok, here's what's happening.
>
> We have a "canned" config that we copy over, per platform.
>
> I'm showing diffs of that config with what results (i.e. what's left in the linux-2.6.27.38 directory after running "make silentoldconfig" and "make prepare1"):
>
> --- target/device/via-c7/linux.config 2009-12-21 10:55:55.000000000 -0800
> +++ build_i586/linux-2.6.27.38-astlinux/.config 2009-12-21 11:02:34.000000000 -0800
> @@ -1,7 +1,7 @@
> #
> # Automatically generated make config: don't edit
> # Linux kernel version: 2.6.27.38
> -# Tue Nov 10 16:50:01 2009
> +# Mon Dec 21 11:02:34 2009
> #
> # CONFIG_64BIT is not set
> CONFIG_X86_32=y
> @@ -1446,8 +1446,16 @@
> #
> # Sonics Silicon Backplane
> #
> -CONFIG_SSB_POSSIBLE=n
> -CONFIG_SSB=n
> +CONFIG_SSB_POSSIBLE=y
> +CONFIG_SSB=m
> +CONFIG_SSB_SPROM=y
> +CONFIG_SSB_PCIHOST_POSSIBLE=y
> +CONFIG_SSB_PCIHOST=y
> +# CONFIG_SSB_B43_PCI_BRIDGE is not set
> +# CONFIG_SSB_SILENT is not set
> +# CONFIG_SSB_DEBUG is not set
> +CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
> +CONFIG_SSB_DRIVER_PCICORE=y
>
> #
> # Multifunction device drivers
> @@ -1621,6 +1629,8 @@
> # CONFIG_USB_DYNAMIC_MINORS is not set
> # CONFIG_USB_SUSPEND is not set
> # CONFIG_USB_OTG is not set
> +# CONFIG_USB_OTG_WHITELIST is not set
> +# CONFIG_USB_OTG_BLACKLIST_HUB is not set
> # CONFIG_USB_MON is not set
>
> #
> @@ -1955,7 +1965,7 @@
> CONFIG_DEBUG_FS=y
> # CONFIG_HEADERS_CHECK is not set
> # CONFIG_DEBUG_KERNEL is not set
> -CONFIG_DEBUG_BUGVERBOSE=y
> +# CONFIG_DEBUG_BUGVERBOSE is not set
> CONFIG_DEBUG_MEMORY_INIT=y
> # CONFIG_LATENCYTOP is not set
> CONFIG_SYSCTL_SYSCALL_CHECK=y
>
>
> as you can see, a bunch of things are getting "turned on" that we explicitly turned off.
>
> -Philip
>
>
>
That is expected, because you have
CONFIG_B44=m
--
Greetings, Michael.
next prev parent reply other threads:[~2009-12-21 19:09 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 [this message]
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=200912212009.41152.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-wireless@vger.kernel.org \
--cc=philipp_subx@redfish-solutions.com \
--cc=rdunlap@xenotime.net \
/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).