Quote:
Originally Posted by NiLuJe
Running without Nickel or pickel or ntx_hwconfig is not a supported configuration. There's okreader for that  .
|
OKreader ... Ohh nice

Im still using ntx_hwconfig and the koreader.sh suggests otherwise (see reboot clause), but ill take your word for it

. BTW this support isn't for me, i just wanted to contribute something back. I will setup a github account and do some PR's if i can find the time.
What is do not understand though is why one would use the variables from rcS instead of relying solely on ntx_config. Because when i look at the default rcS
Quote:
Originally Posted by NiLuJe
(Handling those issues on our own would be fragile, error-prone, and basically reinventing the wheel for, again, an unsupported setup. Incidentally, that's why okreader's hardware support is limited).
|
I always reinvent the wheel, then you have something to bring to the table later on
Quote:
Originally Posted by NiLuJe
As far as CPU schedulers go, it probably doesn't ship with interactive, that's to be expected, but it *should* offer ondemand, though.
In any case, on that front, the startup script is designed to do nothing if nothing sensible is possible on the current HW. Which might indeed be the case on <= Mk.5 devices, given how defensively I coded that after a few rounds of tests on various older models.
|
Yeah that is weird isnt it, but ill give you the ouput
[root@(none)]# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
conservative powersave userspace performance