Return-path: Received: from xenotime.net ([72.52.64.118]:45433 "HELO xenotime.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1756231AbZLUBvL (ORCPT ); Sun, 20 Dec 2009 20:51:11 -0500 Received: from chimera.site ([96.253.169.185]) by xenotime.net for ; Sun, 20 Dec 2009 17:51:02 -0800 Date: Sun, 20 Dec 2009 17:50:33 -0800 From: Randy Dunlap To: "Philip A. Prindeville" Cc: wireless Subject: Re: Can't turn off SSB (CONFIG_SSB)? Message-Id: <20091220175033.36980f35.rdunlap@xenotime.net> In-Reply-To: <4B2ECC72.40703@redfish-solutions.com> References: <4B2ECC72.40703@redfish-solutions.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: On Sun, 20 Dec 2009 17:16:34 -0800 Philip A. Prindeville wrote: > I'm building images for an EMBEDDED platform, and forcing CONFIG_SSB_POSSIBLE=n, but I'm still seeing: What $ARCH ? > * > * 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? That just means that SSB support is possible: config SSB_POSSIBLE bool depends on HAS_IOMEM && HAS_DMA default y Shouldn't be a problem. > 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. Are you using b43 or b44 network drivers? --- ~Randy