NeTV IR driver
NeTV uses a GPIO-based IR sensor. That means that it's simply counting the pattern of 0s and 1s coming from a sensor that performs IR detection and demodulation.
There is currently no LIRC driver. Instead, it acts as a keyboard driver, using a hard-coded set of scancodes and key equivalents. By modifying the driver, it's possible to add new keys or to change the mapping.
Note that it might be useful to build the kernel as a module. That way you can try new code without having to reboot.
These steps instruct you on how to load a new kernel onto your device. Any time you modify the kernel, you risk making your system unbootable. Do not continue unless you are familiar with how to re-image your SD card.
Setting up your build environment
These steps will set up an environment that will allow you to modify the IR kernel drivers. These steps only need to be completed once.
- Install and configure the NeTV toolchain
- Enable SSH on your NeTV
- Check out the kernel
- git clone git://github.com/sutajiokousagi/linux-2.6.28-silvermoon.git; cd linux-2.6.28-silvermoon/src/; git checkout netv
- Grab the latest config file
- Convert the IR driver from a builtin to a module
- make menuconfig
- Go to Device Drivers ---> Input Device Support ---> CIR device and set it from <*> to <M>
- Select < Exit > repeatedly, answer < Yes > when it asks you to save your new kernel configuration
- Enable DEBUG mode in the GPIO IR driver
- nano -w drivers/input/gpio_ir.c
- Add the following to the very top of the file:
- #define DEBUG
- Save and quit:
- Control-X, Y, Enter
- Build a new kernel
- Copy the kernel to your NeTV
- scp arch/arm/boot/zImage root@[NeTV-address]:
- On your NeTV, write the new kernel
- config_util --cmd=putblock --block=krnA < zImage
- On your NeTV, reboot into the new kernel
Modifying the GPIO IR driver
Every time you make changes to the GPIO driver, you must rebuild the module, copy the kernel object over, and reload it. You do not need to reboot your NeTV unless there is a problem with resource management, or if there is a crash in the driver.
- Make changes to drivers/input/gpio_ir.c
- Rebuild kernel modules
- make modules
- Copy gpio_ir.ko to your NeTV
- scp drivers/input/gpio_ir.ko root@[NeTV-address]:
- On your NeTV, make sure the GPIO IR driver is not installed
- rmmod gpio_ir
- On your NeTV, install the newly-copied GPIO IR driver
- insmod gpio_ir.ko
Adding new IR codes
When DEBUG mode is enabled, the driver will report all unrecognized keycodes. Use logread to report these keycodes, then add them to the driver and rebuild.
- Load the module as described above
- Run the following command on your NeTV to monitor syslog events:
- logread -f
- Point your remote control at your NeTV and press a button
- Note the message that gets printed. It will be something of the form:
- Apr 16 16:46:24 chumby-silvermoon-netv user.debug kernel: [ 1262.366693] aspenite-cir aspenite-cir.0: No key found for code 0xfd027d82
- Edit drivers/input/gpio_ir.c
- Add the code mentioned to the nikon_key_table array, along with the keycode. Possible keycodes are listed in input.h.
- Save and rebuild the GPIO IR driver, as mentioned above