linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 2.6.22-rc7] libata: quirk IOMEGA ZIP 250 ATAPI FLOPPY
@ 2007-07-05  3:31 Tejun Heo
  2007-07-05 12:39 ` Alan Cox
  2007-07-11  1:38 ` Jeff Garzik
  0 siblings, 2 replies; 5+ messages in thread
From: Tejun Heo @ 2007-07-05  3:31 UTC (permalink / raw)
  To: Jeff Garzik, linux-ide, bruinjm, alan

The Zip 250 which chokes on MWDMA SET_XFERMODE sometimes have "Floppy"
appeneded to its model number.  Quirk it too.

  http://bugzilla.kernel.org/show_bug.cgi?id=8563

Signed-off-by: Tejun Heo <htejun@gmail.com>
Cc: Hans de Bruin <bruinjm@xs4all.nl>
---
It seems the Zip 250 mwdma failure on libata doesn't seem to be
libata's fault after all.  IDE also fails SET_XFERMODE on this drive
but IDE simply ignores the error and continues to operate in MWDMA
mode, so I guess we can remove the 'temporary fix' comment or add
another quirk type - ATA_HORKAGE_SETXFER_MAY_FAIL - and use it.

Anyways, for the time being, this should do.

 drivers/ata/libata-core.c |    2 ++
 1 file changed, 2 insertions(+)

Index: work/drivers/ata/libata-core.c
===================================================================
--- work.orig/drivers/ata/libata-core.c
+++ work/drivers/ata/libata-core.c
@@ -3774,6 +3774,8 @@ static const struct ata_blacklist_entry 
 	{ "SAMSUNG CD-ROM SN-124","N001",	ATA_HORKAGE_NODMA },
 	{ "Seagate STT20000A", NULL,		ATA_HORKAGE_NODMA },
 	{ "IOMEGA  ZIP 250       ATAPI", NULL,	ATA_HORKAGE_NODMA }, /* temporary fix */
+	{ "IOMEGA  ZIP 250       ATAPI       Floppy",
+				NULL,		ATA_HORKAGE_NODMA },
 
 	/* Weird ATAPI devices */
 	{ "TORiSAN DVD-ROM DRD-N216", NULL,	ATA_HORKAGE_MAX_SEC_128 },

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH 2.6.22-rc7] libata: quirk IOMEGA ZIP 250 ATAPI FLOPPY
  2007-07-05  3:31 [PATCH 2.6.22-rc7] libata: quirk IOMEGA ZIP 250 ATAPI FLOPPY Tejun Heo
@ 2007-07-05 12:39 ` Alan Cox
  2007-07-05 23:53   ` Jeff Garzik
  2007-07-11  1:38 ` Jeff Garzik
  1 sibling, 1 reply; 5+ messages in thread
From: Alan Cox @ 2007-07-05 12:39 UTC (permalink / raw)
  To: Tejun Heo; +Cc: Jeff Garzik, linux-ide, bruinjm

> but IDE simply ignores the error and continues to operate in MWDMA
> mode, so I guess we can remove the 'temporary fix' comment or add
> another quirk type - ATA_HORKAGE_SETXFER_MAY_FAIL - and use it.

Should we warn in these cases ? Or issue a new identify and check the
mode activated ?

Alan

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH 2.6.22-rc7] libata: quirk IOMEGA ZIP 250 ATAPI FLOPPY
  2007-07-05 12:39 ` Alan Cox
@ 2007-07-05 23:53   ` Jeff Garzik
  2007-07-06  6:42     ` Tejun Heo
  0 siblings, 1 reply; 5+ messages in thread
From: Jeff Garzik @ 2007-07-05 23:53 UTC (permalink / raw)
  To: Alan Cox; +Cc: Tejun Heo, linux-ide, bruinjm

Alan Cox wrote:
>> but IDE simply ignores the error and continues to operate in MWDMA
>> mode, so I guess we can remove the 'temporary fix' comment or add
>> another quirk type - ATA_HORKAGE_SETXFER_MAY_FAIL - and use it.
> 
> Should we warn in these cases ? Or issue a new identify and check the
> mode activated ?

The latter, issuing a new identify, is really what you want to do. 
AFAICT that's the canonical method of querying the device's knowledge of 
its mode settings.

	Jeff




^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH 2.6.22-rc7] libata: quirk IOMEGA ZIP 250 ATAPI FLOPPY
  2007-07-05 23:53   ` Jeff Garzik
@ 2007-07-06  6:42     ` Tejun Heo
  0 siblings, 0 replies; 5+ messages in thread
From: Tejun Heo @ 2007-07-06  6:42 UTC (permalink / raw)
  To: Jeff Garzik; +Cc: Alan Cox, linux-ide, bruinjm

Jeff Garzik wrote:
> Alan Cox wrote:
>>> but IDE simply ignores the error and continues to operate in MWDMA
>>> mode, so I guess we can remove the 'temporary fix' comment or add
>>> another quirk type - ATA_HORKAGE_SETXFER_MAY_FAIL - and use it.
>>
>> Should we warn in these cases ? Or issue a new identify and check the
>> mode activated ?
> 
> The latter, issuing a new identify, is really what you want to do.
> AFAICT that's the canonical method of querying the device's knowledge of
> its mode settings.

How about just keep using PIO as the patch posted in this thread does?
I'm not really sure adding more complexity is worth it considering it's
only one device till now and it may not even be safe considering that
some controllers snoop SETXFER and configure themselves accordingly.

-- 
tejun

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH 2.6.22-rc7] libata: quirk IOMEGA ZIP 250 ATAPI FLOPPY
  2007-07-05  3:31 [PATCH 2.6.22-rc7] libata: quirk IOMEGA ZIP 250 ATAPI FLOPPY Tejun Heo
  2007-07-05 12:39 ` Alan Cox
@ 2007-07-11  1:38 ` Jeff Garzik
  1 sibling, 0 replies; 5+ messages in thread
From: Jeff Garzik @ 2007-07-11  1:38 UTC (permalink / raw)
  To: Tejun Heo; +Cc: linux-ide, bruinjm, alan

Tejun Heo wrote:
> The Zip 250 which chokes on MWDMA SET_XFERMODE sometimes have "Floppy"
> appeneded to its model number.  Quirk it too.
> 
>   http://bugzilla.kernel.org/show_bug.cgi?id=8563
> 
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> Cc: Hans de Bruin <bruinjm@xs4all.nl>
> ---
> It seems the Zip 250 mwdma failure on libata doesn't seem to be
> libata's fault after all.  IDE also fails SET_XFERMODE on this drive
> but IDE simply ignores the error and continues to operate in MWDMA
> mode, so I guess we can remove the 'temporary fix' comment or add
> another quirk type - ATA_HORKAGE_SETXFER_MAY_FAIL - and use it.
> 
> Anyways, for the time being, this should do.
> 
>  drivers/ata/libata-core.c |    2 ++
>  1 file changed, 2 insertions(+)

applied



^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2007-07-11  1:38 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-07-05  3:31 [PATCH 2.6.22-rc7] libata: quirk IOMEGA ZIP 250 ATAPI FLOPPY Tejun Heo
2007-07-05 12:39 ` Alan Cox
2007-07-05 23:53   ` Jeff Garzik
2007-07-06  6:42     ` Tejun Heo
2007-07-11  1:38 ` Jeff Garzik

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).