Re: libata limiting to UDMA/33 instead of UDMA/100

From: Alan Cox
Date: Sun Jun 10 2007 - 13:40:27 EST

> The patch fixes my cable detection problem. Now everything is back to
> UDMA/100 again. I noticed that ata1/ata2 claim to be using irq0, although
> they do in fact use irq10. This seems to be a purely cosmetical problem.

I think Tejun posted a patch for that one already - its purely cosmetic
and caused by soem of the core cleanup. The cmd/ctl/bmdma values are also
currently mis-reported from similar updates.

> ata1.01: ata_hpa_resize 1: sectors = 241254720, hpa_sectors = 241254720
> ata1.01: configured for UDMA/100

Will double check the and then push upstream
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at