From: Oliver Neukum <oneukum@suse.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: hare@suse.de, linux-scsi@vger.kernel.org
Subject: Re: READ_CAPACITY_16 vs. READ_CAPACITY_10
Date: Tue, 10 Sep 2013 22:44:18 +0200 [thread overview]
Message-ID: <1378845858.24378.1.camel@linux-fkkt.site> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1309101322390.1075-100000@iolanthe.rowland.org>
On Tue, 2013-09-10 at 13:25 -0400, Alan Stern wrote:
> On Tue, 10 Sep 2013, Oliver Neukum wrote:
>
> > Hi Hannes,
> >
> > you objected to this patch saying there's a possibilty that
> > HS devices may also need this feature, which would require
> > a quirk. Does this mean that the patch is acceptable only
> > with an additional predefined quirk, or do you insist that all
> > devices be handled with quirks?
>
> Indeed, we already know of one or two high-speed devices that suffer
> from this bug:
>
> http://marc.info/?l=linux-usb&m=133586313307042&w=2
>
> This may influence your decision. I'm not certain whether it is
> important enough to merit a new quirk flag, but people experiencing the
> problem may have some strong opinions.
What is the alternative?
I think we can be sure that no drive enclosure will crash
with READ_CAPACITY_16. I am not sure about card readers.
Does anybody know what Windows does?
Regards
Oliver
next prev parent reply other threads:[~2013-09-10 20:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 13:56 READ_CAPACITY_16 vs. READ_CAPACITY_10 Oliver Neukum
2013-09-10 17:25 ` Alan Stern
2013-09-10 20:44 ` Oliver Neukum [this message]
2013-09-11 14:14 ` Alan Stern
2013-09-11 15:05 ` Oliver Neukum
2013-09-11 15:42 ` Alan Stern
2013-09-11 15:56 ` Steve Magnani
2013-09-12 5:47 ` Hannes Reinecke
2013-09-16 12:41 ` Oliver Neukum
2013-09-12 5:56 ` Hannes Reinecke
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=1378845858.24378.1.camel@linux-fkkt.site \
--to=oneukum@suse.de \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).