On 07/10/05, Larry K <[EMAIL PROTECTED]> wrote: > Joe, Thanks for the info. > > That fact that the buttons can have arbitrary names explains a lot. > > I'm wondering how I will know what kernel modules support this 3rd party IR > receiver? The seller said it works with mythtv, so it probably does. If I > hack my Hauppauge IR sensor to connect via serial port, will that work with > my existing setup? I'm thinking it might. > > Also, you state that the EFC codes match up with what is defined in the > lircd.conf. I'm not seeing that. For instance, Jarod defines the the SLEEP > button with EFC code 241, but the sleep code in lircd.conf is not 240. It > is: > > SLEEP 0x0000000000000166 > > I can't see how Hex. 166 matches up with Dec. 240. (x'166' is 358, as you > probably know.) I have been unable to match any of the EFC codes to the > codes in lircd.conf. This is particularly vexing.
They don't match, or need to. 240 is the code you enter into the remote to make the button generate a particular optical code. 166 is the code that the kernel module generates when it sees the above optical signal. _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
