[nickr]

I'll verify this with OE once I get my dual boot sorted out. Then I need to figure out where to get a suitable remote..

Here are the steps in OE:

Code:

i5-nuc:~ # modprobe -r nuvoton_cir
i5-nuc:~ # echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
i5-nuc:~ # modprobe nuvoton-cir
i5-nuc:~ # dmesg | tail -20
[    5.761398] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[    5.761442] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  185.961113] pnp 00:08: [io  0x0240-0x024f]
[  185.961150] pnp 00:08: [irq 3]
[  185.961155] pnp 00:08: [io  0x0250-0x025f]
[  190.799643] Registered IR keymap rc-rc6-mce
[  190.799918] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:08/rc/rc0/input10
[  190.800584] rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:08/rc/rc0
[  190.804930] IR NEC protocol handler initialized
[  190.805066] IR RC5(x) protocol handler initialized
[  190.806204] IR RC6 protocol handler initialized
[  190.807553] IR JVC protocol handler initialized
[  190.808110] IR Sony protocol handler initialized
[  190.810806] IR SANYO protocol handler initialized
[  190.813132] nuvoton_cir: driver has been successfully loaded
[  190.816138] input: MCE IR Keyboard/Mouse (nuvoton-cir) as /devices/virtual/input/input11
[  190.816359] IR MCE Keyboard/mouse protocol handler initialized
[  190.816656] lirc_dev: IR Remote Control driver registered, major 248
[  190.817131] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0
[  190.817133] IR LIRC bridge handler initialized

I'm not sure how things should be configured after this - it looks like there is an input device and a lirc device that could be used. Now I just need to get an MCE remote..

Also, I wonder what the right way is to fix this. Is the ACPI data incorrect, or is the driver supposed to enable the device before validating the resources?

The kernel has a db of devices (vid:pid) that each driver maps to. Sometimes new devices come along that can still use the driver but their vid:pid aren't in the database. Thr kernel won't automatically load the driver but it can still be loaded manually. This may be possible yo fix in modeprobe.conf.