https://bugzilla.novell.com/show_bug.cgi?id=457113
User teheo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=457113#c27
Tejun Heo changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |WONTFIX
--- Comment #27 from Tejun Heo 2009-02-03 21:15:44 MST ---
Ah... now I get it. We had driver priority screwed up during the beta cycles
so you were using the old IDE driver which can do ATAPI DMA fine on the ali, so
the different device name. This is one of the remaining regressions of libata
drivers compared to the original IDE. :-(
I have the pata_ali hardware and tested it quite extensively but couldn't
figure out why the hell ATAPI DMA wouldn't work. Making PCI configuration
areas identical didn't help and apart from slight register access order and
timing differences, both IDE and pata_ali are using the same command sequence.
Maybe I should give a shot at tracing each io access and try to match those up
with IDE, I don't know.
Anyways, sorry that figuring it out took so long. You simply are using
different drivers. You can make the GM use IDE drivers by editing
/etc/sysconfig/kernel and regenerating intird. I'm resolving this as WONTFIX
for now. I'll give another shot at fixing pata_ali ATAPI DMA later.
Thanks.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.