=?ISO-8859-1?Q?Fr=E9d=E9ric_Renet?= writes: > > > > > > I have written a SLIP/IP/ICMP/UDP-stack that fits in 2000 bytes program > > and 36 bytes RAM (not KILObytes) including operating system and device drivers, > > that fits in a PIC 16F84. > > > > So it isn't a problem to implement networking in limited memory. > > > Is it possible to have a look on your code ? > I too would be very interested in looking at this code. I suspect it is in assembler, and very PIC specific, but interesting anyway. My understanding is that UDP is a very thin layer on top of IP, and does not require much buffering, whereas implementing TCP is altogether more difficult. Al
- Re: ELKS Networking: TCP/IP? Tobias
- Re: ELKS Networking: TCP/IP? David Murn
- Re: ELKS Networking: TCP/IP? Tobias Ekbom
- Re: ELKS Networking: TCP/IP? Dan Olson
- Re: ELKS Networking: TCP/IP? Riley Williams
- Re: ELKS Networking: TCP/IP? Stefan Pettersson
- Re: ELKS Networking: TCP/IP? Fr�d�ric Renet
- Re: ELKS Networking: TCP/IP? Alistair Riddoch
- Re: ELKS Networking: TCP/IP? Stefan Pettersson
- Re: ELKS Networking: TCP/I... Alan Cox
- Re: ELKS Networking: TCP/IP? William Jenkins
- Re: ELKS Networking: TCP/IP? Brian D Chase
- Re: ELKS Networking: TCP/IP? Tobias
- Re: ELKS Networking: TCP/IP? David Murn
- Re: ELKS Networking: TCP/IP? Joshua E. Rodd
- Re: ELKS Networking: TCP/IP? JueyChong Ong
- Re: ELKS Networking: TCP/IP? Dan Olson
- Re: ELKS Networking: TCP/IP? Alistair Riddoch
