[En-Nut-Discussion] detecting an unplugged network cable

[Ulrich Prinz]

Hi!

The driver itself detects that fact and does not start ethernet. To not 
get blocked by DHCP you should run DHCP as a thread. The httpd example 
is not a good reference or that, I think.
I am actually reworkign that part... The new PHY driver can give you 
the information if the cable is connected. But it can take a while for 
AutoNegotiation to link up and you have to wait that time until the 
system times out....

Nope, the best way is to start network an DHCP in a thread. Anything 
else doesn't work.

Best Regards
Ulrich


-----Original Message-----
From: elbric0 <elbric0 at f-m.fm>
To: en-nut-discussion at egnite.de
Sent: Mon, Nov 8, 2010 1:47 am
Subject: [En-Nut-Discussion] detecting an unplugged network cable


Hi,I would like to detect if a network cable is unplugged at boot time 
and skip everything related to network when it is the case. 
NutRegisterDevice(&DEV_ETHER, 0, 0) returns an error after a long while 
when the cable is unplugged. It is possible to use that, but it is a 
little annoying as is makes boot time quite long. Is there another way 
to make the check or a way to make NutRegisterDevice return faster?Best 
RegardsJasmin_______________________________________________http://lists.
egnite.de/mailman/listinfo/en-nut-discussion