>>>>> "WE" == Weddington, Eric <eric.wedding...@atmel.com> writes:
IS> Apparently, there's at least some interest in Ethernet and IP IS> networking support for AVR (say, [1-3].) [...] WE> See Ethernut: <http://www.ethernut.de/> WE> or the uIP project: WE> <http://www.sics.se/~adam/uip/index.php/Main_Page>f Thanks for the pointers! Seemingly, both focus on TCP (which could hardly be implemented properly on most of the AVR 8-bit MCU's) over IPv4 (which, IIUC, lacks a simpler autoconfiguration that IPv6 provides.) WE> The main thing to understand is that the 8-bit AVR devices do not WE> have an on-chip Ethernet peripheral. So there is almost zero chance WE> that Ethernet capabilities will be added to avr-libc. You will have WE> to use external projects like those above. ACK for Ethernet. However, IP is not specific to Ethernet. E. g., there's non-standard but still widely implemented SLIP, and there's (yet to be released) Stuntapen, and U(S)ART is quite common in 8-bit AVR. So, what's about having, say, htonX () and ntohX () functions in AVR Libc? These are standard [4], aren't tied to Ethernet in any way, and, unless implemented once in a common library, would most likely have to be reimplemented in each of the networking libraries (like the ones mentioned above.) IS> [1] http://www.harbaum.org/till/ledmatrix/ IS> [2] http://tuxgraphics.org/electronics/200710/avr-ntp-clock.shtml IS> [3] http://www.users.globalnet.co.uk/~arcus/avr-ntp/ IS> [4] http://www.opengroup.org/onlinepubs/000095399/functions/htons.html [...] -- FSF associate member #7257
pgpUCFOXNdLE5.pgp
Description: PGP signature
_______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
