Re: [RTnet-users] r7168 using the rt_r8169.ko driver

[Hidde V. (E2M) <hve...@e2...>]

On Mon, Oct 7, 2013 at 5:40 PM, Stéphane ANCELOT <san...@fr...> wrote:
> It unlocks the 8168 internal chip delay to process interrupts (unwanted
> behaviour in real-time process).

My version does this too.

> It is not dedicated to work with a shared interrupt.

My version does work with shared interrupts (I tested this too).

> I may have locked it to 100 Mbps - FDX. (to check).

Yes you have. My version should use the highest speed the hardware supports.

My version seems to support 9 more different cards.

Both our versions use the linux timers. While trying to find a
solution I found that the current rt_e1000 driver also uses linux
timers. A lot of other rt drivers use busy waits for small timeouts.
However, the timeout here is quite large and a busy wait does not seem
like the right solution. I wanted to try to use the rtdm timer service
(http://www.xenomai.org/documentation/trunk/html/api/group__rtdmtimer.html).
However, these timers are not able to pass context to a handler. So, a
handler wouldn't know which device to check in case of multiple
devices. Could you give a suggestion as how to solve it Jan?

Regards,

Hidde