Re: pcmcia oops on 2.6.17-rc[12]

[Alan Cox]

On Llu, 2006-05-22 at 23:27 +0200, Rogier Wolff wrote:
> Fine. I know hardware that /cannot/ share interrupts. So, my driver
> requesting an interrupt, and getting: "Can't allocate interrupt" is an
> indication of a hardware configuration error. Or software (you've been
> telling one of the drivers the wrong interrupt line). If you force
> "shared mode", my driver will cope (it works just great on the PCI
> version of the card, no problem). But will the hardware?

Depends on the backplane

> You guys maybe trying to fix very real problems in PCMCIA land, of
> which I have very little knowledge. But changing what "not passing
> SA_SHIRQ" means globlaly IMHO changes too much... 

PCMCIA doesn't need any big changes. The rules are simple. PCMCIA IRQs
today are shared, period. Because of the way the hardware works this
isn't an electrical issue. Drivers that ask for an exclusive PCMCIA IRQ
need to wake up and smell the coffee and get fixed.

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/