On Apr 8, 2011, at 2:38 PM, Devin Heitmueller wrote: ... > I question the notion of introducing the requirement that all keymap > definitions must have system codes without having really thought > through the notion that it would result in breaking every existing > keymap which hadn't been updated.
Speaks the the "too many of us are only hacking on this in their limited free time" point I raised. Hack, hack, hack, test with the hardware available on hand (which is actually quite a bit in my case, I think I have upwards of 35 receivers and even more remotes now), see that it works, move on to the next issue. I'm certainly guilty of not looking at the bigger picture and thinking about possible ramifications more than once. :) ... >> I have quite a few pieces of Hauppauge hardware, several with IR >> receivers and remotes, but all of which use ir-kbd-i2c (or >> lirc_zilog), i.e., none of which pass along raw IR. > > You don't have an HVR-950 or some other stick which announces RC5 > codes? If not, let me know and I will send you something. It's kind > of silly for someone doing that sort of work to not have at least one > product in each category of receiver. I don't think I even fully realized before today that there was Hauppauge hardware shipping with the grey remotes and a raw IR receiver. All the Hauppauge stuff I've got is either i2c IR (PVR-250, PVR-350, HVR-1950, HD-PVR) or came with a bundled mceusb transceiver (HVR-1500Q, HVR-1800, HVR-950Q -- model 72241, iirc), and its all working these days (modulo some quirks with the HD-PVR that still need sorting, but they're not regressions, its actually better now than it used to be). So yeah, I guess I have a gap in my IR hardware collection here, and would be happy to have something to fill it. -- Jarod Wilson ja...@wilsonet.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
