You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the phy-linux panics when its device is not present/disappears/has other errors. Instead, we should find a way for the PHY implementation to gracefully report what has happened so the application can decide how to deal with the situation.
Most likely, the best solution is to define a PHY error type which bubbles up through the FdlMaster's poll() call.
The text was updated successfully, but these errors were encountered:
A related question is how to deal with device disconnects. For most real-world applications this is not relevant as a hardware RS485 won't ever disappear. But, for example, a USB device cannot be assumed stable. Should the PHY implementation auto-reconnect? Should this be the job of the application?
Right now, the
phy-linux
panics when its device is not present/disappears/has other errors. Instead, we should find a way for the PHY implementation to gracefully report what has happened so the application can decide how to deal with the situation.Most likely, the best solution is to define a PHY error type which bubbles up through the
FdlMaster
'spoll()
call.The text was updated successfully, but these errors were encountered: