On 12/21/2009 10:59 AM, John W. Linville wrote: > On Mon, Dec 21, 2009 at 10:51:16AM -0800, Philip A. Prindeville wrote: >> On 12/21/2009 12:24 AM, Holger Schurig wrote: >>>> 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. >>> >>> "make xconfig", and then turn on "Options -> Show Debug Info". >>> >>> Then you see the reverse dep. >>> >>> >>> Another thing would be "find -name Kconfig |xargs grep >>> SSB_POSSIBLE" and then carefully check those files. >> >> Well, as I mentioned, arch/x86/configs/i386_defconfig contains: >> >> CONFIG_SSB_POSSIBLE=y >> >> which I've not been able to understand why. There are lots of x86 configurations where this might *not* be possible, in embedded platforms in particular. > > config SSB_POSSIBLE > bool > depends on HAS_IOMEM && HAS_DMA > default y > > What x86 configurations don't have IOMEM or DMA? And what difference > does it make if SSB_POSSIBLE is defined if it doesn't build any code? > > John The issue is that later on when we build compat-wireless, then my .config file from the linux build directory gets sourced by that and we get a bunch of warnings from the b43, b44, etc. drivers that some ssb_* entry points are missing. -- 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
