Continued problems with Aironet device and 5.2-RC

[M. Warner Losh]

In message: <1072126978.76846.6.camel at work.ici>
            James Earl <james at icionline.ca> writes:
: On Mon, 2003-12-22 at 11:21, M. Warner Losh wrote:
: > In message: <1072116630.576.4.camel at chero>
: >             James Earl <james at icionline.ca> writes:
: > : On Mon, 2003-12-22 at 02:30, M. Warner Losh wrote:
: > : > In message: <20031222092127.GA2355 at cactus.homeunix.org>
: > : >             jqdkf at army.com writes:
: > : > : On Mon, Dec 22, 2003 at 01:20:14AM -0700, M. Warner Losh wrote:
: > : > : > In message: <20031222053002.GA872 at cactus.homeunix.org>
: > : > : >             jqdkf at army.com writes:
: > : > : > : cbb0: Unsupported card type detected
: > : > : > 
: > : > : > This is typically a symptom of the resource allocation bugs I've been
: > : > : > fighting...
: > : > : > 
: > : > : 
: > : > : So are you suggesting that I should adjust the resource by myself, like
: > : > : irq numbers, for now?
: > : > 
: > : > I have the unhelpful advice "make sure two devices aren't using the
: > : > same address."  You'll likely have to decode all the BARs to make sure
: > : > that this is the case.
: > : 
: > : So, would this be the reason why I haven't been able to get my an0
: > : device to appear on it's own in the vmstat -i output?  It seems the
: > : uhci2 device follows the an0 device to whatever irq I assign to it (an0)
: > : in the bios setup.
: > 
: > an0 will share interrupts with the CardBus bridge and whatever it
: > shares with.
: 
: Do you know if my fxp0 device would also share interrupts with the
: cardbus bridge also?

Yes.  All cards always share the interrupts with the bridge.

: Would you say my Aironet problems sound related to the resource
: allocation bugs that you're fighting?

Not sure.

Warner