Touch Screen Filter Module

bridged with qdn.public.ddk.input
Post Reply
Biren Mehta

Touch Screen Filter Module

Post by Biren Mehta » Fri Nov 30, 2001 6:07 pm

I am building my own touch screen driver, dyna sc3 protocol, for a ps2
interface.
the driver is name devi-allergan.

In the following directory:
/usr/src/ddk-6.1.0/input/src/hardware/devi/allergan
I have put all of my development files.
These files include
- My Device Module: touch_dev.c
- My Protocol Module: touch_proto.c
- Main file - main.c
- Makefile
- Use File - devi-allergan.use
- driver executable: nto/x86/o/devi-allergan
- touch_dev and touch_proto objects in nto/x86....

I have put some printf's in the protocol module to
observe the packets that are being sent 'up'.

At the command line, in the directory of the
executable (nto/x86/o) I type:
devi-allergan -v touch_proto touch_dev

and I can see my packets being sent up from the
protocol module when I tap the touch screen.

At this point I would expect the packet to go to a
filter module and be calbrated.

I tried to create a calibration file while the device
driver was running and it didn't sense the touch
screen plugged into the ps2 port.

I typed devi-allergan -l (list) to see what modules
are availabe to me and there were my objects and fd,
uart, rel, abs,etc.....

I tried running:
devi-allergan -v touch_proto touch_dev abs
but that didn't work either.

It's like the chicken and the egg. I can't seem to run
the calibration because it doesn't sense my touch
screen as the input device. And I can't use my touch
screen as an input device until I run the calibration.

Hardware Support Account

Re: Touch Screen Filter Module

Post by Hardware Support Account » Fri Jan 04, 2002 8:11 pm

Hi Biren,

I will see what I can find out for you.

Erick.



Biren Mehta <cybermedconsulting@yahoo.com> wrote:

I am building my own touch screen driver, dyna sc3 protocol, for a ps2
interface.
the driver is name devi-allergan.

In the following directory:
/usr/src/ddk-6.1.0/input/src/hardware/devi/allergan
I have put all of my development files.
These files include
- My Device Module: touch_dev.c
- My Protocol Module: touch_proto.c
- Main file - main.c
- Makefile
- Use File - devi-allergan.use
- driver executable: nto/x86/o/devi-allergan
- touch_dev and touch_proto objects in nto/x86....

I have put some printf's in the protocol module to
observe the packets that are being sent 'up'.

At the command line, in the directory of the
executable (nto/x86/o) I type:
devi-allergan -v touch_proto touch_dev

and I can see my packets being sent up from the
protocol module when I tap the touch screen.

At this point I would expect the packet to go to a
filter module and be calbrated.

I tried to create a calibration file while the device
driver was running and it didn't sense the touch
screen plugged into the ps2 port.

I typed devi-allergan -l (list) to see what modules
are availabe to me and there were my objects and fd,
uart, rel, abs,etc.....

I tried running:
devi-allergan -v touch_proto touch_dev abs
but that didn't work either.

It's like the chicken and the egg. I can't seem to run
the calibration because it doesn't sense my touch
screen as the input device. And I can't use my touch
screen as an input device until I run the calibration.

Post Reply

Return to “qdn.public.ddk.input”