Patrick Boettcher wrote: >> The fact that the driver currently uses the same lookup table for both >> types of remote controls however, was perhaps not the best design >> choice. It really should be separated out, and merged with the >> regular ir-functions.c. I just never got around to it. > > I did not follow all the discussion, still I have a comment: > > I will soon work on a device where it is the driver who is doing the > decoding of the IR-frames. It is (maybe, I'm still missing some pieces > to be sure) possible to receive different protocols at the same time > with this hardware. That's good news! Needing to pass a modprobe parameter to select the protocol is not nice, and, while an ioctl will be needed to select IR protocols (as there are some hardwares where this is not possible at all), the better is to auto-detect the protocol. Cheers, Mauro. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
