From: hoppie@kub.nl (Jeroen Hoppenbrouwers) Subject: QIC117 specs! Date: Thu, 01 Apr 1993 06:58:50 GMT
[Message crossposted to comp.os.os2.programmer and comp.os.linux .
Manual mailing list managed by hoppie@kub.nl . All info welcome]
Hi,
Yup, here's something. I'll include some snapshots of the News from yesterday
and earlier in the back, for newcomers (they keep coming!). Thanks, Rob.
Can someone try to find an electronic version of QIC40/80 stuff? It would
be very handy to have *all* related material available electronically.
-Jeroen
====================================================================================
From: "J. Robert Sims III" <edb@csn.org>
To: hoppie@kub.nl (Jeroen Hoppenbrouwers)
Date: Wed, 31 Mar 1993 09:44:08 -0700 (MST)
I just got the file with the select/unselect commands. It's quite
simple. All drives we sell through retail channels have a drive
ID of 0, so the command would be 46, 2.
This was actually proposed as a modification to the QIC spec at one
time, so I don't know why the big deal is made of it.
Rob
=====================================================================
Proposed Change to QIC-117 Common Command Set Interface Specification
The following two commands would be added to Table 2a:
Code Command Name Illegal Modes Required States
---- ------------ ------------- ---------------
E B R N W C E R
46 Select Tape Drive ----- - - - - - - - -
47 Deselect Tape Drive ----- - - - - - - - -
Also, the Select Tape Drive command would be added to Table 2b:
Code Command Name Argument(s)
---- ------------ -----------
46 Select Tape Drive Drive ID + 2
Command timings are added to Table 2d:
Code Command Name 250 Kbps/XL 500Kbps/XL Event
---- ------------ ----------- ---------- -----
46 Select Tape Drive 0 -----
47 Deselect Tape Drive 0 -----
Command descriptions as follows:
(46) Select Tape Drive. Select the tape drive by activating
appropriate interface signals. If the tape drive is already
selected then this command is treated as a NOP. This command takes
one argument in the N+2 form. The argument is the tape drive ID.
(47) Deselect Tape Drive. Deselect the tape drive by de-activating
appropriate interface signals. If the tape drive is already
deselected then this command is treated as a NOP. A Soft Reset
will also deselect the tape drive.
================ OLDER NEWS ==========================================
>From king@cs.uq.oz.au Wed Mar 31 04:02:40 1993
There is an alpha version of a QIC80 driver for linux on
tsx-11.mit.edu in /pub/linux/ALPHA/QIC80 (or similar).
Hope this helps,
Paul.
====================================================================
IMPORTANT:
feg@dodger.att.com sent me a BIG ZIP file with a complete
source for a QIC40/80 driver, apparently for some UNIX.
Here's the README:
=============================================================================
Hello,
This is the first alpha test release of ftape, a QIC-40/80 device
driver. Below are some general instructions and hints on how to
proceed.
Please direct questions about the driver that you feel other testers
should read to
tape-alpha@gnu.ai.mit.edu
I can be reached at either dbrown@ucsd.edu, or dbrown@gnu.ai.mit.edu.
- I recommend starting by looking in the vd directory. Although the
code is scattered, and probably not that portable, it might be very
helpful to get the dynamic loading working with your os. If you have
any success here, please send my anything you did to make it work.
Also, feel free to ask questions about this.
- The next thing to work on is the driver. Theoretically, you should
only have to change kernel-interface.c to support a different os, but
I know this is not true. The program userft should help get the thing
running. It provides simple access to some commands. I don't
recommend working on this stuff with a tape that has data you care
about on it. Note that the memory mapping stuff in the
kernel-interface.c is not used by anything now, so you don't need to
make it work.
- Once (and if) you get the driver working, you can then tackle the
qic program. This should be a lot easier to port.
- Let me know how things work.
When you report changes, I prefer either context or unidiff files.
You might want to mention in the patch what version is in version.mk
so I know what to compare the diffs with. I will have all previous
revisions of the software available to me here.
Thanks
Dave
=============================================================================
Looks good, eh?
Since we have no anonymous FTP here at the university (don't flame ME)
I've put it on Hobbes (ftp-os2.nmsu.edu) in /pub/uploads. It is
called ftape-1.02.zip and I've tried to make clear that it is not for
OS/2 and just is there for developers. If anyone has a better idea,
please tell me. I don't think it is a good idea to diatribute over 100K
per mail...
Regards,
Jeroen