On Thu, 2007-02-08 at 20:19 -0500, Jeff Garzik wrote: > Zhang, Yanmin wrote: > > If an ATA drive uses legacy mode, ata driver will choose 14 and 15 as the > > fixed irq number. On ia64 platform, such numbers are GSI and should be converted > > to irq vector. > > > > Below patch against kernel 2.6.20 fixes it. > > > > Signed-off-by: Zhang Yanmin <yanmin.zhang@xxxxxxxxx> > > IA64 should create its own libata-portmap.h, rather than modifying the > one in asm-generic with arch-specific choices. > > powerpc is a current example of this (and currently the only > non-asm-generic user) found in kernel 2.6.20. Thank Jeff. I worked out a new patch. If an ATA drive uses legacy mode, ata driver will choose 14 and 15 as the fixed irq number. On ia64 platform, such numbers are GSI and should be converted to irq vector. Below patch against kernel 2.6.20 fixes it. Signed-off-by: Zhang Yanmin <yanmin.zhang@xxxxxxxxx> --- diff -Nraup linux-2.6.20/arch/ia64/Kconfig linux-2.6.20_fix/arch/ia64/Kconfig --- linux-2.6.20/arch/ia64/Kconfig 2007-02-08 15:13:41.000000000 +0800 +++ linux-2.6.20_fix/arch/ia64/Kconfig 2007-02-09 11:19:35.000000000 +0800 @@ -11,6 +11,7 @@ menu "Processor type and features" config IA64 bool + select ATA_NONSTANDARD if ATA default y help The Itanium Processor Family is Intel's 64-bit successor to diff -Nraup linux-2.6.20/include/asm-ia64/libata-portmap.h linux-2.6.20_fix/include/asm-ia64/libata-portmap.h --- linux-2.6.20/include/asm-ia64/libata-portmap.h 1970-01-01 08:00:00.000000000 +0800 +++ linux-2.6.20_fix/include/asm-ia64/libata-portmap.h 2007-02-09 11:19:55.000000000 +0800 @@ -0,0 +1,12 @@ +#ifndef __ASM_IA64_LIBATA_PORTMAP_H +#define __ASM_IA64_LIBATA_PORTMAP_H + +#define ATA_PRIMARY_CMD 0x1F0 +#define ATA_PRIMARY_CTL 0x3F6 +#define ATA_PRIMARY_IRQ(dev) isa_irq_to_vector(14) + +#define ATA_SECONDARY_CMD 0x170 +#define ATA_SECONDARY_CTL 0x376 +#define ATA_SECONDARY_IRQ(dev) isa_irq_to_vector(15) + +#endif - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
