[RTnet-developers] Interrupt sharing realtime / non-realtime

[Klaus K. <kla...@in...>]

Hello,

I'm actually porting drivers for RTnet (hope to tell you more in
some days). But now I have a *real* problem...

In one of my development PCs are two NICs: one for "normal"
ethernet operation, and one as the RTnet interface.
(Different chipsets, different drivers)
After several hours (days) of debugging I found out that my
system hangs up when my new RTnet driver is enabled and a
packet on the "normal" interface arrives. I looked into
the PCI table and: yes, these two f*cking NICs share their
interrupt request line (IRQ 10).

As I'm relative new to realtime development, I suppose that
it's not possible to share an IRQ between realtime and
non-realtime domains?
Nevertheless I think that it's the job of Adeos to handle the
interrupts, and when an IRQ 10 is raised, it should first
be handled by RTAI and then (if remaining unhandled) by
the "normal" linux... or not?
However - I added debugging output to my new driver interrupt
handler to see whenever an interrupt arrives; indeed only
local interrupts of the new RTnet drivers are shown, but
when my "killing" packet (from the normal NIC) arrives, the
system hangs immediately.

Currently I'm using RTnet-0.8.3 and RTAI-3.2.

Any ideas?

Best regards,

    Klaus

-- 
Institut für Informatik
Friedrich-Alexander-Universität Erlangen-Nürnberg
http://www.cs.fau.de