From: Pat E. <pat...@ma...> - 2004-03-03 22:42:04
|
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. you could also initiate the serial daemon from outside the xml file, and it would grab the first available ttyS. Any time a ttyS is activated, it should dump a dmesg entry (for hotplug purposes) If you have an entry in the config file that doesn't auto start, you'd issue a echo to a device in /dev to trigger it activating. I havn't decided whether to have your echo go to the device you want to activate like: echo 1 > /dev/ttyS0 or a master device you echo a ttynumber to activate to echo 2 > /dev/coserial I plan on starting on this sometime soon(next day or two) and would like feedback/feature requests. Pat Erley |