Hi Geert,
The last patch series I sent was in August (IRQ chip definition for timer D
interrupt, and make use of that in the NE2000 driver). With these changes
(and the ones before, from June) there should be no need for more than
minimal changes to ne.c. So what else do I need to provide for that driver?
Oops, I (incorrectly) thought it was still blocked somewhere on your side...
The smc91Cx one and the USB one still need their own dedicated IRQ chip
definitions (for reasons of IRQ enable/disable more than anything else)
but even the smc91Cx part that you have should work fine (it did for
Christian IIRC). The NE2000 driver should be done - can't think of
anything further to do with it.
I'll try to find some time to look into it.
In the mean time, have you found a better solution that the noirqdebug
kernel option?
I don't like that one.
Neither do I - but the IRQ being disabled is the device specific one,
not the master chip interrupt dispatching the device specific one. The
only way around that is to share this one with a dummy handler (and Paul
did veto that).
Cheers,
Michael
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50a49fe4.8030...@biophys.uni-duesseldorf.de
