summaryrefslogtreecommitdiffstats
path: root/drivers/scsi/scsi_transport_spi.c
Commit message (Collapse)AuthorAgeFilesLines
* [PATCH] use device_for_each_child() to properly access child devices.gregkh@suse.de2005-06-201-6/+10
| | | | Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* [SCSI] update spi transport class so that u320 Domain Validation worksJames Bottomley2005-06-031-24/+53
| | | | | | | | | | | | | There are several extra things that have to be considered when running Domain Validation on a u320 target (notably how you fall back). Hopefully this should help us when someone adds this transport class to aic79xx. I've tested this on the lsi1030, so I know it works correctly up to u320. Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
* [SCSI] implement parameter limits in the SPI transport classJames Bottomley2005-05-201-27/+161
| | | | | | | | | | | | | | There's a basic need not to have parameters go under or over certain values when doing domain validation. The basic ones are max_offset, max_width and min_period This patch makes the transport class take and enforce these three limits. Currently they can be set by the user, although they could obviously be read from the HBA's on-board NVRAM area during slave_configure (if it has one). Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
* [SCSI] fix command retries in spi_transport classJames Bottomley2005-05-051-15/+34
| | | | | | | | | | | The premise is that domain validation is likely to trigger errors which it wants to know about, so the only time it should be retrying them is when it gets a unit attention (likely as the result of a previous bus or device reset). Ironically, the previous coding retried three times in all cases except those of unit attention. The attached fixes this to do the right thing. Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
* Linux-2.6.12-rc2v2.6.12-rc2Linus Torvalds2005-04-161-0/+1020
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
OpenPOWER on IntegriCloud