View Single Post
Old 06-14-2012, 12:01 AM   #20
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Last I looked it did not depend on any libraries. Unlike my touchpaint code, this does not check to see which event device is the zforce touchscreen. Its assumptions about which device only work when booted from main. If you boot from diags, you need to swap the event device number 2/3...

Did you use diags SSH to test it?

Also, code compiled using the 5.1.0 header files will NOT work on 5.0.x if it uses eink ioctl updates, and if compiled with 5.0.x headers eink ioctl updates will not work on 5.1.x. Calling eips should work fine though.

You did not say HOW it is not working. Is the problem with eink updates, or with touchscreen?

Also, if touchscreen is not working, you may need to tap the power button...
geekmaster is offline   Reply With Quote