🚀 go-pugleaf

In article <19435@gryphon.COM> ddave@pnet02.gryphon.com (David Donley) writes:
>
>Hello there, I have discovered that hot keys in BBS programs do not work right
>with the supra internal modem device driver (It's supposed to be a
>serial.device clone)
> 
>Anyhow, I talked to the writer and he says that it says in the new 1.3
>auto-docs that the CMD_WRITE command is supposed to queue up output and return
>immediatly.  He is aware that this is not the way the serial.device does it,
>but he says he is doing it "by the book".  I don't think this is the way it
>should be, for several reasons:

I suggest that there is some other problem lurking in the Supra driver.

The author is correct in stating that the serial device should support multiple
queued writes. However, I think you have a misunderstanding (from the text I
deleted) about who declares and maintains the buffer.

Queued writes are not pooled in a common buffer. Rather, each chunk of
memory you supply in the iorequest block is held onto by the driver and used
to hold the bytes to be written until they are written or the iorequest is
aborted. 

Bottom line: If it works with the serial.device and doesn't work with the
supra driver, there's a bug in the supra driver.

Interesting Corallary: If a function *doesn't* work with serial.device, 
it may mean simply that there's a bug in the serial.device. Our ASDG test
suite contains a number of function combinations which *should* work but
don't on the serial.device due to its deficiencies. They *do* work as you
would expect from the Rom Kernel Manual on the ASDG Dual Serial Board, however.

pk

-- 
                        Perry Kivolowitz, ASDG Inc.
ARPA: madnix!perry@cs.wisc.edu   {uunet|ncoast}!marque!
UUCP: {harvard|rutgers|ucbvax}!uwvax!astroatc!nicmad!madnix!perry
CIS:  76004,1765 (what was that about ``giggling teenagers''?)