sstaub Ethernet3 - fork or merge back to Ethernet?
Could @sstaub Ethernet3 be done as pull requests to Paul's Teensy Ethernet library? Just asking since I am working on Ethernet for a commercial product and need to pick which of the many T3 MAC address libs to use now and going forward, as well as other Ethernet services such as NTP. It would be nice to not have too much fragmentation or forking of Ethernet functions most people will need. Thanks to everyone for all this helpful code and info...
Could @sstaub Ethernet3 be done as pull requests to Paul's Teensy Ethernet library? Just asking since I am working on Ethernet for a commercial product and need to pick which of the many T3 MAC address libs to use now and going forward, as well as other Ethernet services such as NTP. It would be nice to not have too much fragmentation or forking of Ethernet functions most people will need. Thanks to everyone for all this helpful code and info...