Jorge Almeida wrote:
> Hi to all.
> 
> I'm starting to work with rtnet 0.9.4 and i have a machine with a SIS900 NIC 
> and 3 realtek 8139too NICs, eth0 to eth3 respectively, and when i insert 
> rtnet the 3 realtek will became rteth0 to rteth2 respectively.
> The problem is that i also loose the eth0 capability.
> 
> I think the problem is related with the IRQ sharing between eth0 and rteth1, 
> because they share the same interrupt. 
> 
> If the driver rt_8139too.ko has the rt_pend_to_linux feature this should not 
> happen? Right?

Nope, there is no easy, common way of sharing IRQs between RT-safe and
standard, non-RT-safe device drivers. I'm speaking very abstractly here
as this issues is independent of the RT-extension (Xenomai, RTAI,
Preempt-RT, ...), it's a common design issue. See e.g. this posting for
a short explanation (there are a "few" threads on this topic out there...):

https://mail.gna.org/public/xenomai-core/2006-08/msg00186.html

You either have to pick one device and leave the other alone (use the
"cards" module parameter to control the RTnet driver) or you enhance the
RT-driver with shared-IRQ support (fairly easy today) and arrange the
device mapping that sharing only takes place in the RT space. The third
way is the hardest one: write an RT-safe stub for the non-RT device that
handles the IRQ quickly by disabling it in the device's hardware until
Linux executes again.

Jan

Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Reply via email to