Lines Matching +full:in +full:- +full:and +full:- +full:around
1 .. SPDX-License-Identifier: GPL-2.0
8 with "Type: Medium Changer" in /proc/scsi/scsi.
11 common small CD-ROM changers, neither one-lun-per-slot SCSI changers
19 -------------------
23 and one for the device which actually reads and writes the data. The
24 later may be anything, a MOD, a CD-ROM, a tape or whatever. For the
25 changer device this is a "don't care", he *only* shuffles around the
29 The SCSI changer model is complex, compared to - for example - IDE-CD
34 media transport this one shuffles around the media, i.e. the
39 fill in and remove media from the changer.
42 CD-ROM / Tape / whatever drive.
46 123 CD-ROM's, 5 CD-ROM readers (and therefore 6 SCSI ID's: the changer
47 and each CD-ROM) and 2 transport arms. No problem to handle.
51 ---------------------
53 I implemented the driver as character device driver with a NetBSD-like
54 ioctl interface. Just grabbed NetBSD's header file and one of the
65 -------------
67 Support for more than one transport arm is not implemented yet (and
70 I test and use the driver myself with a 35 slot cdrom jukebox from
72 (Exabyte, HP and DEC). Some People use this driver with amanda. It
73 works fine with small (11 slots) and a huge (4 MOs, 88 slots)
74 magneto-optical Jukebox. Probably with lots of other changers too, most
75 (but not all :-) people mail me only if it does *not* work...
77 I don't have any device lists, neither black-list nor white-list. Thus
79 not. In theory every changer device which supports the SCSI-2 media
80 changer command set should work out-of-the-box with this driver. If it
86 --------
92 device [ try "dmesg" if you don't see anything ] and should show up in
94 device and ID ? / LUN 1 for the robot mechanism. But Linux does *not*
98 1) echo "scsi add-single-device 0 0 ID 1" > /proc/scsi/scsi
99 (replace ID with the SCSI-ID of the device)
101 (append="max_scsi_luns=1" in lilo.conf should do the trick)
105 --------
107 If you insmod the driver with "insmod debug=1", it will be verbose and
110 because the kernel will translate the error codes into human-readable
119 --------------
139 These two allow to specify the SCSI ID and LUN for the data
145 are some vendor-specific element types. Grundig for example
148 driver about this vendor-specific element, use this::
155 All three insmod options accept up to four comma-separated
156 values, this way you can configure the element types 5-8.
157 You likely need the SCSI specs for the device in question to
158 find the correct values as they are not covered by the SCSI-2
163 -------
165 I wrote this driver using the famous mailing-patches-around-the-world
168 - Daniel Moehwald <moehwald@hdg.de>
169 - Dane Jasper <dane@sonic.net>
170 - R. Scott Bailey <sbailey@dsddi.eds.com>
171 - Jonathan Corbet <corbet@lwn.net>
175 - Martin Kuehne <martin.kuehne@bnbt.de>
177 for a old, second-hand (but full functional) cdrom jukebox which I use
178 to develop/test driver and tools now.