🚀 go-pugleaf

In article <15068@oberon.USC.EDU> papa@pollux.usc.edu (Marco Papa) writes:
>In article <443@madnix.UUCP> perry@madnix.UUCP (Perry Kivolowitz) writes:
>|Marco's suggestion to access the CIA registers directly for toggling
>|DTR is *not* a good idea for  the  following reason: No other serial
>|port besides the internal one uses the CIA.
>...
>|Another suggestion:
>|In an earlier incantation of my serial device driver I added a command
>|which would allow access to all setable outputs. Something like:
>|
>|io_Command = CMD_SET_SERIAL_CTRL_LINES;
>|io_Length  = MASK_OF_BITS_TO_BE_AFFECTED;
>|io_Actual  = WHAT_TO_SET_THEM_TO;
>|
>|DoIO(IOB)
>|
>|If we all agree to make this a standard, well then, it will become a
>|standard.
>
>Perry,
>
>I just received word from Bryce that the "standard" way to drop DTR
>is to close and then reopen the device.  This should work no matter
>what serial device and unit one is using.
>
>-- Marco Papa 'Doc'

This is a badly broken approach. There MUST be a method of dropping DTR in
a multitasking environment without losing the serial device. If you close the 
device something else can sneak in there and steal it. I hope Bryce rethinks
this serial attitude problem and cleans this freking thing up a bit. All the
bits of the port should be controllable by the application software through
standard means. Otherwise some uses becoem too awkward to bear thinking about.
{`_'}   Grump


-- 
Sometimes a bird in the hand leaves a sticky deposit.
Perhaps it were best it remain there in the bush with the other one.

{@_@}
	jdow@bix (where else?)		Sometimes the dragon wins. Sometimes
	jdow@gryphon.CTS.COM		the knight. Does the fair maiden ever
	{backbone}!gryphon!jdow		win? Surely both the knight and dragon
					stink. Maybe the maiden should suicide?
					Better yet - she should get an Amiga and
					quit playing with dragons and knights.