The reason behind it is that the device driver is for embedded Linux. I am
using Familiar.org distribution. We would like to save the delay between
user program. Another reason is that the device driver is part of network
protocol stack. We want to queue user program specific data in terms of
port number so that user program can open any number of ports. In this way,
we can support mutiple access to the serial port.
> > I am trying to write a device driver using serial port to
> > with Atmel AVR.
> Is there a special reason to do this in Kernelspace? I don't know what
> of device the Atmel AVR is, so I can't tell if there is.
> You may well be able to use the existing Device driver for RS232 devices.
> A device driver may be necessary if you need some other funktionality
> provided by the Kernel only. Examples are Network devices connected to the
> serial port. You will probably have a look at the irda tty driver for a
> possible Example how to implement this.
> "Even though I once ported Midnight Commander for NT, I now think,
> that giving OpenSource support for an OS that is commercial is nonsense"
> (Juan Grigera on slashdot.org)