You are not logged in.
So extra/v4l-utils provides both keymaps and some utils for assigning keys on a remote control to actual keyboard key presses. What I can't figure out is how I can redefine a key press on my remote to a keyboard input. In other words, what translates the key on the remote to a keypress on the actual keyboard?
$ grep KEY_UP /etc/rc_keymaps/streamzap
0x28d0 KEY_UPRight now, the "KEY_UP" key makes my cursor go up just like a keypress of the up arrow botton. Where is the file that maps "KEY_UP" to "UP ARROW"?
Thanks!
EDIT: my remote is a streamzap usb.
$ sudo ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event18) with:
Driver streamzap, table rc-streamzap
Supported protocols: NEC RC-5 RC-6 JVC SONY LIRC other
Enabled protocols: NEC RC-5 RC-6 JVC SONY LIRC other
Repeat delay = 500 ms, repeat period = 125 msLast edited by graysky (2012-05-27 13:23:29)
Offline
It would seem that you are in kind of situation that i was with my television card and remote in past, where the guides on around linuxtv.org did guide forward rather good in manner of card/remote itself.
Thing is that of where you have an external remote controlled plugged into usb that has nothing in between and sends commands to what understands it ?
Like in term of my momentarily experiment of xbmc being aware of directions but not the "ok/select" key ?
The good choice forward is to figure on how LIRC seems to be supported so the commands that are being send could be used from own supplied choices from configuration written.
At Archlinux installing package of lirc gets a bit further, but configuration is in need, where looking at with command "cat /proc/bus/input/devices" shows event of remote controlled we should be listening at, in my case it would be named as "cx88 IR ***", and line of "kbd event**" shown.
Knowing that the default package installs an own configuration to be readen when started as rc.conf or manually with "rc.d start lircd", the file of /etc/conf.d/lircd.conf should reflect into wanted choices, where first is "LIRC_DEVICE=/dev/input/event**" of the one that is being readen, to other value of i have been using since first getting into area of "LIRC_DRIVER=dev/input", what just works as choice being made, could be default in this area, but i cannot gurantee that. Also notice in this choice there is no slash in front of path.
After those of pointing into spots of what is to be used is last file of lircd.conf what is usually stored at "/etc/lirc/lircd.conf" and could be included as separate file in with last choice of "LIRC_CONFIGFILE=/etc/lirc/lircd.conf", meaning of file is somewhat to understand given value after keypress and what it tells into console/application/likewise that is there when keypress is being done.
To write the file you would have to use irrecord application that comes along with lirc-utils package and do that as root, using the wanted input method and event to be readen, also not forgetting the required name of file to store information, irrecord wants you to press key to catch the time of repeats transmitter sents and later on the name of "button" you are wanting to choose.
Note: That listing can be seen with "irrecord -l" and if you choose first "key_ok", you can rename it into "Ok" later on for good and no real issues other than making certain in case of some applications to understand that of "Ok" in form of. As of writing this informative path of my own usage of remote it gets into spot of where likewise any application that has known entries or commands to be used, could be used from file known as likewise "/~.lircrc" or was it "/~.lircmd", that is user own defined commands from specific buttons to send into applications if being listen there.
In case of multimedia center application like xbmc, you need own "/~.xbmc/userdata/Lircmap.xml" (example exists in harddrive after install) or consider long path of writing an pointed application by rc/cmd by user defined values of sending an command after press from remote, where that of later is perhaps accepted in case of any possible application that can have key presses and name of likewise command is known into user.
Also on when all configuration of /etc/conf.d/lircd.conf and included keymap like /etc/lirc/lircd.conf you can read after starting "lircd" by using application "irw", where you press an key and it shows what is the command of pressing it, like "key_ok" or "Ok", determined by that of keymap made previously.
PS. Hope that made enough sense in the area, somewhat forward going to use simple matter of lirc itself and not try alternative (if any), but one that works for me and remote control of applications likewise xbmc/vdr/mplayer and some other i don't remember anymore from past.
Last edited by Jasa (2012-05-27 17:52:36)
Offline
Thanks for the details reply, Jasa. I would like to proceed without lirc. For example, as you pointed out, the arrow keys ARE functional as-is without lirc. I can open a shell, hit the "up arrow" key on the remote, and the shell behaves just like I hit the "up arrow" key on my keyboard. So, somehow, the arrow buttons are working as arrow keys on the remote -- want this native functionality without lircd.
I want the 'ok' key to map to the physical "enter" key.
I want the 'play' and 'pause' keys to map to the physical 'spacebar' key.
Offline