In message <[EMAIL PROTECTED]> John Hay writes: : our problem is even before a (non) working interrupt would come into the : picture. I'd have to say that based on the evidence so far, that the interrupts aren't getting routined correctly, or that there's an interrupt conflict. This is almost certainly at the cardbus bridge layer, even though I don't want it to be :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: PCI-CardBus bridge + PCMCIA Lucent Wave... Michael Vasilenko
- Re: PCI-CardBus bridge + PCMCIA Lucent ... Warner Losh
- Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN ... John Hay
- Re: PCI-CardBus bridge + PCMCIA Lucent Wave... Warner Losh
- Re: PCI-CardBus bridge + PCMCIA Lucent ... Michael Vasilenko
- Re: PCI-CardBus bridge + PCMCIA Lu... Warner Losh
- Re: PCI-CardBus bridge + PCMCI... John Hay
- Re: PCI-CardBus bridge + PCMCI... Warner Losh
- Re: PCI-CardBus bridge + PCMCI... Edwin Culp
- Re: PCI-CardBus bridge + PCMCIA Lucent ... John Hay
- Re: PCI-CardBus bridge + PCMCIA Lu... Warner Losh
- Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE... Warner Losh
- Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE trou... Edwin Culp