On Sat, Mar 22, 2003 at 10:37:32AM -0700, Pat LaVarre wrote:
> > > 3) By switching to the abbreviation Sig from the
> > > abbreviation S for what in the merely public standard
> > > appears twice as "Signature" we're just torturing
> > > newbies for fun.
> >
> > Actually, we're trying to keep the
> > 3) By switching to the abbreviation Sig from the
> > abbreviation S for what in the merely public standard
> > appears twice as "Signature" we're just torturing
> > newbies for fun.
>
> Actually, we're trying to keep the debug data a little concise
Even as a newbie I can see this works well.
On Fri, Mar 21, 2003 at 05:46:24PM -0700, Pat LaVarre wrote:
> We haven't named the bridge chip yet, have we? Anybody
> got a utility that can send vendor-specific commands,
> read unindexed string descriptors, etc.? Often
> different genetic families of Usb Mass chips can be
> fingerprinted that
On Fri, Mar 21, 2003 at 05:20:58PM -0700, Pat LaVarre wrote:
> > > "usb-storage: > usb_stor_transfer_partial(): xfer 4096 bytes"
> > >
> > > AIUI this message is logged before any data moves
> > > and just indicates how much information is
> > > expected.
> >
> > ... means a request for copying 409
We haven't named the bridge chip yet, have we? Anybody
got a utility that can send vendor-specific commands,
read unindexed string descriptors, etc.? Often
different genetic families of Usb Mass chips can be
fingerprinted that way.
> From: Dave Turner [mailto:[EMAIL PROTECTED]
> Sent: Fri 3/21/2
> Given ... your opinion that it's a firmware problem
We didn't just lose our test hardware, did we? Tell
me no? Please?
(-: As a firmware engineer, I'm prepared to claim,
"it's nearly always a host problem, not a firmware
problem". :-) Even objectively speaking, we know here
talking enough li
On Fri, Mar 21, 2003 at 08:39:12PM +, Dave Turner wrote:
> On Fri, 21 Mar 2003 at 1:25pm, Pat LaVarre wrote:
> > I presume Linux `dd` can't be persuaded to try reading from a volume
> > that hasn't yet been mounted?
>
> Yep, 'dd if=/dev/scsi/.../disc ...' succeeds on a freshly-inserted card.
>
On Fri, Mar 21, 2003 at 01:25:00PM -0700, Pat LaVarre wrote:
> > I have snipped part of the log ...
>
> Re guessing what Windows may be doing that works ...
>
> Anybody know the bInterfaceClass ...SubClass
> ...Protocol involved here?
>
> Specifically does bInterfaceProtocol here != x06 Scsi?
> I have snipped part of the log ...
Re guessing what Windows may be doing that works ...
Anybody know the bInterfaceClass ...SubClass
...Protocol involved here?
Specifically does bInterfaceProtocol here != x06 Scsi?
> ...
Re guessing what Linux may be doing that breaks ...
Would just s
