On Fri, 2013-09-20 at 00:36 +0900, Prabhuram Murugan wrote:
> Hi all,
>
> We got a requirement to interface a USB JOG dial to the TIZEN IVI
> system,
>
> We are using the NDis166 board with TIZEN IVI 2.0 (for some reason)
>
> The below link show the JOG dial , but there is no linux driver
> available at present.
>
> http://retail.contourdesign.com/?/products/22
>
>
> When I just plug in the device it is recognised as a pointing device
> and the I am able to get some event from the device node
>
> cat /dev/mouse3 prints some characters when I rotate the JOG dial /
> press some keys ...
>
>
> I have to make these event recognised by the HTLM 5 applications and
> Native EFL applications.
Perhaps the device just represents itself as a scroll wheel with a
multi-button mouse? If so then it should 'just work' for both web and
native apps using the existing W3C and EFL api's for interacting with
input devices.
Have you attempted to do this yet instead of just just cat'ing the low
level device node?
>
> Should I write a new user space driver like evdev / modify the
> existing evdev driver to take and process events for JOG dial events ?
If the device is already representing itself as some kind of input
device to provide you (the app) with events for everything it can do
then i don't see the need.
> Also for the Hard keys I planned to write some daemon which can open
> and read events from device node and use AUL API's to launch the
> application. Kindly suggest your opinion.
Since your still using a Tizen IVI 2.0 based image then your still using
X. You can either use X or ecore_x methods to grab button events, or
just have you daemon directly pull events of the device node.
--rusty
_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi
