I saw the NEW_TRANS code and that seems definitely the way to code. A
lot of work though.
> There are other commands that can get sent, though -- inquiry, test unit
> ready, and start/stop unit are all 6 byte commands, and there are no 10
> byte SCSI equivalents. So how do you handle those now?
On Wed, Apr 10, 2002 at 21:50:33 +0200, Nick Hibma wrote:
>
> The problem is that we emulate ATAPI and UFI command sets through
> converting SCSI commands. These command sets both do not have 6 byte
> commands.
>
> The solution is to have the umass driver pass a quirk back to the CAM
> layer dyn
Cheers, I've closed the PR as the same thing has already been done in
CURRENT by jhb. Thanks for pointing me at the PR though!
Nick
On Wed, 10 Apr 2002, Lars Eggert wrote:
> There is some (maybe) related code that has been sitting for a while in
> PR misc/32490 (http://www.freebsd.org/cgi/quer
There is some (maybe) related code that has been sitting for a while in
PR misc/32490 (http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/32490)
Lars
--
Lars Eggert <[EMAIL PROTECTED]> Information Sciences Institute
http://www.isi.edu/larse/ University of Southern Califor
Oh, and RBC of course. Anyway, you get my point I guess.
Nick
>
> The class of devices that does not accept 6 byte commands is well known:
> ATAPI and UFI.
>
> Nick
>
> > It seems to me that umass_scsi_transform() in umass.c is
> > the place intended for this kind of things. After the
> > firs
minimum_cmd_size is only used for read_write commands, not for others
like MODE_SENSE_6 and friends.
Nick
> > As in, try a 6 byte command, and if that fails try a 10 byte command
> > instead?
>
> As in, if it fails to reset, then
>
> sc->softc->minimum_cmd_size = 10;
> printf( "aut
The class of devices that does not accept 6 byte commands is well known:
ATAPI and UFI.
Nick
> It seems to me that umass_scsi_transform() in umass.c is
> the place intended for this kind of things. After the
> first failure (which is detected in umass_bbb_state()),
> a flag (quirk) should be s
The problem is that we emulate ATAPI and UFI command sets through
converting SCSI commands. These command sets both do not have 6 byte
commands.
The solution is to have the umass driver pass a quirk back to the CAM
layer dynamically for these devices. Any takers for an implementation
that doesn'
On Thu, Feb 07, 2002 at 09:46:28PM +0100, Oliver Fromme wrote:
> Hi,
>
> I've got a small problem with a nice little thing called
> "USB Memorybird" (Fujitsu-Siemens) ...
>
I've created a patch to RELENG_4 to include the USB advances that are in
-current but which haven't been MFC'd yet. It's a
Chris Dillon wrote:
> On Sat, 9 Feb 2002, Oliver Fromme wrote:
> > I think that would be a very good idea. The boot software issue
> > is negligible, because there aren't any USB devices you can boot
> > from.
>
> You mean can't boot from USB devices in just FreeBSD, or anywhere?
> I've
On Sat, 9 Feb 2002, Oliver Fromme wrote:
> I think that would be a very good idea. The boot software issue
> is negligible, because there aren't any USB devices you can boot
> from.
You mean can't boot from USB devices in just FreeBSD, or anywhere?
I've not actually tried it yet, but many mothe
On 09-Feb-02 Josef Karthauser wrote:
> On Sat, Feb 09, 2002 at 01:16:46PM +0100, Oliver Fromme wrote:
>
>> John Baldwin wrote:
>> > On 07-Feb-02 Gérard Roudier wrote:
>> > > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI
>> > > block
>> > > devices in order to accomodate
On Sat, Feb 09, 2002 at 01:16:46PM +0100, Oliver Fromme wrote:
> John Baldwin wrote:
> > On 07-Feb-02 Gérard Roudier wrote:
> > > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI block
> > > devices in order to accomodate softwares as boot software for example that
> > > ma
John Baldwin wrote:
> On 07-Feb-02 Gérard Roudier wrote:
> > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI block
> > devices in order to accomodate softwares as boot software for example that
> > may not be upgradable on systems still in use. Softwares that are
> > main
On 07-Feb-02 Gérard Roudier wrote:
>
> On Thu, 7 Feb 2002, Josef Karthauser wrote:
>
>> On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote:
>> > >
>> > > IIRC this problem is being addressed at a more fundamental level on
>> > > -current, by adding a 6-byte-to-10-byte READ command tr
Gérard Roudier wrote:
> The performance issue is certainly negligible (~ 1 micro-second), and as I
> wrote above it only applies to the first GB of disks. (Additionnaly, the
> tranfer length is limited to 256 sectors)
>
> So, unless we want to advertise about best support for 1 GB hard disks,
> b
On Fri, 8 Feb 2002, Terry Lambert wrote:
> Gérard Roudier wrote:
> > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI block
> > devices in order to accomodate softwares as boot software for example that
> > may not be upgradable on systems still in use.
>
> Not a real problem
There is hardly a performance issue about 10-byte READ, considering the
size of a whole transaction (command + transfer) is at least as large as
a disk sector (512 bytes on most modern drives); a four-byte difference
is almost nothing here.
IMHO the best way is to `try a 10-byte READ first, and i
Gérard Roudier wrote:
> A couple of READ/WRITE 6 byte commands are still mandatory for SCSI block
> devices in order to accomodate softwares as boot software for example that
> may not be upgradable on systems still in use.
Not a real problem, since if the device doesn't support
the 5 byte comman
Oliver Fromme wrote:
> > Could this be "auto-quirked"?
[ ... ]
> It seems to me that umass_scsi_transform() in umass.c is
> the place intended for this kind of things. After the
> first failure (which is detected in umass_bbb_state()),
> a flag (quirk) should be set in the softc, and afterwards
On Thu, 7 Feb 2002, Josef Karthauser wrote:
> On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote:
> > >
> > > IIRC this problem is being addressed at a more fundamental level on
> > > -current, by adding a 6-byte-to-10-byte READ command translator
> > > somewhere in the abstraction la
Terry Lambert wrote:
> "Eugene M. Kim" wrote:
> > This is a common problem of most umass devices that implements BBB
> > protocol, and arises from the fact that those devices don't understand
> > the 6-byte SCSI READ command. You can add a quirk entry to
> > src/sys/cam/scsi_da.c (refer to
On Thu, Feb 07, 2002 at 04:46:17PM -0800, Terry Lambert wrote:
> I think the person with the problem needs to turn on the
> CAM debugging, or a CAM-head needs to become involved. The
> workaround works, for now, but it's frustrating, knowing
> that the next time anyone OEMs the same hardware and
"Eugene M. Kim" wrote:
> The USB development team seems to have something similar to your idea in
> their mind; see the comment for rev 1.47 of:
>
>
>http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/umass.c?f=u&only_with_tag=MAIN&logsort=date
>
> It mentions about `da(4) becoming more inte
Josef Karthauser wrote:
> On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote:
> > > IIRC this problem is being addressed at a more fundamental level on
> > > -current, by adding a 6-byte-to-10-byte READ command translator
> > > somewhere in the abstraction layer.
> >
> > Could this be "
On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote:
>
>
> "Eugene M. Kim" wrote:
> >
> > This is a common problem of most umass devices that implements BBB
> > protocol, and arises from the fact that those devices don't understand
> > the 6-byte SCSI READ command. You can add a quir
On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote:
> >
> > IIRC this problem is being addressed at a more fundamental level on
> > -current, by adding a 6-byte-to-10-byte READ command translator
> > somewhere in the abstraction layer.
>
> Could this be "auto-quirked"?
>
As in, try
"Eugene M. Kim" wrote:
>
> This is a common problem of most umass devices that implements BBB
> protocol, and arises from the fact that those devices don't understand
> the 6-byte SCSI READ command. You can add a quirk entry to
> src/sys/cam/scsi_da.c (refer to quirk entries that have DA_Q_NO_6_
Eugene M. Kim wrote:
> This is a common problem of most umass devices that implements BBB
> protocol, and arises from the fact that those devices don't understand
> the 6-byte SCSI READ command. You can add a quirk entry to
> src/sys/cam/scsi_da.c (refer to quirk entries that have DA_Q_NO_6_
This is a common problem of most umass devices that implements BBB
protocol, and arises from the fact that those devices don't understand
the 6-byte SCSI READ command. You can add a quirk entry to
src/sys/cam/scsi_da.c (refer to quirk entries that have DA_Q_NO_6_BYTE).
IIRC this problem is being
Hi,
I've got a small problem with a nice little thing called
"USB Memorybird" (Fujitsu-Siemens) ...
It is bascially a 64 MB Flash chip in a small plastic pen
that you can carry with your keys. It doesn't need any
battery and you can plug it directly into a USB socket.
Very neat.
Works without
31 matches
Mail list logo
