James Bottomley wrote:
On Tue, 2004-10-26 at 14:08, Mike Christie wrote:
The null state and and oops are becuase of this
http://marc.theaimsgroup.com/?l=linux-scsi&m=109733573729283&w=2
Oh yeah. that patch is not correct, but if you correctly modify it to
use device_for_each_child per Christoph's s
James Bottomley wrote:
On Wed, 2003-10-29 at 09:24, Alan Stern wrote:
no matter which USB-storage-device I attach (tried CD-ROM,
Flash Card Reader and memory stick) I get a new scsi host
every time i plug a device in.
so when changing devices for several times I finally end up
with /dev/scsi/hos
Matthew Dharm wrote:
On Sat, Jun 21, 2003 at 09:54:46PM -0500, James Bottomley wrote:
@@ -702,7 +692,7 @@
printk("%s: scsi-1 drive\n", cd->cdi.name);
return;
}
- n = buffer[3] + 4;
+ n = rc;
cd->cdi.speed = ((buffer[n + 8] << 8) + buffer[
Matthew Dharm wrote:
On Sat, Mar 22, 2003 at 11:39:05PM -0800, Linus Torvalds wrote:
How about making the SCSI stuff pass a "common" flag (or "required") down
with the command? Then, a emulated thing could just decide to punt all
commands with an immediate failure if they aren't marked "required"
Oliver Neukum wrote:
>
>
I simply don't trust the SCSI layer. I've had to much trouble with it
already.
Hopefully we have some better building blocks and
clearer code in 2.5 to look at this problem in the SCSI
subsystem again.
The first thing a LLDD should do when it _knows_ the device
is gone
[EMAIL PROTECTED] wrote:
>
> >Life would be easier if the scsi subsystem would just report which SCSI
> >device (uniquely identified by the controller,bus,target,unit tuple) belongs
> >to which high-level device. The information is available in the kernel.
> >
> >Attached patc
