> I have recently had a problem with the fdomain driver initialisation and
> have found the problem to be the way in which it requests the irq. Here is
> my patch that has so far work ok.
I've seen this patch before. It needs at least one change
> - do_fdomain_16x0_intr, 0, "fdomain", NULL);
> + retcode = request_irq( shpnt->irq,
> + do_fdomain_16x0_intr, SA_SHIRQ, "fdomain", shpnt);
Only set SA_SHIRQ if PCI - say -
pdev?SA_SHIRQ:0
The other problem is that the code doesnt have support for handling IRQ
source checking, so if the line it shares with generates interrupts we might
sometimes do the right thing
I have a long outstanding request with adaptec (who bought future domain)
for the info needed to fix this, but obviously its a dead product, from a
bought company and hardly on their priorities.
I suspect the IRQ handler needs to either
A. Check bit 0 of the status port and return
B. Check bit 4 or bit 9 of the interrupt control register
Without docs someone would need to play with the various combinations and
see what happened
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
