[Angstrom-devel] Palm LifeDrive Touchscreen

[Paul Sokolovsky]

Hello Zimler,

Saturday, November 3, 2007, 10:55:28 AM, you wrote:

> Hi,

> This is my first post to the list, I searched thru the archive but did
> not find any answer to my question.

> My situation:
> I managed to build an opie and a kernel to Palm LifeDrive (if someone is
> interested http://personal.hlfslinux.hu/hijaszu/palmld contains the
> process, which I would like to integrate into openembedded repository if
> I succeed with everything).

  Thanks for proceeding with this, but please make sure you keep in
touch with Sergey Lapin, who is Palm machines maintainer in OE.

> Currently angstrom is able to boot on the device and opie is started,
> but I'm unable to bring the touchscreen to work. I tried the following
> things:

> 1) I had a mouse pointer on the screen I supposed that opie is not
> correctly starting up. Found out that there is a TSLIB_TSDEVICE
> environment variable which defines the input device for opie.

  All needed environment already should be set up in the images.

> 2) From an older working familiar version I managed to find out that my
> touchscreen is working with wm97xx-ts kernel module, with pil=2 (what
> does this mean?) module parameter and on /dev/input/event2 device.

  Good work on finding out the driver, but /dev/input/event2 is not a
touchscreen, but merely a second input device which was registered by
the kernel. In OE, touchscreen is /dev/input/touchscreen0 and as said
above, what is already used by other parts of the system.

> 3) Tried all event device with TSLIB_TSDEVICE, only progress is that I
> do not have any mousepointer on the touchscreen. (With the new image,
> while wm97xx-ts is loaded I do not have any /dev/input/event2 device).
> 4) Tried to tail -f input devices on angstrom console image as the last
> script in rc5.d directory (the idea was that I should see garbage on
> doing touchscreen actions).

  Why such tricks? You can just SSH and issue commands. Which exactly
kinda written here:
http://pdalinux-tests.svn.sourceforge.net/viewvc/*checkout*/pdalinux-tests/trunk/testcases.html ,
and that page is still-on-the-ground-level effort to create a database
of testcases to verify system functioning of a Linux-PDA system.

> 5) Tried to create in this last boot script state (on console image) the
> event2 device (mknod /dev/input/event2 c 13 66).

> Could you please give me some other ideas, how can I found out why
> touchscreen is not working?

  Based on the above, you have some problem with the kernel touchscreen
driver. There's working driver for PalmLD of course, there're random
images floating around which have it working. The problem, as I
already wrote, is that folks creating those images prefer to exactly
create random irreproducible stuff instead of fixing issues in common
place like OE. Well, the solution is still to fix them there, so other
folks coming along can contribute to progress of the project, instead
of resolving same boring issues again and again. So, please be
encouraged to work on this.

> Attila ZIMLER




-- 
Best regards,
 Paul                            mailto:pmiscml at gmail.com