Цитата(shworker @ Dec 1 2009, 13:59)
Сеть и ядро 2.6.27:
--- 192.168.0.21 ping statistics ---
4 packets transmitted, 3 packets received, 25% packet loss
round-trip min/avg/max = 1.151/1003.803/2008.343 ms
У меня 2.6.27 и пинг проходит
# ping -c 4 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: seq=0 ttl=64 time=0.958 ms
64 bytes from 192.168.0.1: seq=1 ttl=64 time=0.350 ms
64 bytes from 192.168.0.1: seq=2 ttl=64 time=0.349 ms
64 bytes from 192.168.0.1: seq=3 ttl=64 time=0.696 ms
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0.349/0.588/0.958 ms
Правда вместо at91_twi стоит i2c_gpio, так как
This driver is BROKEN because the controller which it uses
will easily trigger RX overrun and TX underrun errors. Using
low I2C clock rates may partially work around those issues
on some systems. Another serious problem is that there is no
documented way to issue repeated START conditions, as needed
to support combined I2C messages. Use the i2c-gpio driver
unless your system can cope with those limitations.