and why do you really bother about the flow from driver to EventHub .
Its reaching instantaneously to EvetHub and no filtering in the path.
So all your analysis for any means ca start from EventHub unless you
are facing any weired problem of not all data reaching to Eventhub ?
On Oct 12, 12:44 p
Um. EventHub.cpp reads the data from the driver. You can look at EventHub
to see how it reads it. There isn't anything more to say about I don't
think -- it reads the next event from the driver, and the driver provides
it. (I can't really help you with details in the kernel, I work in the user
Hi Dianne,
Thanks for your reply. Can you please describe how events are passed
from touch screen DRIVER to EventHub.cpp (JNI layer) when a touch
screen event gets generated?
Regards
Leo
On Oct 12, 7:25 pm, Dianne Hackborn wrote:
> EventHub.cpp and KeyInputQueue.java are the main participan
EventHub.cpp and KeyInputQueue.java are the main participants.
On Mon, Oct 12, 2009 at 10:10 AM, Leo wrote:
>
> Hi Guys,
>
> I'll be grateful if someone can explain that how the JNI layer (Native
> layer) gets notified by the touchscreen driver when a touchscreen
> event occurs? Any documentatio
