>> Hi Thomas, >> Do you think handling really vendor specific "boosts" like EeePC's SHE >> is in cpupower scope > This is an oem/vendor specific way to modify the front-side-bus > throughput on (Intel atom only?) eeepc like machines (acer, asus and > others?)? I don't know exactly what it does, but yes it seems to modify the fsb (and possibly something else on some models, who know ...), and it's only specific to Asus EeePCs. But Asus notebooks seems to have a similar "Power4Gear" function, that may also overclock/downclock the gpu. > You could try to experiment with registering your own delayed work queue > in eeepc-laptopc.c and try to find best tunings and fittings for such > requirements. > If it works out and/or other xy-laptop.c or whatever drivers provide > similar functionality it could get moved up into a more generic > framework. A separate one next to cpuidle and cpufreq, for example > fsb_mod? I'll see if other platform drivers have something similar, but I believe that at least one of them has a "peformance" mode. > PS: Wouldn't the cpufreq subsystem suffice to register for this > SHE thing? > Could it be that SHE and real CPU freq (speedstep) is mutual exclusive? > Is the only problem that p4_clockmod cannot be loaded then? p4_clockmod is only loaded on olds EeePCs. New ones are using acpi-cpufreq. And you can only load one cpufreq driver at a time. -- Corentin Chary http://xf.iksaif.net -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
