Messages in this thread | | | Date | Thu, 5 Feb 2004 13:56:20 -0800 | From | Tony Lindgren <> | Subject | Re: [PATCH] powernow-k8 max speed sanity check |
| |
* Pavel Machek <pavel@suse.cz> [040205 13:39]: > > Well, I wanted some way to detect exactly this broken machine. You > might want to simply put == 8 there.. but proper solution is DMI blacklist.
Or just use the current running values for max speed. That will fail if the system boots at lower speeds on battery though. And the BIOS checks will fail on buggy BIOSes and when upgrading the CPU. So maybe use both checks?
> > > What do you think about using module options maxfid and maxvid? > > Well, the original BIOS has not only maximum values wrong, but also > 1600MHz wrong, as far as I can tell...
Outch! I did not know that...
Are the middle values needed? What if you only use the min and max fid/vid values, and always recalculate the stepping tables from those values?
> Something like /proc/frequencies file would be needed where you could > > echo "0 0xa; 0x8 0x6; 0xa 0x2" > /proc/frequencies to override. You > need to override all of them, not just top one.
Maybe not, if the stepping table would get recalculated on init?
Tony - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |