From: Pete Zaitcev <zaitcev@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, Pete Zaitcev <zaitcev@redhat.com>
Subject: Re: [BK PATCH] Still more USB changes for 2.5.31
Date: Wed, 21 Aug 2002 19:07:19 -0400 [thread overview]
Message-ID: <20020821190719.B25260@devserv.devel.redhat.com> (raw)
In-Reply-To: <20020821224940.GA3099@kroah.com>; from greg@kroah.com on Wed, Aug 21, 2002 at 03:49:40PM -0700
> From: Greg KH <greg@kroah.com>
> Date: Wed, 21 Aug 2002 15:49:40 -0700
> ChangeSet@1.514, 2002-08-21 13:53:49-07:00, mdharm-usb@one-eyed-alien.net
> [PATCH] PATCH: fix devices which don't support START_STOP
>
> Based on my discussions with Pete Zaitcev <zaitcev@redhat.com>, I'm
> convinced that globally re-writing the START_STOP command into a
> TEST_UNIT_READY command is a good idea. This is supported by the fact
> that:
>
> (1) Lots of devices don't support START_STOP
> (2) Those that do support it often don't do a good job
> (3) Win/Mac will never send these commands over a USB bus
>
> So, here's a patch that re-writes them into Test Unit Ready commands.
For the record, I do not think the blanket rewrite is a good idea.
I did it for broken devices only, governed by a new quirk flag,
and this is what we currently ship.
Matt reviewed what I did, but decided it would be cleaner
to rewrite commands always. I did not go on a roll against it because:
1. 2.5 is supposed to be somewhat broken;
2. Matt is the module maintainer, he knows what he's doing.
-- Pete
prev parent reply other threads:[~2002-08-21 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 22:49 [BK PATCH] Still more USB changes for 2.5.31 Greg KH
2002-08-21 23:07 ` Pete Zaitcev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020821190719.B25260@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.