Michel Hoogervorst wrote:
> Hi,
>
>
> 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"
>
>
>
> Nope... nothing about this in dmesg|tail...
>
>
> 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.
>
>
>
> That indeed is the reason I'm sure it does work ;-)
> This thing has a switch for switching between presenter mode, and mouse
> mode.
> When I put it in mouse mode, I see events for event device 3, and when I
> put it in presenter mode, it gives events for event device 2.
>
> Problem is, that the stick in presenter mode, only returns a "KEY_M", no
> matter what side I push it.
> Other thing is, that while in mouse mode, it returns "KEY_M" on every
> key I press on device 2.
>
> Could this be my problem? That device 2 also returns a keypress when
> using the thing as device 3?
> I added USE_SDL_KEYBOARD = 0 in local_conf.py to stop it from pushing up
> the volume on every key I press :-P
> If I remove that, the thing still doesn't work (I then only see the
> mouse pointer move around my screen).
I would evpect that you see, something like:
grabbed input device
waiting for events
20:42:12.552117: EV_KEY KEY_LEFT pressed
20:42:12.552121: EV_SYN code=0 value=0
20:42:12.754057: EV_KEY KEY_LEFT released
20:42:12.754060: EV_SYN code=0 value=0
20:42:13.763784: EV_KEY KEY_DOWN pressed
20:42:13.763788: EV_SYN code=0 value=0
20:42:13.965727: EV_KEY KEY_DOWN released
20:42:13.965730: EV_SYN code=0 value=0
20:42:14.369619: EV_KEY KEY_RIGHT pressed
20:42:14.369623: EV_SYN code=0 value=0
20:42:14.571558: EV_KEY KEY_RIGHT released
20:42:14.571561: EV_SYN code=0 value=0
20:42:15.076425: EV_KEY KEY_UP pressed
20:42:15.076429: EV_SYN code=0 value=0
20:42:15.177394: EV_KEY KEY_UP released
20:42:15.177397: EV_SYN code=0 value=0
timeout, quitting
released input device
You can try
evtest /dev/input/event[23], this gives me:
Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0
Input device name: "i2c IR (Hauppauge)"
Supported events:
Event type 0 (Sync)
Event type 1 (Key)
Event code 0 (Reserved)
Event code 1 (Esc)
Event code 28 (Enter)
Event code 71 (KP7)
Event code 72 (KP8)
Event code 73 (KP9)
Event code 75 (KP4)
Event code 76 (KP5)
Event code 77 (KP6)
Event code 79 (KP1)
Event code 80 (KP2)
Event code 81 (KP3)
Event code 82 (KP0)
Event code 103 (Up)
Event code 105 (Left)
Event code 106 (Right)
Event code 108 (Down)
Event code 113 (Mute)
Event code 114 (VolumeDown)
Event code 115 (VolumeUp)
Event code 116 (Power)
Event code 120 (?)
Event code 121 (KPComma)
Event code 122 (Hanguel)
Event code 123 (Hanja)
Event code 128 (Stop)
Event code 132 (Front)
Event code 139 (Menu)
Event code 142 (Sleep)
Event code 148 (Prog1)
Event code 163 (NextSong)
Event code 164 (PlayPause)
Event code 165 (PreviousSong)
Event code 167 (Record)
Event code 168 (Rewind)
Event code 207 (Play)
Event code 208 (Fast Forward)
Event code 218 (Connect)
Event code 224 (Brightness down)
Event code 225 (Brightness up)
Event code 354 (Goto)
Event code 363 (Channel)
Event code 368 (Language)
Event code 370 (Subtitle)
Event code 375 (Screen)
Event code 377 (TV)
Event code 392 (Audio)
Event code 393 (Video)
Event code 395 (List)
Event code 402 (ChannelUp)
Event code 403 (ChannelDown)
Event type 20 (Repeat)
Testing ... (interrupt to exit)
Event: time 1185734798.210091, type 1 (Key), code 105 (Left), value 1
Event: time 1185734798.210095, -------------- Report Sync ------------
Event: time 1185734798.412028, type 1 (Key), code 105 (Left), value 0
Event: time 1185734798.412031, -------------- Report Sync ------------
Event: time 1185734799.724673, type 1 (Key), code 108 (Down), value 1
Event: time 1185734799.724677, -------------- Report Sync ------------
Event: time 1185734799.926610, type 1 (Key), code 108 (Down), value 0
Event: time 1185734799.926613, -------------- Report Sync ------------
Event: time 1185734800.330505, type 1 (Key), code 106 (Right), value 1
Event: time 1185734800.330509, -------------- Report Sync ------------
Event: time 1185734800.532444, type 1 (Key), code 106 (Right), value 0
Event: time 1185734800.532447, -------------- Report Sync ------------
Event: time 1185734800.835368, type 1 (Key), code 103 (Up), value 1
Event: time 1185734800.835373, -------------- Report Sync ------------
Event: time 1185734801.037303, type 1 (Key), code 103 (Up), value 0
Event: time 1185734801.037307, -------------- Report Sync ------------
>From my /etc/ivtv/ir_kbd_i2c.pvr350.conf, there is:
# cursor keys
0x0014 = 103 # KEY_UP
0x0015 = 108 # KEY_DOWN
0x0016 = 105 # KEY_LEFT
0x0017 = 106 # KEY_RIGHT
applykeymap only removes the comments from the ir_kbd_i2c.pvr350.conf
and sends this to input-kbd.
So what remains is how to determine the key values 0x0014-0x0017. IIRC
there were send to dmesg (and /var/log/messages) when a button was not
recognised but it need to be held down for quite a few seconds.
My guess is that it will work when you have the correct mapping.
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
