Michel Hoogervorst wrote:
> I tried some, but can't get it to work at all :-(
>
> Because my distro (Mandriva) had no 'lsinput' in the input-utils
> package, I downloaded and compiled the utils from the package
> mentioned in the wiki (in the Linux event interface page).
>
> When I do ./lsinput, I get those two wich belong to my presenter:
> /dev/input/event2
> bustype : BUS_USB
> vendor : 0x5fe
> product : 0x1010
> version : 16641
> name : "USB Device USB Device"
> phys : "usb-0000:00:02.0-1/input0"
> uniq : ""
> bits ev : EV_SYN EV_KEY EV_LED EV_REP
>
> /dev/input/event3
> bustype : BUS_USB
> vendor : 0x5fe
> product : 0x1010
> version : 16641
> name : "USB Device USB Device"
> phys : "usb-0000:00:02.0-1/input1"
> uniq : ""
> bits ev : EV_SYN EV_KEY EV_REL EV_ABS
>
When you press a button on you presenter do you see any messages from dmesg?
If you do then you need to map the unknown events to an event using
"applykeymap"
You can also try "input-events 2" or "input-events 3" and press some
keys, it you see something then it's working and will work with either
the event driver or lircd.
Duncan
> The event3 part is the mouse-function on this thing, and the event2
> part is the presenter-part.
> When I do ./input-events 3, and push the mouse up, I get this:
>
> 02:40:51.407932: EV_REL REL_Y -7
>
> Where the -7 is a number between -1 and -7
> Pushing it down, gives a positive number between 1 and 7
>
> So, me happy, and I put this in local_conf.py:
> EVENT_DEVS = [ '/dev/input/event3' ]
> EVENTMAP['REL_Y'] = ('UP', 'DOWN')
> EVENTMAP['REL_X'] = ('LEFT', 'RIGHT')
>
> But, nothing happens when I push the stick up, down, left or right...
> I also tried putting lines in like:
> EVENTMAP['REL_Y -7'] = 'UP'
> EVENTMAP['REL_Y 7'] = 'DOWN'
>
> And I even tried putting it like this:
> EVENTMAP['EV_REL REL_Y 3'] = 'DOWN'
>
> But, nothing works... :-(
>
> Just to be sure, I tried putting this in local_conf.py:
> EVENT_DEVS = [ '/dev/input/event0' ]
> EVENTMAP['BTN_TL2'] = 'DOWN'
>
> which is mapped to a key on my joystick device... and that works, so
> the communication between the event interface and Freevo works fine...
> but I still can't use the presenter to control Freevo. :-(
>
> Any ideas left?
>
>
> Michel
>
> 2007/7/26, Duncan Webb <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:
>
> > Hi,
> >
> > Just got to the last bit there where you mention the wiki and that's
> >> where I was going to say to check. Freevo doesn't natively
> support mouse
> >> navigation
> >
> >
> >
> > I understand, but I was thinking, maybe there's a way of fooling
> the Linux
> > OS in thinking that mouse-down is the same as the down button on a
> > keyboard
> > or joystick? :-) The mouse on this thing is a sort of joystick
> anyway...
> > it
> > only identifies itself as a mouse.
> >
> > An imap search just found a posting in
> >> freevo-users from 2004 that doesn't look encouraging - see Re:
> Plans for
> >> mouse input?
> >
> >
> >
> > I found that one too, but hey, it's three years later.. a lot
> could have
> > happened in the mean time ;-)
> >
> >
> > Wait, just found this -
> >> http://studio.kyperjokki.fi/engine/FreevoPointerInput. Doubt
> that diff
> >> will apply now though :)
> >
> >
> >
> > I found that one as well... but the latest change on the page is
> already a
> > year old, and I'm pretty sure I won't be able to apply this to
> Freevo
> > 1.7.2:-D
> > If I only understood Python... *sigh*
> >
> >
> > A google for 'freevo mouse patch' might help,
> >> patches welcome....
> >
> >
> >
> > Yeah, did that.... but couldn't find anything, that's why I
> asked the
> > list... hoping somebody knows more than I have found so far.
>
> Does your remote have an event interface under Linux?
>
> You can tell by using lsinput (package input-utils)
>
> If it does then you can use the lircd with dev/input driver
>
> See http://freevo.sourceforge.net/cgi-bin/doc/LircDevInput
> <http://freevo.sourceforge.net/cgi-bin/doc/LircDevInput> for a guide,
> which I wrote for the PVR-350 but should be relevant to any event
> driver.
>
> Duncan
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Freevo-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freevo-users
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Freevo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-users
