blob: 0edb048b2ea442240bea0e99b5afa787aa4acf98 [file] [log] [blame]
Ju, Seokmannfbf60802006-07-25 08:44:48 -06001Release Date : Fri May 19 09:31:45 EST 2006 - Seokmann Ju <sju@lsil.com>
2Current Version : 2.20.4.9 (scsi module), 2.20.2.6 (cmm module)
3Older Version : 2.20.4.8 (scsi module), 2.20.2.6 (cmm module)
4
51. Fixed a bug in megaraid_init_mbox().
6 Customer reported "garbage in file on x86_64 platform".
7 Root Cause: the driver registered controllers as 64-bit DMA capable
8 for those which are not support it.
9 Fix: Made change in the function inserting identification machanism
10 identifying 64-bit DMA capable controllers.
11
12 > -----Original Message-----
13 > From: Vasily Averin [mailto:vvs@sw.ru]
14 > Sent: Thursday, May 04, 2006 2:49 PM
15 > To: linux-scsi@vger.kernel.org; Kolli, Neela; Mukker, Atul;
16 > Ju, Seokmann; Bagalkote, Sreenivas;
17 > James.Bottomley@SteelEye.com; devel@openvz.org
18 > Subject: megaraid_mbox: garbage in file
19 >
20 > Hello all,
21 >
22 > I've investigated customers claim on the unstable work of
23 > their node and found a
24 > strange effect: reading from some files leads to the
25 > "attempt to access beyond end of device" messages.
26 >
27 > I've checked filesystem, memory on the node, motherboard BIOS
28 > version, but it
29 > does not help and issue still has been reproduced by simple
30 > file reading.
31 >
32 > Reproducer is simple:
33 >
34 > echo 0xffffffff >/proc/sys/dev/scsi/logging_level ;
35 > cat /vz/private/101/root/etc/ld.so.cache >/tmp/ttt ;
36 > echo 0 >/proc/sys/dev/scsi/logging
37 >
38 > It leads to the following messages in dmesg
39 >
40 > sd_init_command: disk=sda, block=871769260, count=26
41 > sda : block=871769260
42 > sda : reading 26/26 512 byte blocks.
43 > scsi_add_timer: scmd: f79ed980, time: 7500, (c02b1420)
44 > sd 0:1:0:0: send 0xf79ed980 sd 0:1:0:0:
45 > command: Read (10): 28 00 33 f6 24 ac 00 00 1a 00
46 > buffer = 0xf7cfb540, bufflen = 13312, done = 0xc0366b40,
47 > queuecommand 0xc0344010
48 > leaving scsi_dispatch_cmnd()
49 > scsi_delete_timer: scmd: f79ed980, rtn: 1
50 > sd 0:1:0:0: done 0xf79ed980 SUCCESS 0 sd 0:1:0:0:
51 > command: Read (10): 28 00 33 f6 24 ac 00 00 1a 00
52 > scsi host busy 1 failed 0
53 > sd 0:1:0:0: Notifying upper driver of completion (result 0)
54 > sd_rw_intr: sda: res=0x0
55 > 26 sectors total, 13312 bytes done.
56 > use_sg is 4
57 > attempt to access beyond end of device
58 > sda6: rw=0, want=1044134458, limit=951401367
59 > Buffer I/O error on device sda6, logical block 522067228
60 > attempt to access beyond end of device
61
Ju, Seokmannaa677bc2006-07-25 08:44:58 -0600622. When INQUIRY with EVPD bit set issued to the MegaRAID controller,
63 system memory gets corrupted.
64 Root Cause: MegaRAID F/W handle the INQUIRY with EVPD bit set
65 incorrectly.
66 Fix: MegaRAID F/W has fixed the problem and being process of release,
67 soon. Meanwhile, driver will filter out the request.
68
Ju, Seokmannc005fb42006-04-27 02:33:06 -070069Release Date : Mon Apr 11 12:27:22 EST 2006 - Seokmann Ju <sju@lsil.com>
70Current Version : 2.20.4.8 (scsi module), 2.20.2.6 (cmm module)
71Older Version : 2.20.4.7 (scsi module), 2.20.2.6 (cmm module)
72
731. Fixed a bug in megaraid_reset_handler().
74 Customer reported "Unable to handle kernel NULL pointer dereference
75 at virtual address 00000000" when system goes to reset condition
76 for some reason. It happened randomly.
77 Root Cause: in the megaraid_reset_handler(), there is possibility not
78 returning pending packets in the pend_list if there are multiple
79 pending packets.
80 Fix: Made the change in the driver so that it will return all packets
81 in the pend_list.
82
832. Added change request.
84 As found in the following URL, rmb() only didn't help the
85 problem. I had to increase the loop counter to 0xFFFFFF. (6 F's)
86 http://marc.theaimsgroup.com/?l=linux-scsi&m=110971060502497&w=2
87
88 I attached a patch for your reference, too.
89 Could you check and get this fix in your driver?
90
91 Best Regards,
92 Jun'ichi Nomura
93
Ju, Seokmanned7e8ef2005-11-17 13:17:25 -050094Release Date : Fri Nov 11 12:27:22 EST 2005 - Seokmann Ju <sju@lsil.com>
95Current Version : 2.20.4.7 (scsi module), 2.20.2.6 (cmm module)
96Older Version : 2.20.4.6 (scsi module), 2.20.2.6 (cmm module)
97
981. Sorted out PCI IDs to remove megaraid support overlaps.
99 Based on the patch from Daniel, sorted out PCI IDs along with
100 charactor node name change from 'megadev' to 'megadev_legacy' to avoid
101 conflict.
102 ---
103 Hopefully we'll be getting the build restriction zapped much sooner,
104 but we should also be thinking about totally removing the hardware
105 support overlap in the megaraid drivers.
106
107 This patch pencils in a date of Feb 06 for this, and performs some
108 printk abuse in hope that existing legacy users might pick up on what's
109 going on.
110
111 Signed-off-by: Daniel Drake <dsd@gentoo.org>
112 ---
113
1142. Fixed a issue: megaraid always fails to reset handler.
115 ---
116 I found that the megaraid driver always fails to reset the
117 adapter with the following message:
118 megaraid: resetting the host...
119 megaraid mbox: reset sequence completed successfully
120 megaraid: fast sync command timed out
121 megaraid: reservation reset failed
122 when the "Cluster mode" of the adapter BIOS is enabled.
123 So, whenever the reset occurs, the adapter goes to
124 offline and just become unavailable.
125
126 Jun'ichi Nomura [mailto:jnomura@mtc.biglobe.ne.jp]
127 ---
128
Ju, Seokmann 672b2d32005-05-16 18:32:17 -0400129Release Date : Mon Mar 07 12:27:22 EST 2005 - Seokmann Ju <sju@lsil.com>
130Current Version : 2.20.4.6 (scsi module), 2.20.2.6 (cmm module)
131Older Version : 2.20.4.5 (scsi module), 2.20.2.5 (cmm module)
132
1331. Added IOCTL backward compatibility.
134 Convert megaraid_mm driver to new compat_ioctl entry points.
135 I don't have easy access to hardware, so only compile tested.
136 - Signed-off-by:Andi Kleen <ak@muc.de>
137
1382. megaraid_mbox fix: wrong order of arguments in memset()
139 That, BTW, shows why cross-builds are useful-the only indication of
140 problem had been a new warning showing up in sparse output on alpha
141 build (number of exceeding 256 got truncated).
142 - Signed-off-by: Al Viro
143 <viro@parcelfarce.linux.theplanet.co.uk>
144
1453. Convert pci_module_init to pci_register_driver
146 Convert from pci_module_init to pci_register_driver
147 (from:http://kerneljanitors.org/TODO)
148 - Signed-off-by: Domen Puncer <domen@coderock.org>
149
1504. Use the pre defined DMA mask constants from dma-mapping.h
151 Use the DMA_{64,32}BIT_MASK constants from dma-mapping.h when calling
152 pci_set_dma_mask() or pci_set_consistend_dma_mask(). See
153 http://marc.theaimsgroup.com/?t=108001993000001&r=1&w=2 for more
154 details.
155 Signed-off-by: Tobias Klauser <tklauser@nuerscht.ch>
156 Signed-off-by: Domen Puncer <domen@coderock.org>
157
1585. Remove SSID checking for Dobson, Lindsay, and Verde based products.
159 Checking the SSVID/SSID for controllers which have Dobson, Lindsay,
160 and Verde is unnecessary because device ID has been assigned by LSI
161 and it is unique value. So, all controllers with these IOPs have to be
162 supported by the driver regardless SSVID/SSID.
163
1646. Date Thu, 27 Jan 2005 04:31:09 +0100
165 From Herbert Poetzl <>
166 Subject RFC: assert_spin_locked() for 2.6
167
168 Greetings!
169
170 overcautious programming will kill your kernel ;)
171 ever thought about checking a spin_lock or even
172 asserting that it must be held (maybe just for
173 spinlock debugging?) ...
174
175 there are several checks present in the kernel
176 where somebody does a variation on the following:
177
178 BUG_ON(!spin_is_locked(&some_lock));
179
180 so what's wrong about that? nothing, unless you
181 compile the code with CONFIG_DEBUG_SPINLOCK but
182 without CONFIG_SMP ... in which case the BUG()
183 will kill your kernel ...
184
185 maybe it's not advised to make such assertions,
186 but here is a solution which works for me ...
187 (compile tested for sh, x86_64 and x86, boot/run
188 tested for x86 only)
189
190 best,
191 Herbert
192
193 - Herbert Poetzl <herbert@13thfloor.at>, Thu, 27 Jan 2005
194
Linus Torvalds1da177e2005-04-16 15:20:36 -0700195Release Date : Thu Feb 03 12:27:22 EST 2005 - Seokmann Ju <sju@lsil.com>
196Current Version : 2.20.4.5 (scsi module), 2.20.2.5 (cmm module)
197Older Version : 2.20.4.4 (scsi module), 2.20.2.4 (cmm module)
198
1991. Modified name of two attributes in scsi_host_template.
200 On Wed, 2005-02-02 at 10:56 -0500, Ju, Seokmann wrote:
201 > + .sdev_attrs = megaraid_device_attrs,
202 > + .shost_attrs = megaraid_class_device_attrs,
203
204 These are, perhaps, slightly confusing names.
205 The terms device and class_device have well defined meanings in the
206 generic device model, neither of which is what you mean here.
207 Why not simply megaraid_sdev_attrs and megaraid_shost_attrs?
208
209 Other than this, it looks fine to me too.
210
211Release Date : Thu Jan 27 00:01:03 EST 2005 - Atul Mukker <atulm@lsil.com>
212Current Version : 2.20.4.4 (scsi module), 2.20.2.5 (cmm module)
213Older Version : 2.20.4.3 (scsi module), 2.20.2.4 (cmm module)
214
2151. Bump up the version of scsi module due to its conflict.
216
217Release Date : Thu Jan 21 00:01:03 EST 2005 - Atul Mukker <atulm@lsil.com>
218Current Version : 2.20.4.3 (scsi module), 2.20.2.5 (cmm module)
219Older Version : 2.20.4.2 (scsi module), 2.20.2.4 (cmm module)
220
2211. Remove driver ioctl for logical drive to scsi address translation and
222 replace with the sysfs attribute. To remove drives and change
223 capacity, application shall now use the device attribute to get the
224 logical drive number for a scsi device. For adding newly created
225 logical drives, class device attribute would be required to uniquely
226 identify each controller.
227 - Atul Mukker <atulm@lsil.com>
228
229 "James, I've been thinking about this a little more, and you may be on
230 to something here. Let each driver add files as such:"
231
232 - Matt Domsch <Matt_Domsch@dell.com>, 12.15.2004
233 linux-scsi mailing list
234
235
236 "Then, if you simply publish your LD number as an extra parameter of
237 the device, you can look through /sys to find it."
238
239 - James Bottomley <James.Bottomley@SteelEye.com>, 01.03.2005
240 linux-scsi mailing list
241
242
243 "I don't see why not ... it's your driver, you can publish whatever
244 extra information you need as scsi_device attributes; that was one of
245 the designs of the extensible attribute system."
246
247 - James Bottomley <James.Bottomley@SteelEye.com>, 01.06.2005
248 linux-scsi mailing list
249
2502. Add AMI megaraid support - Brian King <brking@charter.net>
251 PCI_VENDOR_ID_AMI, PCI_DEVICE_ID_AMI_MEGARAID3,
252 PCI_VENDOR_ID_AMI, PCI_SUBSYS_ID_PERC3_DC,
253
2543. Make some code static - Adrian Bunk <bunk@stusta.de>
255 Date: Mon, 15 Nov 2004 03:14:57 +0100
256
257 The patch below makes some needlessly global code static.
258 -wait_queue_head_t wait_q;
259 +static wait_queue_head_t wait_q;
260
261 Signed-off-by: Adrian Bunk <bunk@stusta.de>
262
2634. Added NEC ROMB support - NEC MegaRAID PCI Express ROMB controller
264 PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_MEGARAID_NEC_ROMB_2E,
265 PCI_SUBSYS_ID_NEC, PCI_SUBSYS_ID_MEGARAID_NEC_ROMB_2E,
266
2675. Fixed Tape drive issue : For any Direct CDB command to physical device
268 including tape, timeout value set by driver was 10 minutes. With this
269 value, most of command will return within timeout. However, for those
270 command like ERASE or FORMAT, it takes more than an hour depends on
271 capacity of the device and the command could be terminated before it
272 completes.
273 To address this issue, the 'timeout' field in the DCDB command will
274 have NO TIMEOUT (i.e., 4) value as its timeout on DCDB command.
275
276
277
278Release Date : Thu Dec 9 19:10:23 EST 2004
279 - Sreenivas Bagalkote <sreenib@lsil.com>
280
281Current Version : 2.20.4.2 (scsi module), 2.20.2.4 (cmm module)
282Older Version : 2.20.4.1 (scsi module), 2.20.2.3 (cmm module)
283
284i. Introduced driver ioctl that returns scsi address for a given ld.
285
286 "Why can't the existing sysfs interfaces be used to do this?"
287 - Brian King (brking@us.ibm.com)
288
289 "I've looked into solving this another way, but I cannot see how
290 to get this driver-private mapping of logical drive number-> HCTL
291 without putting code something like this into the driver."
292
293 "...and by providing a mapping a function to userspace, the driver
294 is free to change its mapping algorithm in the future if necessary .."
295 - Matt Domsch (Matt_Domsch@dell.com)
296
297Release Date : Thu Dec 9 19:02:14 EST 2004 - Sreenivas Bagalkote <sreenib@lsil.com>
298
299Current Version : 2.20.4.1 (scsi module), 2.20.2.3 (cmm module)
300Older Version : 2.20.4.1 (scsi module), 2.20.2.2 (cmm module)
301
302i. Fix a bug in kioc's dma buffer deallocation
303
304Release Date : Thu Nov 4 18:24:56 EST 2004 - Sreenivas Bagalkote <sreenib@lsil.com>
305
306Current Version : 2.20.4.1 (scsi module), 2.20.2.2 (cmm module)
307Older Version : 2.20.4.0 (scsi module), 2.20.2.1 (cmm module)
308
309i. Handle IOCTL cmd timeouts more properly.
310
311ii. pci_dma_sync_{sg,single}_for_cpu was introduced into megaraid_mbox
312 incorrectly (instead of _for_device). Changed to appropriate
313 pci_dma_sync_{sg,single}_for_device.
314
315Release Date : Wed Oct 06 11:15:29 EDT 2004 - Sreenivas Bagalkote <sreenib@lsil.com>
316Current Version : 2.20.4.0 (scsi module), 2.20.2.1 (cmm module)
317Older Version : 2.20.4.0 (scsi module), 2.20.2.0 (cmm module)
318
319i. Remove CONFIG_COMPAT around register_ioctl32_conversion
320
321Release Date : Mon Sep 27 22:15:07 EDT 2004 - Atul Mukker <atulm@lsil.com>
322Current Version : 2.20.4.0 (scsi module), 2.20.2.0 (cmm module)
323Older Version : 2.20.3.1 (scsi module), 2.20.2.0 (cmm module)
324
325i. Fix data corruption. Because of a typo in the driver, the IO packets
326 were wrongly shared by the ioctl path. This causes a whole IO command
327 to be replaced by an incoming ioctl command.
328
329Release Date : Tue Aug 24 09:43:35 EDT 2004 - Atul Mukker <atulm@lsil.com>
330Current Version : 2.20.3.1 (scsi module), 2.20.2.0 (cmm module)
331Older Version : 2.20.3.0 (scsi module), 2.20.2.0 (cmm module)
332
333i. Function reordering so that inline functions are defined before they
334 are actually used. It is now mandatory for GCC 3.4.1 (current stable)
335
336 Declare some heavy-weight functions to be non-inlined,
337 megaraid_mbox_build_cmd, megaraid_mbox_runpendq,
338 megaraid_mbox_prepare_pthru, megaraid_mbox_prepare_epthru,
339 megaraid_busywait_mbox
340
341 - Andrew Morton <akpm@osdl.org>, 08.19.2004
342 linux-scsi mailing list
343
344 "Something else to clean up after inclusion: every instance of an
345 inline function is actually rendered as a full function call, because
346 the function is always used before it is defined. Atul, please
347 re-arrange the code to eliminate the need for most (all) of the
348 function prototypes at the top of each file, and define (not just
349 declare with a prototype) each inline function before its first use"
350
351 - Matt Domsch <Matt_Domsch@dell.com>, 07.27.2004
352 linux-scsi mailing list
353
354
355ii. Display elapsed time (countdown) while waiting for FW to boot.
356
357iii. Module compilation reorder in Makefile so that unresolved symbols do
358 not occur when driver is compiled non-modular.
359
360 Patrick J. LoPresti <patl@users.sourceforge.net>, 8.22.2004
361 linux-scsi mailing list
362
363
364Release Date : Thu Aug 19 09:58:33 EDT 2004 - Atul Mukker <atulm@lsil.com>
365Current Version : 2.20.3.0 (scsi module), 2.20.2.0 (cmm module)
366Older Version : 2.20.2.0 (scsi module), 2.20.1.0 (cmm module)
367
368i. When copying the mailbox packets, copy only first 14 bytes (for 32-bit
369 mailboxes) and only first 22 bytes (for 64-bit mailboxes). This is to
370 avoid getting the stale values for busy bit. We want to set the busy
371 bit just before issuing command to the FW.
372
373ii. In the reset handling, if the reseted command is not owned by the
374 driver, do not (wrongly) print information for the "attached" driver
375 packet.
376
377iii. Have extended wait when issuing command in synchronous mode. This is
378 required for the cases where the option ROM is disabled and there is
379 no BIOS to start the controller. The FW starts to boot after receiving
380 the first command from the driver. The current driver has 1 second
381 timeout for the synchronous commands, which is far less than what is
382 actually required. We now wait up to MBOX_RESET_TIME (180 seconds) for
383 FW boot process.
384
385iv. In megaraid_mbox_product_info, clear the mailbox contents completely
386 before preparing the command for inquiry3. This is to ensure that the
387 FW does not get junk values in the command.
388
389v. Do away with the redundant LSI_CONFIG_COMPAT redefinition for
390 CONFIG_COMPAT. Replace <asm/ioctl32.h> with <linux/ioctl32.h>
391
392 - James Bottomley <James.Bottomley@SteelEye.com>, 08.17.2004
393 linux-scsi mailing list
394
395vi. Add support for 64-bit applications. Current drivers assume only
396 32-bit applications, even on 64-bit platforms. Use the "data" and
397 "buffer" fields of the mimd_t structure, instead of embedded 32-bit
398 addresses in application mailbox and passthru structures.
399
400vii. Move the function declarations for the management module from
401 megaraid_mm.h to megaraid_mm.c
402
403 - Andrew Morton <akpm@osdl.org>, 08.19.2004
404 linux-scsi mailing list
405
406viii. Change default values for MEGARAID_NEWGEN, MEGARAID_MM, and
407 MEGARAID_MAILBOX to 'n' in Kconfig.megaraid
408
409 - Andrew Morton <akpm@osdl.org>, 08.19.2004
410 linux-scsi mailing list
411
412ix. replace udelay with msleep
413
414x. Typos corrected in comments and whitespace adjustments, explicit
415 grouping of expressions.
416
417
418Release Date : Fri Jul 23 15:22:07 EDT 2004 - Atul Mukker <atulm@lsil.com>
419Current Version : 2.20.2.0 (scsi module), 2.20.1.0 (cmm module)
420Older Version : 2.20.1.0 (scsi module), 2.20.0.0 (cmm module)
421
422i. Add PCI ids for Acer ROMB 2E solution
423
424ii. Add PCI ids for I4
425
426iii. Typo corrected for subsys id for megaraid sata 300-4x
427
428iv. Remove yield() while mailbox handshake in synchronous commands
429
430
431 "My other main gripe is things like this:
432
433 + // wait for maximum 1 second for status to post
434 + for (i = 0; i < 40000; i++) {
435 + if (mbox->numstatus != 0xFF) break;
436 + udelay(25); yield();
437 + }
438
439 which litter the driver. Use of yield() in drivers is deprecated."
440
441 - James Bottomley <James.Bottomley@SteelEye.com>, 07.14.2004
442 linux-scsi mailing list
443
444v. Remove redundant __megaraid_busywait_mbox routine
445
446vi. Fix bug in the managment module, which causes a system lockup when the
447 IO module is loaded and then unloaded, followed by executing any
448 management utility. The current version of management module does not
449 handle the adapter unregister properly.
450
451 Specifically, it still keeps a reference to the unregistered
452 controllers. To avoid this, the static array adapters has been
453 replaced by a dynamic list, which gets updated every time an adapter
454 is added or removed.
455
456 Also, during unregistration of the IO module, the resources are
457 now released in the exact reverse order of the allocation time
458 sequence.
459
460
461Release Date : Fri Jun 25 18:58:43 EDT 2004 - Atul Mukker <atulm@lsil.com>
462Current Version : 2.20.1.0
463Older Version : megaraid 2.20.0.1
464
465i. Stale list pointer in adapter causes kernel panic when module
466 megaraid_mbox is unloaded
467
468
469Release Date : Thu Jun 24 20:37:11 EDT 2004 - Atul Mukker <atulm@lsil.com>
470Current Version : 2.20.0.1
471Older Version : megaraid 2.20.0.00
472
473i. Modules are not 'y' by default, but depend on current definition of
474 SCSI & PCI.
475
476ii. Redundant structure mraid_driver_t removed.
477
478iii. Miscellaneous indentation and goto/label fixes.
479 - Christoph Hellwig <hch@infradead.org>, 06.24.2004 linux-scsi
480
481iv. scsi_host_put(), do just before completing HBA shutdown.
482
483
484
485Release Date : Mon Jun 21 19:53:54 EDT 2004 - Atul Mukker <atulm@lsil.com>
486Current Version : 2.20.0.0
487Older Version : megaraid 2.20.0.rc2 and 2.00.3
488
489i. Independent module to interact with userland applications and
490 multiplex command to low level RAID module(s).
491
492 "Shared code in a third module, a "library module", is an acceptable
493 solution. modprobe automatically loads dependent modules, so users
494 running "modprobe driver1" or "modprobe driver2" would automatically
495 load the shared library module."
496
497 - Jeff Garzik <jgarzik@pobox.com> 02.25.2004 LKML
498
499 "As Jeff hinted, if your userspace<->driver API is consistent between
500 your new MPT-based RAID controllers and your existing megaraid driver,
501 then perhaps you need a single small helper module (lsiioctl or some
502 better name), loaded by both mptraid and megaraid automatically, which
503 handles registering the /dev/megaraid node dynamically. In this case,
504 both mptraid and megaraid would register with lsiioctl for each
505 adapter discovered, and lsiioctl would essentially be a switch,
506 redirecting userspace tool ioctls to the appropriate driver."
507
508 - Matt Domsch <Matt_Domsch@dell.com> 02.25.2004 LKML
509
510ii. Remove C99 initializations from pci_device id.
511
512 "pci_id_table_g would be much more readable when not using C99
513 initializers.
514 PCI table doesn't change, there's lots of users that prefer the more
515 readable variant. And it's really far less and much easier to grok
516 lines without C99 initializers."
517
518 - Christoph Hellwig <hch@infradead.org>, 05.28.2004 linux-scsi
519
520iii. Many fixes as suggested by Christoph Hellwig <hch@infradead.org> on
521 linux-scsi, 05.28.2004
522
523iv. We now support up to 32 parallel ioctl commands instead of current 1.
524 There is a conscious effort to let memory allocation not fail for ioctl
525 commands.
526
527v. Do away with internal memory management. Use pci_pool_(create|alloc)
528 instead.
529
530vi. Kill tasklet when unloading the driver.
531
532vii. Do not use "host_lock', driver has fine-grain locks now to protect all
533 data structures.
534
535viii. Optimize the build scatter-gather list routine. The callers already
536 know the data transfer address and length.
537
538ix. Better implementation of error handling and recovery. Driver now
539 performs extended errors recovery for instances like scsi cable pull.
540
541x. Disassociate the management commands with an overlaid scsi command.
542 Driver now treats the management packets as special packets and has a
543 dedicated callback routine.