Linux says I have the USB controller. It's built in my device.
With cat /proc/bus/input/devices it shows this:

I: Bus=0003 Vendor=14e1 Product=6000 Version=0001
N: Name="DIALOGUE INC PenMount USB"
P: Phys=usb-0000:00:1d.7-4.1/input0
S: Sysfs=/class/input/input6
U: Uniq=
H: Handlers=mouse0 event6 evbug
B: EV=1b
B: KEY=30000 0 0 0 0 0 0 0 0
B: ABS=3
B: MSC=10

On 11 mrt, 10:40, squix <[email protected]> wrote:
> I don't really understand that much of linux drivers. I thought that
> at least for the serial module a parameter for the kernel would be
> needed. My controller is attached directly to the serial port and
> someone has to tell the kernel which serial settings it should use to
> address the board. Do you have a USB or serial controller? Have you
> tried the drivers I mentioned in the last thread? Before putting
> android on that device I successfully  could use the touch screen
> under ubuntu...
>
> On Mar 11, 10:26 am, Androidphan <[email protected]> wrote:
>
> > I have a PenMount 6000. I noticed the kernel driver. But when I put a
> > printk("Test IRQ\n"); in the file at the interrupt handler and then
> > touch the screen, it's not printing anything... Still finding out how
> > it works. When I call geteevent, it does react on touchscreen input.
>
> > On 11 mrt, 08:05, squix <[email protected]> wrote:
>
> > > Hi
>
> > > My android machine has an old serial penmount touchscreen with a DMC
> > > 9000 controller board. Now I don't really know which driver promises
> > > best chances. The generic distribution independent drivers either
> > > require Xorg or are GPM (general purpose mouse). In addition, there's
> > > a kernel module for penmount available. Any ideas which is the most
> > > promising driver? How android integrates input devices?
>
> > > Penmounts drivers:http://www.penmount.com.tw/down_2_1_9k.php
>
> > > Dani
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to