So any change in this area is untestable in the 2.4 context. Sigh.
But how can the current code prevent IRQ problems? AFAICT it just
delays the yenta_open_bh() operations by a short-but-random time
interval.
Should the IRQ be registered _after_ the call to cardbus_register()
when, presumably, the hardware is set up and has negated the IRQ
signal?
-
-
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/