Messages in this thread | | | Subject | Re: pcmcia oops on 2.6.17-rc[12] | From | Alan Cox <> | Date | Tue, 16 May 2006 01:17:59 +0100 |
| |
On Llu, 2006-05-15 at 16:52 -0700, Linus Torvalds wrote: > Even the ISA drivers that currently do not have SA_SHIRQ won't generally > _break_ when/if they were to get a shared interrupt. The reason they don't > have SA_SHIRQ isn't generally that they really really want an exclusive > interrupt, but simply because they never had a reason to say SA_SHIRQ.
The reason they do it is also however because the ISA bus IRQ allocation scheme and IRQ probing scheme they use for auto detection relies upon other users marking the IRQ as exclusively used. The same is true for things like setserial and ISA ports.
Given the historical use of exclusive IRQ allocation as a resource management API it appears to be easier just to beat up the PCMCIA drivers where the resource element is not present (it is tracked internally by the pcmcia core).
PCMCIA doesn't seem to have too many offenders, and the number of drivers is low so it won't take long to go over them.
Alan
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |