<div class="gmail_quote">On Tue, Feb 9, 2010 at 4:40 AM, David Kubicek <span dir="ltr"><<a href="mailto:foceni@gmail.com">foceni@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On 02/09/2010 01:11 AM, j2u4 j2u4 wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 02/08/2010 10:01:54 PM, Michael T. Dean wrote:<br>
> This is the entire reason LIRC was invented.<br>
<br>
This remote appears as a normal keyboard,* not as an IR device...<br>
Maybe I don't understand LIRC -- does it control normal usb input<br>
devices (mouse and keyboard) as well as IR controllers?<br>
<br>
-j<br>
<br>
* actually, it appears as two devices, one is a keyboard, and the<br>
other is a mouse. It's quite the nice little jobber.<br>
<br>
</blockquote>
<br></div></div>
It doesn't by default, but you can route dev/input devices via Lirc and some Lirc drivers register their remotes into Linux INPUT framework as regular mice/keyboards.<br>
<br>
Usually, this uinput limitation doesn't concern you. It applies mostly to BT devices (like my PS3 BD remote), but for those remapping is not really required.<br>
<br>
One device appearing as two is normal, all wireless kbd/mouse combos do this. The important thing is keyfuzz can remap per device, so you're covered.</blockquote><div><br></div><div><br></div><div>Yeah, keyfuzz worked great. Exactly what I was looking for, and super easy to set up (with your instructions). Thanks again!</div>
<div><br></div><div>-j</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> </blockquote></div>