M. Koehrer wrote: > O.K., > > I have done a test with the standard e1000 driver of linux (2.4.33, the Intel > e1000 driver 7.1.9) > I have written the following bash script: > modprobe e1000 > ifconfig eth1 up 192.168.2.2 > dmesg -c > sleep 1 > echo "--------" > dmesg -c > sleep 1 > echo "--------" > dmesg -c > > The output of this is: > > Intel(R) PRO/1000 Network Driver - version 7.1.9 > Copyright (c) 1999-2006 Intel Corporation. > e1000: 03:05.0: e1000_probe: (PCI:33MHz:32-bit) 00:0e:0c:b8:e9:32 > e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection > -------- > -------- > e1000: eth1: e1000_watchdog: NIC Link is Up 100 Mbps Half Duplex > > (Here I have connected the e1000 to a Hub - this is where the 100Mbps Half > Duplex comes from). > As you see it takes about 2 seconds after ifconfig until the e1000 is able to > communicate on Ethernet. > I think, the situation is the very same with rtnet...
...except that Thinus's report indicates total failure if transmissions takes place earlier. Could you test what happens when you sent packets during that init period? > This is not nice, however as it is a one-time initialization delay I think it > is acceptable. I think we could live with a simple delay on ifup, if A) we know for sure (or almost) how long it must be and B) cable re-plug doesn't render the device useless until the next manual ifdown/up cycle. Jan
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
