On Mon, Nov 23, 2009 at 9:14 AM, Krzysztof Halasa <khc@xxxxxxxxx> wrote: > I think this makes a lot of sense. > But: we don't need a database of RC codes in the kernel (that's a lot of > data, the user has to select the RC in use anyway so he/she can simply > provide mapping e.g. RC5<>keycode). Just bear in mind that with the current in-kernel code, users do *not * have to manually select the RC code to use if they are using the default remote that shipped with the product. This helps alot for those unfamiliar with LIRC, since their product "works out of the box" with the remote the product came with. I agree though, that the user should be able to easily change the RC to be used if he/she decides to use a remote other than the default. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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
