>>It's not clear what you're trying to do; there's no link to your "previous posts".
Here's a link to some of our previous interactions:
Indeed... hard to find. Should be available at a click. Time for improvements... hopefully. Lotta trackers and other Java nonsense on this site.
>>The Ethernet MAC or PHY driver should be able to detect/report
>>when the link's state changes to up or down. I haven't bothered
>>to look at the Linux kernel to see how this is done.
The 'no OS' info must have slipped by you. I have had to add stuff to sense when connection is dropped, in order to change a status LED. Here's a link to my previous posts, if I can find them...
http://mail.at91.com/discussions/viewto ... 24883.html
Not available when searching the site with my username... I had to rely on Google. My username never pops up if there's no reply that includes it. There's no button where I get to see my past posts. Really questioning the utility of this site/forum.
>>But this is typically an event with limited significance.
>>Since the link is typically only between your host and a switch,
>>there could still be no hosts out there to communicate with.
You miss the problem. When you run the example project, if you are not at that time plugged into any equipment, ethernet_phy_auto_negotiate() times out and burbles the error all the way back up, with any error code being discarded along the way (sometimes NULL is good, sometimes bad). The project does not attempt to re-initiate the hardware or connection, it just fails.
I originally wrote around this by blocking on the timeout... I did not have any main-loop tasks requiring attention. Now I wish to get on with other services and to be able to complete the stack initialization. When you start the example with a physical connection, then unplug/replug, there is no problem... maddening!
Has anyone fixed this? Is this just the way it is?