On Sun, Aug 06, 2000 at 11:40:08AM +0200, Marc SCHAEFER wrote:
> Well, I have developped a Linux (user-space) driver for the Able
> Communications SCSI serial device (16-port), two years ago.
> This was however done as a contract work with NDA. I can only tell
> what could be obviously seen from installing the driver:
>
> - it uses the SCSI generic driver
> - it uses ptys
>
> The Able device I developped for had 16 serial lines with full
> flow control and modem signals.
Excellent. That sounds like a very similar product. I'm relatively
familiar with the SCSI generic driver (well, version 1, anyway. version 2
is a giant improvement.) I'm new to ptys, though. I found 0 docs on it,
though. What I know about pty allocation I stole from pppd, and had
confirmed from a few mailing lists. Are there better docs?
> If you have the specification for the protocol for your device type,
> it shouldn't be too difficult to do something similar. The most
> complicated part is the RTS/CTS and various signal handling.
That is exactly what I don't know how to do right now. :) Is there a
simple way to "trap" ioctls done against the slave pty? Because as long
as I can trap the various serial-port ioctls, I can pass them to the
device.
> I sustain your proposition for the patch (I didn't look at it,
> however).
Cool. I didn't mention it in my original email (but it's obvious from
looking at the patch) that it is against 2.4.0-test5. Who handles patch
approval for linux-scsi?
--
Cornelius "Kees" Cook [EMAIL PROTECTED]
Sr. Systems Engineer Counterpoint Networking, Inc.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
