<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
<blockquote type="cite">
<pre>>><i> Just looked at the evtest output you sent, and evtest is *not* reporting
</i>>><i> keycodes for most IR scancodes, so that explains why irw isn't either.
</i>>><i> You have Misc reports showing the scancodes, but only Key reports for a
</i>>><i> select few buttons -- lirc needs the Key reports. I'm not sure yet why
</i>>><i> there are so many keys w/o a scancode to keycode mapping though.
</i>>><i>
</i>><i> It looks like some of them are also mapped incorrectly (Radio to Power, Menu to Mute etc).
</i>><i> So I guess the next course I could take is to use setkeycodes and map them all manually.
</i>
There actually *is* a proper fix for this Coming Soon upstream, but that
doesn't exactly help your situation right now. The Hauppauge remotes
typically use one of (iirc) three device codes, 0x1d, 0x1e and 0x1f. The
ir-kbd-i2c driver has historically discarded the device code, and only
passed along the key code. Some key codes aren't exactly the same between
the various device codes. The fix is that ir-kbd-i2c will no longer eat
up the device code, but rather, pass it along, allowing for a discrete
mapping for each device/key code pair.</pre>
</blockquote>
I will wait for the fix to come then. Not a big deal. I went ahead
and got one of the VisionTek Candyboard mini keyboards to hold me
over til then. Plus I needed one anyway since I have started using
MythNetvision more.<br>
</body>
</html>