linux/drivers/message/i2o
Markus Lidel e22bec266c [PATCH] Fix i2o_scsi oops on abort
Fix http://bugzilla.kernel.org/show_bug.cgi?id=5923

When a scsi command failed, an oops would result.

Back-to-back SMART queries would make the Seagate drives unhappy.  The
second SMART query would timeout, and the command would be aborted.

Acked-by: Markus Lidel <Markus.Lidel@shadowconnect.com>
Cc: Kenny Simpson <theonetruekenny@yahoo.com>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-02-05 11:06:51 -08:00
..
bus-osm.c [PATCH] I2O: Beautifying 2006-01-06 08:33:54 -08:00
config-osm.c [PATCH] I2O: Optimizing 2006-01-06 08:33:54 -08:00
core.h [PATCH] I2O: fix and workaround for Motorola/Freescale controller 2006-02-03 08:32:07 -08:00
debug.c [PATCH] Typo fix: dot after newline in printk strings 2005-10-30 17:37:20 -08:00
device.c [PATCH] I2O: Lindent run 2006-01-06 08:33:54 -08:00
driver.c [PATCH] I2O: Optimizing 2006-01-06 08:33:54 -08:00
exec-osm.c [PATCH] I2O: Lindent run 2006-01-06 08:33:54 -08:00
i2o_block.c [PATCH] Add block_device_operations.getgeo block device method 2006-01-08 20:13:54 -08:00
i2o_block.h [PATCH] I2O: Lindent run and replacement of printk through osm printing functions 2005-06-24 00:05:29 -07:00
i2o_config.c [PATCH] I2O: Optimizing 2006-01-06 08:33:54 -08:00
i2o_lan.h [PATCH] I2O: Lindent run 2006-01-06 08:33:54 -08:00
i2o_proc.c [PATCH] I2O: Beautifying 2006-01-06 08:33:54 -08:00
i2o_scsi.c [PATCH] Fix i2o_scsi oops on abort 2006-02-05 11:06:51 -08:00
iop.c [PATCH] I2O: Optimizing 2006-01-06 08:33:54 -08:00
Kconfig [PATCH] I2O: SPARC fixes 2006-01-06 08:33:53 -08:00
Makefile [PATCH] I2O: new sysfs attributes and Adaptec specific block device access and 64-bit DMA support 2005-06-24 00:05:28 -07:00
pci.c [PATCH] I2O: fix and workaround for Motorola/Freescale controller 2006-02-03 08:32:07 -08:00
README
README.ioctl spelling: s/retreive/retrieve/ 2006-01-10 00:10:13 +01:00

	Linux I2O Support	(c) Copyright 1999 Red Hat Software
					and others.

	This program is free software; you can redistribute it and/or
	modify it under the terms of the GNU General Public License
	as published by the Free Software Foundation; either version
	2 of the License, or (at your option) any later version.

AUTHORS (so far)

Alan Cox, Building Number Three Ltd.
	Core code, SCSI and Block OSMs

Steve Ralston, LSI Logic Corp.
	Debugging SCSI and Block OSM

Deepak Saxena, Intel Corp.
	Various core/block extensions
	/proc interface, bug fixes
	Ioctl interfaces for control
	Debugging LAN OSM

Philip Rumpf
	Fixed assorted dumb SMP locking bugs

Juha Sievanen, University of Helsinki Finland
	LAN OSM code
	/proc interface to LAN class
	Bug fixes
	Core code extensions

Auvo Häkkinen, University of Helsinki Finland
	LAN OSM code
	/Proc interface to LAN class
	Bug fixes
	Core code extensions

Taneli Vähäkangas, University of Helsinki Finland
	Fixes to i2o_config

CREDITS

	This work was made possible by 

Red Hat Software
	Funding for the Building #3 part of the project

Symbios Logic (Now LSI)
	Host adapters, hints, known to work platforms when I hit
	compatibility problems

BoxHill Corporation
	Loan of initial FibreChannel disk array used for development work.

European Comission
	Funding the work done by the University of Helsinki

SysKonnect
        Loan of FDDI and Gigabit Ethernet cards

ASUSTeK
        Loan of I2O motherboard 

STATUS:

o	The core setup works within limits.
o	The scsi layer seems to almost work. 
           I'm still chasing down the hang bug.
o	The block OSM is mostly functional
o	LAN OSM works with FDDI and Ethernet cards.

TO DO:

General:
o	Provide hidden address space if asked
o	Long term message flow control
o	PCI IOP's without interrupts are not supported yet
o	Push FAIL handling into the core
o	DDM control interfaces for module load etc
o       Add I2O 2.0 support (Deffered to 2.5 kernel)

Block:
o	Multiple major numbers
o	Read ahead and cache handling stuff. Talk to Ingo and people
o	Power management
o	Finish Media changers

SCSI:
o	Find the right way to associate drives/luns/busses

Lan:	
o	Performance tuning
o	Test Fibre Channel code

Tape:
o	Anyone seen anything implementing this ?
           (D.S: Will attempt to do so if spare cycles permit)