Sorry, do not know details. I assumed you would find some information
in source code. Maybe other people on list know or can help find it.
On Mar 24, 9:22 am, Akio <[EMAIL PROTECTED]> wrote:
> Hi vladimir.schlott:
>
> After follow what you said, using Google as the key words, I
> found
> android-emulator-20080211\qemu\hw\events_device.c
> in this file, I found
> void events_dev_init(uint32_t base, void *pic, int irq)
> {
> events_state *s;
> int iomemtype;
>
> s = (events_state *) qemu_mallocz(sizeof(events_state));
>
> iomemtype = cpu_register_io_memory(0, events_readfn,
> events_writefn, s);
>
> cpu_register_physical_memory(base, 0xfff, iomemtype);
>
> qemu_add_kbd_event_handler(events_put_keycode, s);
> qemu_add_mouse_event_handler(events_put_mouse, s, 1);
> qemu_add_generic_event_handler(events_put_generic, s);
>
> s->base = base;
> s->pic = pic;
> s->irq = irq;
>
> s->first = 0;
> s->last = 0;
> }
>
> and in linux-2.6.23-m3\drivers\input\keyboard
> \goldfish_events.c seems only provide keyboard events.
> where is the mouse or touch screen's event handling?
> Could you do us a favor to show which one should be hacked?
>
> Thank you very much.
>
> Best Regards,
> Akio
>
> On Mar 24, 8:48 pm, "[EMAIL PROTECTED]"
>
> <[EMAIL PROTECTED]> wrote:
> > If touch works in emulator, read source code of emulator and kernel
> > and see how it works, then do same thing in your kernel.
>
> > On Mar 24, 5:33 am, "Anil Sasidharan" <[EMAIL PROTECTED]> wrote:
>
> > > Hi,
>
> > > It would be great if you could throw some light on "how can
> > > synaptics touchscreen (RMI) driver can be integrated with Android". We
> > > do report "X, Y, X2, Y2, Pressure, ABS_FINGERS and TOOL_WIDTH to the
> > > input subsystem. However Android does not seem to be responding to the
> > > touch events. Any suggestions?
>
> > > Warm Regards,
> > > Anil
>
> > > On Wed, Mar 19, 2008 at 1:05 PM, hackbod <[EMAIL PROTECTED]> wrote:
>
> > > > On Mar 17, 1:21 am, "Anil Sasidharan" <[EMAIL PROTECTED]> wrote:
> > > > > Android reads raw X,Y and Pressure info from touch driver.
> > > > > And the device node being opened for touch is /dev/input/event1.
> > > > > Regarding the network, you will have to set the DNS and LOCAL-IP
> > > > using
> > > > > the setprop utility.
>
> > > > It shouldn't matter what name you publish your input device under /dev/
> > > > input -- we just scan through all of the devices there and examine the
> > > > events they report to classify them. So for something to be
> > > > considered a touch driver, you just need to make sure you say you
> > > > report X, Y, and the key code for the primary mouse button.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Android Internals" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-internals?hl=en
-~----------~----~----~----~------~----~------~--~---
