From: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: phil@ipom.com, usb-storage@lists.one-eyed-alien.net,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [usb-storage] [PATCH] [resend] unusual_devs.h: Fix capacity for SL11R-IDE 2.6c
Date: Wed, 24 Feb 2010 11:29:59 -0800 [thread overview]
Message-ID: <20100224192959.GJ20232@one-eyed-alien.net> (raw)
In-Reply-To: <201002241141.10103.linux@rainbow-software.org>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
On Wed, Feb 24, 2010 at 11:41:08AM +0100, Ondrej Zary wrote:
> SL11R-IDE 2.6c (at least) reports wrong capacity (one sector more).
> Reading that last sector causes the device not to work anymore (and looks
> like HAL or something does that automatically after plugging in):
> sd 5:0:0:0: [sdc] Device not ready
> sd 5:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08
> sd 5:0:0:0: [sdc] Sense Key : 0x2 [current]
> sd 5:0:0:0: [sdc] ASC=0x0 ASCQ=0x0
> sd 5:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 04 a8 b5 70 00 00 01 00
>
> Add unusual_devs entry to fix the capacity.
Why not just adjust the version range of the entry above where you added a
new one?
If you just expand the upper version of the previous entry, it should cover
both devices.
Matt
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
Oh BAY-bee.
-- Dust Puppy to Greg
User Friendly, 12/13/1997
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2010-02-24 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 10:41 Ondrej Zary
2010-02-24 19:29 ` Matthew Dharm [this message]
2010-02-24 21:22 ` [usb-storage] " Ondrej Zary
2010-02-24 22:47 ` Matthew Dharm
2010-02-27 19:11 ` Phil Dibowitz
2010-02-27 20:33 ` Matthew Dharm
2010-02-25 19:03 ` Phil Dibowitz
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=20100224192959.GJ20232@one-eyed-alien.net \
--to=mdharm-kernel@one-eyed-alien.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=phil@ipom.com \
--cc=usb-storage@lists.one-eyed-alien.net \
/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
all inboxes | Powered by JetHome®