> My question to the lwIP users: does anyone have the need to know the link state ? Can you share why ?
I do, for 2 reasons. One: We have a panel LED for link/no link/connected to PC state. Often the user can't see the jack or switch. Gets the 2 basic connectivity questions answered quickly. Two: On loss of link we reset/abort the connection and delay to force the PC to see no activity. Our system is real time and we don't want link glitches to cause pauses that don't close the connection but effect the program's operation causing "bug reports". We'd rather have a fatal disconnect error. Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sergio R. Caprile Sent: Thursday, June 12, 2014 11:51 AM To: [email protected] Subject: [lwip-users] Ethernet link state: needed ? Hi folks, I wrote a driver for the DM9000 Ethernet chip, and nowadays it is missing the link state part. I feel reluctant to add it because I don't really see a need for the stack/application to know the link state, since all the devices I can imagine I'll be developing will be permanently attached to the network, and not mobile devices like a laptop. My question to the lwIP users: does anyone have the need to know the link state ? Can you share why ? Thank you, regards _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
