From: Pat E. <pat...@ma...> - 2004-03-03 23:05:46
|
On Thu, 04 Mar 2004 01:45:57 +0300 Vlad Doubrov <vl...@w-...> wrote: > Pat Erley wrote: > > > I plan on starting a coSerial driver some time tonight. The driver will work as follows: > > > a line in config.xml creates a /dev/ttySn, and has a > > colinux-serial-daemon that it will call, that will pass to/from > > stdin/out on another program. Examples of such programs could be a > > slirp daemon, a serial console daemon, a virtual palm pilot.... really > > anything for windows that you could want to communicate with a linux > > program. > > Seems to be a very good idea, but it'd be better if it provides a > virtual COM-port interface at the Windows side. An example of virtual > COM-port implementation can be found at http://www.ircomm2k.de/ - I used > to look at it sources and it seems to support only one port, so some > enhancements are needed. The virtual comport part would be something that would be a client of this. > Also it would be nice if it supports not only simple data transfer, but > control signals too (RTS, CTS, DTR, etc...) hmmm. ok, I'll keep that in mind. Pat |