Hi All, We have noticed that if a DM355 is started with the ethernet cable unplugged, the boot hangs for a considerable time doing the 'ifup'. The interface is configured with the following lines in /etc/network/interfaces... auto eth0 iface eth0 inet dhcp
If the cable is plugged in after the board eventually starts, then nothing happens, you get no link light on the connector. Does anybody know a way to fix this? One of our customers reported this on a DM6446 so it looks like it is a common issue for both boards. I am going to try a DM6446 myself to confirm this. Incidentally, I tried using netlink to see if the linkup/link down events are seen by the driver & passed to netlink. If you allow the DM355 to boot with the cable plugged in then start the netlink test program then the events are generated as the cable is unplugged and plugged in.... root@(none):~# ./netlink_test_dm355 Started watching: eth0: link down msg_handler: RTM_NEWLINK netlink_link_state: Link Down eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 msg_handler: RTM_NEWLINK netlink_link_state: Link Up This is a lot better than some boards we have tried ;-) If you ping a host on the network & unplug the cable, then the transmission stops - we have seen all kinds of errors on the console on other boards when this is done. Plugging the cable back in restores operation as you would expect (but don't always get). Regards Phil Q Phil Quiney, Senior Software Engineer Trinity Convergence Cambridge Business Park Cowley Road Cambridge CB4 0WZ, UK T: +44(0)1223-435536 F: +44(0)1223-435560 www.trinityconvergence.com <http://www.trinityconvergence.com/>
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
