[9300] in linux-scsi channel archive
Re: TYPE_COMM not being used in the kernel source
daemon@ATHENA.MIT.EDU (Marc SCHAEFER)
Sun Aug 6 05:44:31 2000
To: linux-scsi@vger.rutgers.edu
From: Marc SCHAEFER <schaefer@alphanet.ch>
Date: 6 Aug 2000 11:40:08 +0200
Message-ID: <8mjbpo$t81$1@vulcan.alphanet.ch>
Kees Cook <cook@cpoint.net> wrote:
> Therefore, I'd conclude that the missing definition in include/scsi/scsi.h
> is simply just the case that no one has or uses these devices, especially
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.
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.
I sustain your proposition for the patch (I didn't look at it,
however).
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
