From: Matthieu CASTET <castet.matthieu@free.fr>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Milan Svoboda" <milan.svoboda@centrum.cz>,
"Sarah Sharp" <sarah.a.sharp@linux.intel.com>,
"USB list" <linux-usb@vger.kernel.org>,
"USB Storage List" <usb-storage@lists.one-eyed-alien.net>,
"SCSI development list" <linux-scsi@vger.kernel.org>,
"Richard SchÃŒtz" <r.schtz@t-online.de>
Subject: Re: [usb-storage] Re: usb disk recognized but fails
Date: Wed, 29 Jan 2014 14:07:08 +0100 [thread overview]
Message-ID: <20140129140708.5bd372a1@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1401241056050.1129-100000@iolanthe.rowland.org>
Hi,
Le Fri, 24 Jan 2014 11:07:01 -0500,
Alan Stern <stern@rowland.harvard.edu> a écrit :
> Matthieu:
>
> Can you help with this problem?
>
>
> You were right; that driver caused the problem.
>
> Matthieu Castet wrote the Cypress-ATACB driver, so maybe he can help.
>
> As shown above, this device matches the last entry in the
> unusual_cypress.h file (the one named "Super Top"). Not shown here is
The "Super Top" id were added later. When I did the driver I only
check the datasheet of the fisrt two entry.
Looking at the git log, we can see there already was corruption
detected by this entry [1].
Without knowing what chip is in the "super top" bridge, I propose to
remove the entry : it seems to cause too much trouble.
An alternative could be to enable it only for bcdDevice
1.60.
Matthieu
[1]
USB: usb-storage: unusual_devs update for Super TOP SATA bridge
The current entry in unusual_cypress.h for the Super TOP SATA bridge devices
seems to be causing corruption on newer revisions of this device. This has
been reported in Arch Linux and Fedora. The original patch was tested on
devices with bcdDevice of 1.60, whereas the newer devices report bcdDevice
as 2.20. Limit the UNUSUAL_DEV entry to devices less than 2.20.
This fixes https://bugzilla.redhat.com/show_bug.cgi?id=909591
The Arch Forum post on this is here:
https://bbs.archlinux.org/viewtopic.php?id=152011
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-01-29 13:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 6:57 [usb-storage] Re: usb disk recognized but fails Milan Svoboda
2014-01-24 16:07 ` Alan Stern
2014-01-26 20:17 ` Milan Svoboda
2014-01-29 13:07 ` Matthieu CASTET [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-21 20:56 Milan Svoboda
[not found] ` <20140121215636.F5422382-aRb0bU7PRFPrBKCeMvbIDA@public.gmane.org>
2014-01-21 22:12 ` [usb-storage] " Alan Stern
2014-01-22 19:19 ` Milan Svoboda
2014-01-22 19:59 ` Alan Stern
2014-01-22 21:07 ` Milan Svoboda
[not found] ` <20140122220717.D61BDE5D-aRb0bU7PRFPrBKCeMvbIDA@public.gmane.org>
2014-01-22 21:34 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1401221632200.1310-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2014-01-23 12:08 ` Milan Svoboda
2014-01-23 16:54 ` Alan Stern
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=20140129140708.5bd372a1@free.fr \
--to=castet.matthieu@free.fr \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=milan.svoboda@centrum.cz \
--cc=r.schtz@t-online.de \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stern@rowland.harvard.edu \
--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