Hi! > > In 2.6.20.9 I can change trippoints: > > > > echo "105:100:100:78:70:40:30" > /proc/acpi/thermal_zone/TZ0/trip_points > > echo 10 > /proc/acpi/thermal_zone/TZ0/polling_frequency > > > > Then I got: > > cat /proc/acpi/thermal_zone/TZ0/* ... > > Its bug or feature? > > > > Committed to mainline May 10: > > Gitweb: http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=11ccc0f249cb01a129f54760b8ff087f242935d4 > Commit: 11ccc0f249cb01a129f54760b8ff087f242935d4 > Parent: de46c33745f5e2ad594c72f2cf5f490861b16ce1 > Author: Len Brown <len.brown@xxxxxxxxx> > AuthorDate: Mon Apr 30 22:36:01 2007 -0400 > Committer: Len Brown <len.brown@xxxxxxxxx> > CommitDate: Mon Apr 30 22:36:01 2007 -0400 > > ACPI: thermal trip points are read-only What was the rationale? Can we get this one reverted? Some machines (HP omnibook xe3) have broken trip points -- too high -- so machine will overheat and trigger hw shutdown before starting passive cooling. That's really broken, and write to trip points is reasonable way to 'fix' that. (I'd understand if you only ever let trip points to decrease... but otoh root should be able to shoot himself....) Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
