I already mailed it inside the small ELKS development group, I want to
add an ethernet driver for the Crystal CS8900A chip. I know this chip
very well, and I can do this. For a little 8bit controller (Atmel AVR)
I also write a driver an a little IP stack with ARP, UDP and 'ping'.
This should only replace some field bus. The ethernet controller:
see http://www.embeddedethernet.com
I need this at home, so I will write it (I don't know when exactly,
as I also have to work on other things....)
So first I will port my primitive filedbus-like stack (arp, udp, ping
and perhaps bootp) to ELKS to connect a embedded target to a host, and
later on I will search a more complex stack (ideas from linux or what
ever.....)
With friendly regards
Christoph Plattner
Dido Sevilla wrote:
>
> Luke Farrar wrote:
> >
> > On Tue, 13 Jun 2000, Cristi wrote:
> >
> > >
> > > I would rather wait for a solid kernel and then add networking. I think
> > > networking should be a module as you don't need networking everywhere.
> > > Biulding it modular you can deal with limited resources.
> > >
> >
> > I think the origional plan was to have a user space stack, and in kernel
> > drivers. That makes sense, as the 64k limit won't stretch much further.
> >
>
> As for NIC drivers, I think a good strategy would be to recycle the
> packet drivers Crynwyr provides. They're all GPL anyhow, right? I
> think that the packet driver model, while it does have performance
> bottlenecks, is good enough for what ELKS is supposed to do. We're
> trying to multitask and network on a real-mode processor with at most
> 640K of RAM...
>
> --
> Rafael R. Sevilla <[EMAIL PROTECTED]> +63 (2) 4342217
> Mobile Robotics Laboratory +63 (917) 4458925
> University of the Philippines Diliman
