Difference between revisions of "NeTV IR driver"

From Studio Kousagi Wiki
Jump to: navigation, search
(Making the changes permanent)
 
(3 intermediate revisions by the same user not shown)
Line 45: Line 45:
 
# On your NeTV, install the newly-copied GPIO IR driver
 
# On your NeTV, install the newly-copied GPIO IR driver
 
#* insmod gpio_ir.ko
 
#* insmod gpio_ir.ko
 +
# Check to see your key is doing what you want it to:
 +
#* Run "hexdump -C /dev/input/event1"
 +
#* Press the newly-defined button.  Your output should look like the following, with the new keycode defined in the bolded field.  Press Control-C to exit:
 +
00000000  e9 06 00 00 3f b7 06 00  01 00 '''1c''' 00 01 00 00 00  |....?...........|
 +
00000010  e9 06 00 00 a4 87 0a 00  01 00 '''1c''' 00 02 00 00 00  |................|
 +
00000020  e9 06 00 00 ba 87 0a 00  01 00 '''1c''' 00 00 00 00 00  |................|
 +
 +
==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 [https://github.com/sutajiokousagi/linux-2.6.28-silvermoon/blob/netv/src/drivers/input/gpio_ir.c#L75 nikon_key_table] array, along with the keycode.  Possible keycodes are listed in [https://github.com/sutajiokousagi/linux-2.6.28-silvermoon/blob/netv/src/include/linux/input.h#L121 input.h].
 +
# Save and rebuild the GPIO IR driver, as mentioned above
 +
 +
==Making the changes permanent==
 +
Once you have your changes made, you'll want to have them automatically load at boot.  To do that, you will need to modify the kernel configuration to compile gpio_ir as a builtin rather than as a module.
 +
# Convert the IR driver from a module to a builtin
 +
#* make menuconfig
 +
#* Go to Device Drivers ---> Input Device Support ---> CIR device and set it from <M> to <*> by moving the cursor over it and hitting "Y"
 +
#* 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
 +
#* Remove the following from the very top of the file:
 +
#** #define DEBUG
 +
#* Save and quit:
 +
#** Control-X, Y, Enter
 +
# Build a new kernel
 +
#* make
 +
# 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
 +
#* reboot

Latest revision as of 09:39, 16 April 2012

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.

  1. Install and configure the NeTV toolchain
  2. Enable SSH on your NeTV
  3. Check out the kernel
  4. Grab the latest config file
  5. 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
  6. 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
  7. Build a new kernel
    • make
  8. Copy the kernel to your NeTV
    • scp arch/arm/boot/zImage root@[NeTV-address]:
  9. On your NeTV, write the new kernel
    • config_util --cmd=putblock --block=krnA < zImage
  10. On your NeTV, reboot into the new kernel
    • reboot

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.

  1. Make changes to drivers/input/gpio_ir.c
  2. Rebuild kernel modules
    • make modules
  3. Copy gpio_ir.ko to your NeTV
    • scp drivers/input/gpio_ir.ko root@[NeTV-address]:
  4. On your NeTV, make sure the GPIO IR driver is not installed
    • rmmod gpio_ir
  5. On your NeTV, install the newly-copied GPIO IR driver
    • insmod gpio_ir.ko
  6. Check to see your key is doing what you want it to:
    • Run "hexdump -C /dev/input/event1"
    • Press the newly-defined button. Your output should look like the following, with the new keycode defined in the bolded field. Press Control-C to exit:
00000000  e9 06 00 00 3f b7 06 00  01 00 1c 00 01 00 00 00  |....?...........|
00000010  e9 06 00 00 a4 87 0a 00  01 00 1c 00 02 00 00 00  |................|
00000020  e9 06 00 00 ba 87 0a 00  01 00 1c 00 00 00 00 00  |................|

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.

  1. Load the module as described above
  2. Run the following command on your NeTV to monitor syslog events:
    • logread -f
  3. Point your remote control at your NeTV and press a button
  4. 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
  5. Edit drivers/input/gpio_ir.c
  6. Add the code mentioned to the nikon_key_table array, along with the keycode. Possible keycodes are listed in input.h.
  7. Save and rebuild the GPIO IR driver, as mentioned above

Making the changes permanent

Once you have your changes made, you'll want to have them automatically load at boot. To do that, you will need to modify the kernel configuration to compile gpio_ir as a builtin rather than as a module.

  1. Convert the IR driver from a module to a builtin
    • make menuconfig
    • Go to Device Drivers ---> Input Device Support ---> CIR device and set it from <M> to <*> by moving the cursor over it and hitting "Y"
    • Select < Exit > repeatedly, answer < Yes > when it asks you to save your new kernel configuration
  2. Enable DEBUG mode in the GPIO IR driver
    • nano -w drivers/input/gpio_ir.c
    • Remove the following from the very top of the file:
      • #define DEBUG
    • Save and quit:
      • Control-X, Y, Enter
  3. Build a new kernel
    • make
  4. Copy the kernel to your NeTV
    • scp arch/arm/boot/zImage root@[NeTV-address]:
  5. On your NeTV, write the new kernel
    • config_util --cmd=putblock --block=krnA < zImage
  6. On your NeTV, reboot into the new kernel
    • reboot