Posts: 3,735
Joined: Dec 2010
Reputation:
53
negge
yo guysv7may bd latr tomorroe
Posts: 3,735
@FishOil: While your guide is very nice, I don't really see how it relates to this. This is about handing over control of a remote to LIRC instead of having the kernel do the job (which is less flexible), not about starting from scratch.
Posts: 3,735
Joined: Dec 2010
Reputation:
53
negge
yo guysv7may bd latr tomorroe
Posts: 3,735
It's not exactly what I'm trying to accomplish here, like I already explained this is about making a fully out-of-the-box thing work a bit better by allowing LIRC to handle the remote instead of the kernel. If you have a remote that is already supported by LIRC there is no need to use your guide in order to make it work since all the buttons are already mapped.
Posts: 3,735
Joined: Dec 2010
Reputation:
53
negge
yo guysv7may bd latr tomorroe
Posts: 3,735
@blm14: I believe you still need this hack.
Posts: 196
Joined: Nov 2009
Reputation:
0
blm14
Senior Member
Posts: 196
Are you still running ancient 2.6 kernels? There is no reason not to be using LIRC for remotes... I have installed XBMC fresh on no fewer than 18 machines in the past year, all of them on different hardware, and all of them with remotes, and I only once had to do anything with ~/.xbmc/keymappings and I never had to do this hack
Posts: 3,735
Joined: Dec 2010
Reputation:
53
negge
yo guysv7may bd latr tomorroe
Posts: 3,735
The whole point of this is to make use of LIRC instead of having the kernel handle the remote. I guess you have only used remotes that the kernel doesn't handle, and thus LIRC gets used automatically.
Posts: 196
Joined: Nov 2009
Reputation:
0
blm14
Senior Member
Posts: 196
The whole point of LIRC is to not have to rely upon depmodding drivers into the kernel. I still don't understand why you don't just use LIRC?
Posts: 3,735
Joined: Dec 2010
Reputation:
53
negge
yo guysv7may bd latr tomorroe
Posts: 3,735
What have I written that makes you think I don't "use LIRC"? This is exactly about using LIRC, not anything else.