summaryrefslogtreecommitdiffstats
path: root/drivers/scsi/scsi_transport_sas.c
diff options
context:
space:
mode:
authorPetr Vandrovec <petr@vmware.com>2006-01-11 11:31:07 -0800
committerJames Bottomley <jejb@mulgrave.(none)>2006-01-12 15:26:13 -0600
commit745caf71d99c5d4ff4c9e4c0f74e64c429fed531 (patch)
treed03b234d62a611a2d2f29aeac9b13efee0bd5c5c /drivers/scsi/scsi_transport_sas.c
parentcd2f1e6980157638f66f427d577a1c368fd4dc12 (diff)
[SCSI] Pass proper device from BusLogic to SCSI layer
While trying to get SUSE's SLES9 working on system with more than 4GB we've noticed that SCSI layer happilly passes addresses over 4GB to the buslogic driver, which is quite a big problem as buslogic can generate only 32bit busmastering cycles. Fortunately in the current kernels this problem does not exist anymore as SCSI layer now assumes 4GB capable device by default, but it is still good idea to pass correct device structure to the SCSI layer. If nothing else, /sys/block/sda/device now points to /sys/devices/pci0000:00/0000:00:10.0/host0/... instead of /sys/devices/platform/host0/... like it did in the past. Change does nothing for ISA based BusLogic adapters, they'll still end under platform (and they are probably broken for long time as I do not see anything forcing ISA 16MB limit for them). Signed-off-by: Petr Vandrovec <petr@vmware.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
Diffstat (limited to 'drivers/scsi/scsi_transport_sas.c')
0 files changed, 0 insertions, 0 deletions