View Single Post
Old 03-06-2019, 01:36 PM   #11
BloodRagg
Zealot
BloodRagg ought to be getting tired of karma fortunes by now.BloodRagg ought to be getting tired of karma fortunes by now.BloodRagg ought to be getting tired of karma fortunes by now.BloodRagg ought to be getting tired of karma fortunes by now.BloodRagg ought to be getting tired of karma fortunes by now.BloodRagg ought to be getting tired of karma fortunes by now.BloodRagg ought to be getting tired of karma fortunes by now.BloodRagg ought to be getting tired of karma fortunes by now.BloodRagg ought to be getting tired of karma fortunes by now.BloodRagg ought to be getting tired of karma fortunes by now.BloodRagg ought to be getting tired of karma fortunes by now.
 
BloodRagg's Avatar
 
Posts: 128
Karma: 842196
Join Date: Feb 2019
Device: none
Quote:
Originally Posted by Frenzie View Post
Some of those may be easy to fix (especially the first one strikes me as most likely a complete non-issue), but you'd have to do it through a PR and/or giving us a backtrace. (Read: I'm not going to strip my device of Nickel stuff, even if this particular change could probably be tested with a quick rename. )
Indeed non-issues, but a robust script goes a long way
I made a PR to pull all ntx_hwconfig values into the environment, its a good base.

Quote:
Originally Posted by Frenzie View Post
PRODUCT and to a lesser extent WIFI_MODULE seem to located more in the realm of fundamental necessities. I have considered implementing a "generic fallback Kobo" with a warning message instead of erroring out (so that in some cases a new device could work out of the box) but that'd still depend on the presence some Kobo stuff regardless.


Quote:
Originally Posted by Frenzie View Post
Screen upside down might well be an issue in KSM at the moment with NiLuJe's latest 8-bit change, see here.
Im not running KSM (koreader only)
BloodRagg is offline   Reply With Quote