Hi! Es schrieb David Atkinson: > > Hi Wieslaw, > > Wieslaw Kierbedz wrote: > > Uz.ytkownik hermann pitton napisa?: > > Hard life of ignorant :(. > > Maybe these are stupid questions but excuse full layman. > > I did not compiled neither evdev nor joydev - do I need it to set > > ir-common (I mean input/eventX) working (evdev sounds good)? > > You definately need evdev. I don't think you need joydev. > It looks like you don't even need evdev to see some first function. Numbers and enter just work straight through. With evdev and the tools from Gerd's input you can easily define and load a new keymap appropriate to the app you want to control via remote. According to what "./list" shows I get with "./kbd 2 > FV3k-keys" a file to edit. From the keyboard-map "./kbd 1 > keyboard-keys" (or from input.h) I replace those I want and, i.e. use for tvtime 103 for KEY_UP and 108 for KEY_DOWN. With "/kbd -f new-settings 2" this works immediately. So that is made very nice. > > Compiling lirc I supposed, that devinput is right choice for driver but > > of course I am not sure of that. > > Yes, devinput is the correct driver. > > > Could you explain me shortly how it works (I mean some schema like: > > hardware - ir-common(sa7134?) - evdev - /dev/input/eventX - lircd? > > That looks pretty much right to me :) The saa7134 driver creates an > input device for the remote control. evdev is required in order to be > able to access that input device via /dev/input/eventX. The devinput > driver for lirc reads from /dev/input/eventX. > > After modprobing saa7134 and evdev, you can use the list command in > Gerd's input device tools to find out which input device has the remote > on it (eg. for me it is /dev/input/event2), then fire up lircd with > lircd -d /dev/input/eventX. > Greetings Hermann
