Quote:
Originally Posted by tshering
I don't mind at all. I am glad somebody takes care of the stuff.
I am not sure whether this can help you, but have a look at this post. |
Oh wow, that's super helpful! Can't believe I missed it. So I guess that implies that the Forma version would be the best to rebase on.
OK, I've created a new
unifed dev branch based on the Forma version to work on stuff until everything is caught up (then you could do a KSM09 2019-12 update roll up release or something), but
added in the usb version from CH23's Clara package. I'm not a strong programmer, but if I did it right, I also
added a conditional to ksmhome.sh with
gilali's modification to support the Libra H20. So in theory, I think that's all that needs to be done for Forma and Libra devices?
My struggle is knowing if the files in the repository are the absolute latest, and if not, where to get them. Off the top of your head, like the example of that usb file, can you think of any others? For example, I'm no longer certain which version of start_plato.sh is the latest to add in baskerville's
suggested modification; the one in the repository
right now is my best guess.
Quote:
|
I think it would be preferable to have one package for all models. The binary files that are borrowed from vlasovsoft should be updated to the most recent version. Currently the standard KSM 09 version comes with two different touch/mouse drivers (libKoboTS.so and libKoboTS_h2o2.so) on the user partition; based on the device model, KSM copies the appropriate driver to the system partition. This part should be modified to include also libKoboTS_h2o.so so that all models can use the correct driver (See also this post.)
|
OK, sounds easy enough. For the "case $MODEL_NUMBER in ..." block, I'm looking at what
geek1011 has posted in terms of device information and it looks like there are a few missing devices. However, how do you find out which models use which driver? (Edit: Oh, I see. That's the entire point of
ksm_helper).
As for the "case $PRODUCT in ..." block, where does one find the coordinate data for the various missing devices?
Quote:
|
The rcS file should also export the device names that vlasovsoft expects (cf. kobomenu_test.sh in the package that is available here.) As for the screen orientation, I guess one should follow how vlasovsoft handles it.
|
Not sure what vlasovsoft expects for the newer devices and it looks like that pbchess package hasn't been updated since February. Not sure how to do this part, but the above should be enough for now unless other people are willing to chip in (feel free to send pull requests!).