lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 28 Nov 2009 09:04:27 +0000 From: Simon Kenyon <simon@...la.ie> To: unlisted-recipients:; (no To-header on input) CC: linux-input@...r.kernel.org, linux-kernel@...r.kernel.org, linux-media@...r.kernel.org Subject: Re: [RFC] What are the goals for the architecture of an in-kernel IR system? Christoph Bartelmus wrote: > A user friendly GUI tool to configure the mapping of the remote buttons is > essential for good user experience. I hope noone here considers that users > learn command line or bash to configure their remotes. oh please no the major, major problem with bluetooth is that there is *only* a gui the core system should use the command line and then a gui (or guis) can follow > Nobody is manually writing lircd.conf files. Of course you don't want the > user to know anything about the technical details unless you really want > to get your hands dirty. speak for yourself > If it ain't broke, don't fix it. i have been hacking lirc for *so many years* because i needed two separate serial inputs. so that is most assuredly broken -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists