From: "Richard Schütz" <r.schtz@t-online.de>
To: linux-usb@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
Sergey Vlasov <vsu@altlinux.ru>, Greg KH <gregkh@suse.de>,
Matthew Dharm <mdharm-usb@one-eyed-alien.net>
Subject: Re: [PATCH v2] USB: usb-storage: unusual_devs update for TrekStor DataStation maxi g.u external hard drive enclosure
Date: Fri, 07 Jan 2011 13:07:47 +0100 [thread overview]
Message-ID: <4D270213.7000104@t-online.de> (raw)
In-Reply-To: <4D11FD18.6090100@t-online.de>
> The TrekStor DataStation maxi g.u external hard drive enclosure uses a
> JMicron USB to SATA chip which needs the US_FL_IGNORE_RESIDUE flag to work
> properly.
>
> Signed-off-by: Richard Schütz <r.schtz@t-online.de>
> ---
>
> Applies to 2.6.37-rc7 now.
>
> --- a/drivers/usb/storage/unusual_devs.h 2010-12-21 20:26:40.000000000 +0100
> +++ b/drivers/usb/storage/unusual_devs.h 2010-12-22 13:37:58.438818902 +0100
> @@ -1872,6 +1872,15 @@ UNUSUAL_DEV( 0x1908, 0x3335, 0x0200, 0x0
> USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> US_FL_NO_READ_DISC_INFO ),
>
> +/* Patch by Richard Schütz <r.schtz@t-online.de>
> + * This external hard drive enclosure uses a JMicron chip which
> + * needs the US_FL_IGNORE_RESIDUE flag to work properly. */
> +UNUSUAL_DEV( 0x1e68, 0x001b, 0x0000, 0x0000,
> + "TrekStor GmbH & Co. KG",
> + "DataStation maxi g.u",
> + USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> + US_FL_IGNORE_RESIDUE | US_FL_SANE_SENSE ),
> +
> UNUSUAL_DEV( 0x2116, 0x0320, 0x0001, 0x0001,
> "ST",
> "2A",
>
Why was this simple patch not accepted (yet)? Is something wrong with it?
Discussion was here:
http://thread.gmane.org/gmane.linux.usb.general/40545
http://thread.gmane.org/gmane.linux.usb.general/40550
--
Richard Schütz
prev parent reply other threads:[~2011-01-07 12:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 13:28 [PATCH v2] USB: usb-storage: unusual_devs update for TrekStor DataStation maxi g.u external hard drive enclosure Richard Schütz
2011-01-07 12:07 ` Richard Schütz [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=4D270213.7000104@t-online.de \
--to=r.schtz@t-online.de \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=stern@rowland.harvard.edu \
--cc=vsu@altlinux.ru \
/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.