public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wheeler <matt@yurisko.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	Mike Anderson <andmike@us.ibm.com>,
	Javier Marcet <lists@marcet.info>,
	USB Storage list <usb-storage@lists.one-eyed-alien.net>,
	SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: PATCH: (as333) BLIST flag for non-lockable devices
Date: Sun, 27 Jun 2004 10:52:35 +1000	[thread overview]
Message-ID: <40DE1A53.8060004@yurisko.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0406251209580.1147-100000@ida.rowland.org>


Alan,
    This patch worked without any problems that I could see. I was able 
to mount, copy files to and from and eject the camera. Let me know if 
you would like me to run any more tests or send debugging logs etc.

    Matt

Alan Stern wrote:

>On Wed, 23 Jun 2004, Mike Anderson wrote:
>
>  
>
>>Since SCSI already has the device list it would seem like we would
>>possibly add a new flag like was done for mode sense. As this is not a
>>transport issue I would assume we would not want to add flags in
>>usb/storage, but handle it in the mid-layer as a SCSI protocol
>>non-compliance.
>>    
>>
>
>Here is a patch that implements this suggestion.  It's rather similar to 
>the one that Javier Marcet wrote back in January, in
>
>http://marc.theaimsgroup.com/?l=linux-usb-users&m=107345268526718&w=2
>
>Matthew, does this patch work for your digital camera?
>
>Alan Stern
>
>
>
>Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
>
>===== include/scsi/scsi_devinfo.h 1.5 vs edited =====
>--- 1.5/include/scsi/scsi_devinfo.h	Sun May 30 04:51:19 2004
>+++ edited/include/scsi/scsi_devinfo.h	Fri Jun 25 11:53:20 2004
>@@ -24,4 +24,5 @@
> #define BLIST_REPORTLUN2	0x20000	/* try REPORT_LUNS even for SCSI-2 devs
>  					   (if HBA supports more than 8 LUNs) */
> #define BLIST_NOREPORTLUN	0x40000	/* don't try REPORT_LUNS scan (SCSI-3 devs) */
>+#define BLIST_NOT_LOCKABLE	0x80000	/* don't use PREVENT-ALLOW commands */
> #endif
>===== drivers/scsi/scsi_devinfo.c 1.9 vs edited =====
>--- 1.9/drivers/scsi/scsi_devinfo.c	Sat Jun 19 07:49:23 2004
>+++ edited/drivers/scsi/scsi_devinfo.c	Fri Jun 25 12:07:06 2004
>@@ -158,8 +158,11 @@
> 	{"IOMEGA", "Io20S         *F", NULL, BLIST_KEY},
> 	{"INSITE", "Floptical   F*8I", NULL, BLIST_KEY},
> 	{"INSITE", "I325VM", NULL, BLIST_KEY},
>+	{"iRiver", "iFP Mass Driver", NULL, BLIST_NOT_LOCKABLE | BLIST_INQUIRY_36},
> 	{"LASOUND", "CDX7405", "3.10", BLIST_MAX5LUN | BLIST_SINGLELUN},
> 	{"MATSHITA", "PD-1", NULL, BLIST_FORCELUN | BLIST_SINGLELUN},
>+	{"MATSHITA", "DMC-LC5", NULL, BLIST_NOT_LOCKABLE | BLIST_INQUIRY_36},
>+	{"MATSHITA", "DMC-LC40", NULL, BLIST_NOT_LOCKABLE | BLIST_INQUIRY_36},
> 	{"Medion", "Flash XL  MMC/SD", "2.6D", BLIST_FORCELUN},
> 	{"MegaRAID", "LD", NULL, BLIST_FORCELUN},
> 	{"MICROP", "4110", NULL, BLIST_NOTQ},
>===== drivers/scsi/scsi_scan.c 1.61 vs edited =====
>--- 1.61/drivers/scsi/scsi_scan.c	Mon Jun 21 12:58:41 2004
>+++ edited/drivers/scsi/scsi_scan.c	Fri Jun 25 11:56:28 2004
>@@ -661,6 +661,9 @@
> 	if (*bflags & BLIST_MS_192_BYTES_FOR_3F)
> 		sdev->use_192_bytes_for_3f = 1;
> 
>+	if (*bflags & BLIST_NOT_LOCKABLE)
>+		sdev->lockable = 0;
>+
> 	if(sdev->host->hostt->slave_configure)
> 		sdev->host->hostt->slave_configure(sdev);
> 
>
>  
>


  reply	other threads:[~2004-06-27  0:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22 21:05 Windows and non-lockable devices (fwd) Alan Stern
2004-06-23 19:14 ` Mike Anderson
2004-06-25 16:14   ` PATCH: (as333) BLIST flag for non-lockable devices Alan Stern
2004-06-27  0:52     ` Matthew Wheeler [this message]
2004-06-27 23:10     ` PATCH: " Javier Marcet
2004-06-28 15:54       ` Alan Stern
2004-06-28 20:24         ` Javier Marcet

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=40DE1A53.8060004@yurisko.net \
    --to=matt@yurisko.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=andmike@us.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lists@marcet.info \
    --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