linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Holger Schurig <holgerschurig@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Can't turn off SSB (CONFIG_SSB)?
Date: Mon, 21 Dec 2009 11:07:47 -0800	[thread overview]
Message-ID: <4B2FC783.7050709@redfish-solutions.com> (raw)
In-Reply-To: <20091221185922.GD4979@tuxdriver.com>

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.



  reply	other threads:[~2009-12-21 19:07 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
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 [this message]
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=4B2FC783.7050709@redfish-solutions.com \
    --to=philipp_subx@redfish-solutions.com \
    --cc=holgerschurig@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).