mirror of
https://github.com/koreader/koreader.git
synced 2025-08-10 00:52:38 +00:00
cb2314d11b
* Run grep against /proc/modules directly instead of forking to lsmod * Revamp the CPUFreq governor choice logic I finally figured out why the scaling on the H2O was so wonky: Because it relies on an obscure i.MX hardware feature called DVFS, and it gets flipped for mysterious workaround-y reasons depending on Wi-Fi state... * Start playing with conservative, because just staying pegged at max clock is entirely stupid. And DVFS is extremely conservative, it needs somewhat sustained load to clock up... * Take care of the DVFS switcheroo in the Wi-Fi scripts