RE: CF flash PATA on libata failure to attach

["Andrew Hall" <andrew.a.hall@gmail.com>]

> 
> I'm betting that the SATA/PATA converter is getting confused with
> the ata_piix driver's attempt to use MDMA2 on it.
> 
> PIO appears to be working fine -- the BIOS uses it to boot,
> and libata uses it to do the IDENTIFY operation.
> 
> So, try this hack, which should force ata_piix to use only PIO
> for the ICH8 chipset. So long as you don't have any real SATA
> drives, this might do the trick.
> 
> Cheers
> 
> --- linux/drivers/ata/ata_piix.c.orig 2007-06-27 11:20:51.000000000 -
> 0400
> +++ linux/drivers/ata/ata_piix.c 2007-06-28 13:32:27.000000000 -0400
> @@ -526,8 +526,8 @@
> .flags = PIIX_SATA_FLAGS | PIIX_FLAG_SCR |
> PIIX_FLAG_AHCI,
> .pio_mask = 0x1f, /* pio0-4 */
> - .mwdma_mask = 0x07, /* mwdma0-2 */
> - .udma_mask = 0x7f, /* udma0-6 */
> + .mwdma_mask = 0x00, /* mwdma0-2 */
> + .udma_mask = 0x00, /* udma0-6 */
> .port_ops = &piix_sata_ops,
> },
> 
> @@ -537,8 +537,8 @@
> .flags = PIIX_SATA_FLAGS | PIIX_FLAG_SCR |
> PIIX_FLAG_AHCI,
> .pio_mask = 0x1f, /* pio0-4 */
> - .mwdma_mask = 0x07, /* mwdma0-2 */
> - .udma_mask = 0x7f, /* udma0-6 */
> + .mwdma_mask = 0x00, /* mwdma0-2 */
> + .udma_mask = 0x00, /* udma0-6 */
> .port_ops = &piix_sata_ops,
> },

Yes!! It worked.. which means you were right - forcing the channel to PIO4
and the drive was happy. The problem I have now is that we do in fact also
have a SATA HDD connected to the same controller used for database and
logging data - this now also is forced to use PIO4. How can I force the
first channel to only use PIO and the remainder to use MWDMA2? 

Thanks for your help..