> ... multi LUN ... Zip 250 ... valid. But ... damned rude ...
Agreed, I think.
I'd say, should a device be so unfortunate as to encounter a
non-compliant host, then I prefer the Shuttle choice here for the
"not specified" response to a "valid but not meaningful" CBW:
have the device return a "valid but not meaningful" CSW.
I trust the Linux stack by now has come into compliance
here? The class-specific Get Max LUN response has to bless
a LUN before it goes to the device in a CBW?
> I mean, if you want me to reset the device, then don't STALL,
> go into indefinite NAK on all bulk endpoints.
Eh???
The host doesn't understand indefinite NAK until after a timeout.
ACK and STALL, by contrast, are immediately understood?
> STALL (in terms of the spec) has the semantic meaning
> of 'I heard you correctly, but I can't right now' ...
> the indefinite NAK means 'I'm not even hearing you'.
Eh??? ACK means pass, STALL means fail, NAK means
other? This is why indefinite NAK is so evil - the host
can't ever know when to give up?
>From USB 1.1 8.3.1:
ACK: Receiver accepts error-free data packet
NAK: Rx device cannot accept data or Tx device cannot send data
STALL: Endpoint is halted or a control pipe request is not supported.
x4402 Pat LaVarre of iOmega [EMAIL PROTECTED] http://members.aol.com/ppaatt/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
