Lines Matching refs:to
25 It has originally written by C.L. Huang from the Tekram corp. to support the
27 scsi = SCSI driver, m = AMD (?) as opposed to w for the DC390W/U/F
34 general AM53C974 based adapters and some possibilities to configure it were
45 The numbering scheme isn't consistent. The first versions went from 1.00 to
46 1.12, then 1.20a to 1.20t. Finally I decided to use the ncr53c8xx scheme. So
47 the next revisions will be 2.0a to 2.0X (stable), 2.1a to 2.1X (experimental),
48 2.2a to 2.2X (stable, again) etc. (X = anything between a and z.) If I send
49 fixes to people for testing, I create intermediate versions with a digit
56 linux/drivers/scsi, you basically have to do nothing special to use this
57 driver. Of course you have to choose to compile SCSI support and DC390(T)
65 my web page and apply the patch. Apply further patches to upgrade to the
68 If you want to do it manually, you should copy the files (dc390.h,
69 tmscsim.h, tmscsim.c, scsiiom.c and README.tmscsim) from this directory to
70 linux/drivers/scsi. You have to recompile your kernel/module of course.
74 The patches are against 2.1.125, so you might have to manually resolve
75 rejections when applying to another kernel version.
77 The patches will update the kernel startup code to allow boot parameters to
78 be passed to the driver, update the Documentation and finally offer you the
79 possibility to omit the non-DC390 parts of the driver.
85 I recommend upgrading your kernel. However, if you don't want to, please
86 contact me to get the appropriate patches.
89 Upgrading a SCSI driver is always a delicate thing to do. The 2.0 driver has
90 proven stable on many systems, but it's still a good idea to take some
100 * make sure you are able to boot Linux (e.g. from floppy disk using InitRD)
104 One more warning: I used to overclock my PCI bus to 41.67 MHz. My Tekram
106 produced errors and started to corrupt my disks. So don't do that! A 37.50
115 * Sync speed up to 10 MHz
120 * Support for up to 4 AM53C974 adapters.
123 * Dynamically configurable by writing to /proc/scsi/tmscsim/?
132 * Try to use the partition table for the determination of the mapping
163 is somehow inconvenient, but the way the mid-level SCSI code expects it to be.
174 (1 / 112 ns = 8.9 MHz). At least in theory. The driver is able to adjust the
177 10 MHz corresp. to a min. NegoPeriod of 100 ns.
179 it, but that's out of adapter spec, on your own risk and unlikely to improve
180 performance. You're likely to crash your disks.)
183 displayed in brackets to show the values which will be used after enabling
188 If you want to change a setting, you can do that by writing to
189 /proc/scsi/tmscsim/?. Basically you have to imitate the output of driver.
191 You don't have to care about capitalisation. The driver will accept space,
203 unless you want to see what happens, if the driver hangs.
205 (2) Change device settings: You write a config line to the driver. The Nr
208 You can use "y" or "n" instead of "Yes" and "No" if you want to.
209 You don't need to specify a full line. The driver automatically performs
210 an INQUIRY on the device if necessary to check if it is capable to operate
218 select the device to which the following parameters apply. Note that it
219 would be sufficient to use the index or both SCSI ID and LUN, but I chose
220 to require all three to have a syntax similar to the output.
224 the Negotiation Period setting but the "10" sets the max sync. speed to
225 10 MHz. It's useless to specify both NegoPeriod and SyncSpeed as
244 after unmounting its partitions, telling the SCSI mid-level code to
247 The ADD command allows you to configure a device before you tell the
248 mid-level code to try detection.
252 settings to see if everything changed as requested.
257 With the DC390, the driver reads its EEPROM settings and tries to use them.
258 But you may want to override the settings prior to being able to change the
261 possibility to adjust settings before you are able to write to the
262 /proc/scsi/tmscsim/? pseudo-file, e.g. if you want to use another
265 For this purpose, you can pass options to the driver before it is initialised
267 pages on how to pass params to the kernel or a module.
268 [NOTE: Formerly, it was not possible to override the EEPROM supplied
273 interface. This makes it a little bit more difficult to use. However, long
274 parameter lines have the risk to be misinterpreted and the length of kernel
293 applies to all devices. (Sync, Disc and TagQ will only apply, if the
304 you want to enable all values, e.g., you would use 31(0x1f). Default is 31.
326 bus reset. Default is 1 (corresp. to 1.5s).
330 would set the adapter ID to 6, max. speed to 6.7 MHz, enable all device
332 and the Delay after a reset to the defaults.
334 As you can see, you don't need to specify all of the six params.
335 If you want values to be ignored (i.e. the EEprom settings or the defaults
338 The defaults (7,0,31,15,3,1) are aggressive to allow good performance. You
347 to further improve its usability:
370 For the CRW4416S, this seems to be solved with firmware 1.0g (reported by
375 replaced by the dev index of your scanner). You may try to reset your SCSI
377 The problem seems to be solved as of 2.0d18, thanks to Andreas Rick.
383 want to be compatible to those, use this old mapping when creating
388 Try to disable DsCn, if you meet this problem. Please contact me for
394 Whenever you have problems with the driver, you are invited to ask the
395 author for help. However, I'd suggest reading the docs and trying to solve
397 If you find something, which you believe to be a bug, please report it to me.
399 maybe the DC390 log messages to the report.
401 Bug reports should be send to me (Kurt Garloff <dc390@garloff.de>) as well
402 as to the linux-scsi list (<linux-scsi@vger.kernel.org>), as sometimes bugs
405 I will ask you for some more details and probably I will also ask you to
408 Beware: If your syslog gets written to a SCSI disk connected to your
419 Thanks to Linus Torvalds, Alan Cox, the FSF people, the XFree86 team and
421 Thanks to C.L. Huang and Philip Giang (Tekram) for the initial driver
423 Thanks to Doug Ledford, Gérard Roudier for support with SCSI coding.
424 Thanks to a lot of people (espec. Chiaki Ishikawa, Andreas Haumer, Hubert
436 If you want to use any later version of the GNU GPL, you will probably
437 be allowed to, but you have to ask me and Tekram <erich@tekram.com.tw>