On 2/23/07, Guenther Sohler <[EMAIL PROTECTED]> wrote:
>
> > > At the denoted place <======Broken Pipe ==> In the function input_event
> > > with the configuration sent from input_sync it will NOT call the event
> > > function from evdev. Thus it does not know that new data is available.
> > > Maybe hid_input_report should call another function but input_sync
> > > instead ...
>
> If you look at the function stack i described earlier, you see that there is
> the function 'input_sync' which calls the function 'input_event'.
> Input sync gets the parametes from the function call in "input_sync" but
> with this parameters submitted, "input_event" will NEVER call the
> event function of the evdev device.
>
In input lungua evdev is not a device but a handler (interface) so
input_sync should definitely reach evdev_event throug this piece of
code at the end of input_event():
list_for_each_entry(...)
if (handle->open)
handle->handler->event(...)
--
Dmitry
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
