Hi all,
I have here a buggy firewire bridge (Prolific PL3507) which requires that each
'INQUIRY' command is followed by a 'READ CAPACITY' command. Otherwise any read
will return invalid data (the payload is preceded by 36 empty bytes).
How to fix this? Sure one could add a hack to sbp2.c
On Tue, Jan 08, 2008 at 02:43:34PM +0100, Hannes Reinecke wrote:
Hi all,
I have here a buggy firewire bridge (Prolific PL3507) which requires that
each 'INQUIRY' command is followed by a 'READ CAPACITY' command. Otherwise
any read will return invalid data (the payload is preceded by 36
Matthew Wilcox wrote:
On Tue, Jan 08, 2008 at 02:43:34PM +0100, Hannes Reinecke wrote:
I have here a buggy firewire bridge (Prolific PL3507) which requires
that each 'INQUIRY' command is followed by a 'READ CAPACITY' command.
Otherwise any read will return invalid data (the payload is preceded
On Tue, 2008-01-08 at 18:56 +0100, Stefan Richter wrote:
Matthew Wilcox wrote:
On Tue, Jan 08, 2008 at 02:43:34PM +0100, Hannes Reinecke wrote:
I have here a buggy firewire bridge (Prolific PL3507) which requires
that each 'INQUIRY' command is followed by a 'READ CAPACITY' command
On Tue, Jan 08, 2008 at 06:56:11PM +0100, Stefan Richter wrote:
It's hald or something like that.
Can't we get hald to look at the cached results of the inquiry command,
handily available through sysfs?
Matthew Wilcox wrote:
I have a hard time thinking this needs to be handled generically
Matthew Wilcox wrote:
According to SPC4r05a, READ CAPACITY(10) (opcode 25) is Mandatory for D,
W and O. READ CAPACITY (opcode 25) is Optional for R. READ CARD
CAPACITY (also opcode 25) is Mandatory for K.
[...]
According to this table (D.2 for anyone following along at home), RBC
devices
On Tue, Jan 08, 2008 at 12:10:47PM -0600, James Bottomley wrote:
Not to hijack the thread, but this is getting to be a broken record. I
was dealing only a few days ago with a camera presenting as a mass
storage device that was then crashing and going offline. I looked at
the dmesg trace
On Tue, 2008-01-08 at 15:10 -0500, David Zeuthen wrote:
Perhaps if you can point to what SCSI commands hald are sending it would
be easier to debug. Any other ideas?
Also, if you can identify the name of the process image doing this it
would be helpful. I know both libipoddevice and libgpod
8 matches
Mail list logo
