From: Marek Michalkiewicz <marekm@amelek.gda.pl>
To: Greg KH <greg@kroah.com>
Cc: Marek Michalkiewicz <marekm@amelek.gda.pl>,
marcelo@conectiva.com.br, mdharm-usb@one-eyed-alien.net,
mwilck@freenet.de, linux-kernel@vger.kernel.org
Subject: Re: [patch] USB storage: Datafab KECF-USB, Sagatek DCS-CF
Date: Wed, 26 Jun 2002 18:03:26 +0200 (CEST) [thread overview]
Message-ID: <E17NFGQ-00069b-00@alf.amelek.gda.pl> (raw)
In-Reply-To: <20020626152213.GE4611@kroah.com>
> 2.4.19-final is too close. I'll trust Matt to tell me if the patch is
> ok or not technically, as it's his code. I'd also prefer for you to
> work through him, as he is the maintainer, and not try to send things
> like this to Marcelo directly (read Documentation/SubmittingPatches).
OK, and sorry if sending directly to Marcelo was the wrong thing to do
(I wouldn't have done that if the patch might affect other devices).
I've just played a little more with this device, and here is the really
minimal patch (new entry in unusual_devs.h for the flags, no other
changes in the code) - there should be no doubt if it's OK technically,
as it makes a device work that previously didn't...
The device I have is called "Sagatek DCS-CF", but the name "Sagatek"
is only on the packaging, and the "DCS-CF" is only on a small sticker
at tbe bottom side. So I left the name "Datafab" in the entry,
assuming it's really the same device inside (same vendor:product ID)
so I guess it's a Datafab product and Sagatek really just sells it...
Please at least consider this - later, the larger issue of limiting
INQUIRY to 36 bytes might have a different solution (in the SCSI code),
but in the meantime this micro-patch is sufficient. Thanks.
Regards,
Marek
--- linux/drivers/usb/storage/unusual_devs.h.orig Tue Jun 25 15:38:23 2002
+++ linux/drivers/usb/storage/unusual_devs.h Wed Jun 26 17:45:59 2002
@@ -461,6 +461,13 @@
US_FL_MODE_XLATE ),
#endif
+/* aka Sagatek DCS-CF */
+UNUSUAL_DEV( 0x07c4, 0xa400, 0x0000, 0xffff,
+ "Datafab",
+ "KECF-USB",
+ US_SC_SCSI, US_PR_BULK, NULL,
+ US_FL_FIX_INQUIRY | US_FL_MODE_XLATE | US_FL_START_STOP ),
+
/* Casio QV 2x00/3x00/4000/8000 digital still cameras are not conformant
* to the USB storage specification in two ways:
* - They tell us they are using transport protocol CBI. In reality they
next prev parent reply other threads:[~2002-06-26 16:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 21:44 Marek Michalkiewicz
2002-06-26 14:57 ` Greg KH
2002-06-26 15:14 ` Marek Michalkiewicz
2002-06-26 15:22 ` Greg KH
2002-06-26 16:03 ` Marek Michalkiewicz [this message]
2002-08-04 13:22 ` Marek Michalkiewicz
2002-08-05 15:56 ` Greg KH
2002-08-29 13:57 ` Marek Michalkiewicz
2002-09-01 20:19 ` Martin Wilck
2002-09-02 6:41 ` Marek Michalkiewicz
2002-09-02 8:27 ` Andries Brouwer
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=E17NFGQ-00069b-00@alf.amelek.gda.pl \
--to=marekm@amelek.gda.pl \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=mwilck@freenet.de \
/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®