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 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
