https://bugzilla.kernel.org/show_bug.cgi?id=102741 --- Comment #3 from Sergei Shtylyov <headless@xxxxxxxx> --- (In reply to Andreas E from comment #2) > NAH!!! I can't believe it. This thing can do UDMA/100 Well, I wouldn't call UDMA/100 with 66 MHz clock real UDMA/100. > but it was limited artificially to /66. "Shit happens". :-) > In any case, I think the driver messages should *inform* the user about this > being not their HDD(s) at fault, but forced to this speed by the driver > itself. Because every user would initially think that it's their fault, not > the driver's. Makes sense. > Is there any way I can force it to operate at UDMA/100? > Some #define, anything? With the IDE driver, there was a #define but that's not the case with the libata one. Thank Alan Cox for that. :-) However, it shouldn't be hard to do, just comment out the following lines: if (clock_slot < 2 && ppi[0] == &info_hpt370) ppi[0] = &info_hpt370_33; if (clock_slot < 2 && ppi[0] == &info_hpt370a) ppi[0] = &info_hpt370a_33; [the rest skipped] -- You are receiving this mail because: You are watching the assignee of the bug. -- 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
