Am 10.12.2012 18:57, schrieb Antti Palosaari: > On 12/10/2012 06:13 PM, Devin Heitmueller wrote: >> On Mon, Dec 10, 2012 at 11:01 AM, Frank Schäfer >>> Adding a new property to the RC profile certainly seems to be the >>> cleanest solution. >>> Do all protocols have paritiy checking ? Otherwise we could add a new >>> type RC_TYPE_NEC_NO_PARITY. >>> OTOH, introducing a new bitfield in struct rc_map might be usefull for >>> other flags, too, in the future... >> >> It's probably also worth mentioning that in that mode the device >> reports four bytes, not two. I guess perhaps if parity is ignored it >> reports the data in some other format? You will probably have to do >> some experimentation there. > > Uh, current em28xx NEC implementation is locked to traditional 16 bit > NEC, where is hw checksum used. > > Implementation should be changed to more general to support 24 and 32 > bit NEC too. There is multiple drivers doing already that, for example > AF9015. > Hmm... are there and documents (, links, books, ...) where I can learn more about all those RC protocols ? Regards Frank -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
