Do you have a question? Post it now! No Registration Necessary
- arrudasx
September 2, 2006, 7:09 pm

am trying to get a PS/2 touchscreen working using a 2.4 kernel based on
Redhat Enterprise WS3. The touchscreen controller sits behind an
embedded controller from National Smeiconductor, part number PC87591.
The embedded controller has in it an i8042 keyboard mouse controller,
with the ability to mux 4 PS/2 ports.
Currently, I have an X windows drivers module that communicates with
the touchscreen controller at startup using /dev/psaux. It sends
configuration commands down, and receives correct ACKs back (0xFA).
Also, when it sends the command to get the model touchscreen
controller, that is correctly received. This is all verified in the
logfile for X.
The file /proc/interrupts shows increasing interrupts for psaux (IRQ12)
when X is starting up. However, after X starts, I do not receive
interrupts from the touchscreen, i.e., pressing the stylus on the
screen does nothing.
I would like to point out that this all works under an ACPI enabled 2.6
kernel. What could ACPI be doing to the embedded controller to get
interrupts to work that I am missing? Suggestions?
Thanks
Steve
Redhat Enterprise WS3. The touchscreen controller sits behind an
embedded controller from National Smeiconductor, part number PC87591.
The embedded controller has in it an i8042 keyboard mouse controller,
with the ability to mux 4 PS/2 ports.
Currently, I have an X windows drivers module that communicates with
the touchscreen controller at startup using /dev/psaux. It sends
configuration commands down, and receives correct ACKs back (0xFA).
Also, when it sends the command to get the model touchscreen
controller, that is correctly received. This is all verified in the
logfile for X.
The file /proc/interrupts shows increasing interrupts for psaux (IRQ12)
when X is starting up. However, after X starts, I do not receive
interrupts from the touchscreen, i.e., pressing the stylus on the
screen does nothing.
I would like to point out that this all works under an ACPI enabled 2.6
kernel. What could ACPI be doing to the embedded controller to get
interrupts to work that I am missing? Suggestions?
Thanks
Steve
Site Timeline
- » uc linux support for threading
- — Next thread in » Embedded Linux
-
- » Linux on a IXDP465 ?
- — Previous thread in » Embedded Linux
-
- » Crosscompiling for ARM: reloc type R_ARM_ABS32 is not supported for PIC - ...
- — Newest thread in » Embedded Linux
-
- » White House In Danger Of Imminent Collapse, First Family Evicted
- — The site's Newest Thread. Posted in » Electronics Design
-
- » Using Bats To Burn Down the House
- — The site's Last Updated Thread. Posted in » Electronics Design
-