Re: ELKS Networking: TCP/IP?

1999-04-23 Thread Stefan Pettersson

On 19-Apr-99 Tobias Ekbom wrote:
  --Murn wrote:
 On Sun, 18 Apr 1999, Tobias wrote:
 
 What I wanted was a discussion about TCP/IP in computers with very
 limited memory.
 
  --Tobias Ekbom

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.


-- 
Stefan Pettersson  Voice +46-70-5933800  Kanard AB
[EMAIL PROTECTED] ([EMAIL PROTECTED])  Fax +46-221-50180 Vretberga
finger [EMAIL PROTECTED] for my public key  S-732 96  ARBOGA

"What a scary world it must be, for those with no UID:GID" /OZ9ABN



Re: ELKS Networking: TCP/IP?

1999-04-23 Thread Frédéric Renet


 
 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 ?

Thnks.

Frédéric Renet
Mipsys
19c Av des Indes
91969 Les Ulis (France)
Tel: +33 1 64 86 26 00
Fax: +33 1 64 86 26 09



Re: ELKS Networking: TCP/IP?

1999-04-23 Thread Alistair Riddoch

=?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