On Wed, Jul 23, 2008 at 08:13:49PM +0100, Alan Cox wrote: > > Ok, however the drivers/ide/pci/alim15x3.c still works fine > > on this board, so there's something that something in the libata > > driver path not working properly. Possibly drivers/ata/pata_ali.c > > that is missing something > > The old driver makes some rather iffy assumptions when dev->irq == 0 in > part because the old IDE code predates PCI quirks. >From reading the ALI M1543 datasheets that the interrupt pin in either mode (compatibility or native) is routed directly into the inbuilt ISA-PIC, and thus the IRQ field in the PCI child device is not available. This means we need to be able to override the IRQ numbers for these devices. I had a look, and there doesn't seem to be any way of specifying an IRQ for a host port when registering with libata-sff.c, which is a problem since we need to be able to either pass-in or have a callback to allow our "quirk" to specify a new IRQ for the device. Does anyone know if the ALi M5229 actually exists outside of one of the M1543 bridges? Note, this hardly seems to be a board-quirk, it is more of a device quirk... -- Ben Q: What's a light-year? A: One-third less calories than a regular year. -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
