This change forces the controller drivers to allocate a scsibus_data struct
via a call to scsi_alloc_bus(), fill in the adapter_link field, and optionally
modify any other fields of the struct. Scsi_alloc_bus() initializes all fields
to the default, so the changes in most drivers are very minimal. For drivers
that support Wide controllers, the maxtarg field will have to be updated to
allow probing of all targets (for an example, look at the aic7xxx driver).
Scsi_attachdevs() now takes a scsibus_data* as its argument instead of an
sc_link*. This allows us to expand the role of the scsibus_data struct for
other bus level configuration setings (max number of transactions, current
transaction opennings, etc for better tagged queuing support).
Reviewed by: Rodney Grimes <rgrimes>, Peter Dufault <dufault>, Julian Elischer <julian>
Future Domain TMC-885 controllers. These beasts were just different enough in
a number of perverse ways to be recognised but not work with the seagate
stuff. I also whacked in blind transfers for DATAIN and DATAOUT phases - this
more than doubles my throughput. If you're dubious about that, comment out the
definition of SEA_BLINDTRANSFER. Anyway if you're running an ST01 or TMC-950
controller, please give this a go, I'd like to see if anything's broken for
those beasts.
Submitted by: Stephen Hocking <sysseh@devetir.qld.gov.au>
For those where it was easy, drivers were also fixed to call
dev_attach() during probe rather than attach (in keeping with the
new design articulated in a mail message five months ago). For
a few that were really easy, correct state tracking was added as well.
The `fd' driver was fixed to correctly fill in the description.
The CPU identify code was fixed to attach a `cpu' device. The code
was also massively reordered to fill in cpu_model with somethingremotely
resembling what identifycpu() prints out. A few bytes saved by using
%b to format the features list rather than lots of ifs.
This is new version of Seagate ST01/02, Future Domain TMC-885, TMC-950
SCSI driver for FreeBSD. I started from the 2.0R version and mostly
rewrote it. New features are:
1) New probe algorithm. Old driver read the BIOS region of the adapter
memory and find the copyright string. The problem was in the BIOS itself:
it conflicted with IDE disks. The solution was to unplug it and
make the probe algorithm to work without it.
2) Proper timeout handling in numerous places where the driver
polls waiting for some event.
3) Assembler flagments added in critical places, mostly for data transfer
to of from the target. It was possible to make it faster,
but at the price of decreasing reliability.
4) Target-dependent delays when waiting for REQ deassert event.
Some devices seem to be slower (CD-ROMS, some tape drives),
and some seem to be too fast (disks). The driver tests the REQ
deassert timeout for each target and then uses it for polling.
5) Device flags added for SCSI parity control and sense request
priority control.
6) Generic cleanup, after which the driver became much more readable
(at least by me:).
7) Target data parity error logging is limited to avoid log file overflow.
8) Manual page added.
Submitted by: serge
