irTrans lirc_serial bug...

[Baxter K. <bax...@gm...>]

Hi. I'm curious if there's a specific solution to this problem:

I have an mce-keyboard and remote combo that happened to come standard with
my case. The case itself has an integrated irTrans receiver.

As far as I know, I've not seen mention of using lirc with the reciever
since irTrans produces their own irserver software which is compatible with
most lirc clients. The problem comes in that I can't figure out what client
to use to act as a keyboard input driver (if such a one exists). I'm aware
of the mod_mce and mce_lircd work and have suspicion that mce_lircd would
suit my needs except that it specifically listens for /dev/lirc/0 which is a
device interface that I'm not aware of irserver possessing. (Irserver
connects to ttyUSB0 but I am going to assume that this is a raw interface
and does not use the same socket / compatibility layer as lirc).

I tried to use lirc serial (since the irTrans receiver is dependent upon the
ftdi_sio usb-serial input driver) but received the following on dmesg when
modprobing lirc_serial:

-----------------------------------------------------------
lirc_dev: IR Remote Control driver registered, at major 61
printk: 118 messages suppressed.
BUG: using smp_processor_id() in preemptible [00000001] code: modprobe/28631
caller is init_module+0x156/0x30e [lirc_serial]

Call Trace:
 [<ffffffff8020b10a>] show_trace+0x34/0x47
 [<ffffffff8020b12f>] dump_stack+0x12/0x17
 [<ffffffff803da0e4>] debug_smp_processor_id+0xb4/0xc4
 [<ffffffff88938197>] :lirc_serial:init_module+0x156/0x30e
 [<ffffffff80249647>] sys_init_module+0xaf/0x21c
 [<ffffffff8020987e>] system_call+0x7e/0x83
 [<00002b1c7e2e37ba>]

lirc_serial: auto-detected active low receiver
lirc_dev: lirc_register_plugin: sample_rate: 0
-----------------------------------------------------------

At this point I'm unsure what the best solution would be and I'm willing to
get my hands a little dirty (amateurish skill considering).

I was never comfortable with the idea of the irTrans irserver 'fork' as it
were so resolving lirc driver compatibility would solve it. At the same time
I recognize how wonderful/useful it would be to have a socket compatible
generalized keyboard / mouse console input driver/application that's lirc
compatible (and configurable via .lircrc).

Any and all thoughts are appreciated and thank you for the great work thus
far.

~Chad