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

2013-10-09 Thread Jan Kiszka
On 2013-10-09 11:13, Hidde Verstoep (E2M) wrote: > 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. The key is that the rt_e1000 doesn't call Linux timer services from real-time contexts or while holding re

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

2013-10-09 Thread Hidde Verstoep (E2M)
On Mon, Oct 7, 2013 at 5:40 PM, Stéphane ANCELOT 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 te

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

2013-10-07 Thread Stéphane ANCELOT
This version is known to work with an RTL8168 (kernel 2.6.34) and solves some issues. It unlocks the 8168 internal chip delay to process interrupts (unwanted behaviour in real-time process). It is not dedicated to work with a shared interrupt. I may have locked it to 100 Mbps - FDX. (to check).

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

2013-10-07 Thread Jan Kiszka
On 2013-10-07 16:34, Stéphane ANCELOT wrote: > Hi, > > Try this one. Please no rtdm_irq_disable/enable for synchronization. This breaks subtly once the affected line is shared with other (real-time) devices. It's also often quite slow. Didn't check all details, so could you list what you did dif

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

2013-10-07 Thread Jan Kiszka
On 2013-10-07 11:10, Hidde Verstoep (E2M) wrote: > On Fri, Oct 4, 2013 at 8:34 AM, Jan Kiszka wrote: >> On 2013-10-03 11:16, Hidde Verstoep (E2M) wrote: >>> Hello Sam, >>> >>> I recently posted a version of the driver I ported from a more recent >>> Linux driver. You can just drop it over the old

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

2013-10-07 Thread Hidde Verstoep (E2M)
On Fri, Oct 4, 2013 at 8:34 AM, Jan Kiszka wrote: > On 2013-10-03 11:16, Hidde Verstoep (E2M) wrote: >> Hello Sam, >> >> I recently posted a version of the driver I ported from a more recent >> Linux driver. You can just drop it over the old file and it should >> work. http://sourceforge.net/maila

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

2013-10-03 Thread Jan Kiszka
On 2013-10-03 11:16, Hidde Verstoep (E2M) wrote: > Hello Sam, > > I recently posted a version of the driver I ported from a more recent > Linux driver. You can just drop it over the old file and it should > work. http://sourceforge.net/mailarchive/message.php?msg_id=31389885. I just had a quick l

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

2013-10-03 Thread sam sokolik
I don't think our conversation made it to the list so I thought I would re-cap. I got Hidde's rt_r8169.c from the link he posted and I dropped the rt_r8169.c file into the /rtnet-0.9.13/drivers directory. I get an error when I do a make clean make /home/empire/rtnet-0.9.13/drivers/rt_r8169.

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

2013-10-03 Thread Hidde Verstoep (E2M)
Hello Sam, I recently posted a version of the driver I ported from a more recent Linux driver. You can just drop it over the old file and it should work. http://sourceforge.net/mailarchive/message.php?msg_id=31389885. I see now that it was an HTML message, which is why you might not have found it

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

2013-10-02 Thread sam sokolik
I meant the subject to say RTL8168 using the rt_r8169.ko driver Also - I did try the rt_8139too.ko driver the same way.. Got this similar error [16716.482616] rt_8139too: :03:00.2: region #1 not an MMIO resource, aborting [16716.482621] Trying to free nonexistent resource