View Single Post
Old 06-07-2018, 02:37 PM   #294
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by CH23 View Post
Could you tell me where i can find more info abou this? What code within KSM should i look at, or what code in pbchess?
The script etc/init.d/rcS exports based on the value of PRODUCT the name of the touch driver to be used for KSM as mousedriver.
The script adds/kbmenu/onstart/checkinstall.sh checks whether this touch driver is available in adds/kbmenu/Qt/plugins/mousedrivers. If it does not find it there, it tries to copy it from mnt/onboard/.adds/kbmenu_user/copyrepos.
Currently there are two touch drivers available in KSM: libKoboTS.so and libKoboTS_h2o2.so. Since your device model is not known to KSM it tries to use libKoboTS.so.

The source code of the drivers are here.

Last edited by tshering; 06-07-2018 at 04:47 PM.
tshering is offline   Reply With Quote