Last time I implemented a complex network-using serial driver,
I chose to implement the driver in userspace, communicating wiht
the kernel through a special driver I called USSP: User-Space Serial
Ports. The general consensus then was that I should've used ptys.
So this time, I've done things using ptys. There were however, some
features that physical serial ports could do which ptys could not.
For example Baud rates. You could set the baud rate on the slave
side, which was impossible to get at from the master side. Also
modem control signals were not implemented.
Also we don't want the program on the master side to have to poll
say every second to see if the other side changed the baud rate
or did something else special. So when these are changed, the other
side is signalled that a change has happened and notified....
So we implemented all this. Patch attached. What do you think?
(We can dial out or dial in on the remote modem using our
userspace driver, without any significant differences from a
normal local port!)
(This is not the time to bitch about that I generated the patch
against the wrong kernel. I'll generate them against recent
kernels when we agree that the followed path is OK. )
-- ** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 ** *-- BitWizard writes Linux device drivers for any device you may have! --* * The Worlds Ecosystem is a stable system. Stable systems may experience * * excursions from the stable situation. We are currently in such an * * excursion: The stable situation does not include humans. *************** - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/