Vladimir Cotfas wrote: > Jan, > >> I had it running only for a short while w/o the WDT and I did not see any >>> lockup. I could do a longer test. >> That would make e100 _very_ interesting as a eepro100 replacement, at >> least mid-term when we know that no eepro100 users suffer from potential >> regressions with e100. >> > > I left the driver run over night connected to our mixed corporate network, I > had a Linux machine pinging it non-stop (just to prove that we don't have > an rtskb leak) and everything looks fine. > > The TX timeout watchdog did NOT kick in ;)
That's good to hear. Probably the micro-code updates make the difference. So we should definitely head for a (cleaned up) rt_e100. > > However I will keep the wtd in place; again you can make it a compile-time > option via autoconf. No need, in fact. The timer is running in non-RT, and if it hits, it doesn't disturb the rest of the system (rtdm_lock_irqsave path looks short). Jan
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
_______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
