Am Freitag, den 27.07.2007, 13:53 +0200 schrieb Ouattara Oumar Aziz: > > The daemon needs to be runned by the root user, we can't really cope > > with that. So every time lircd.conf is updated, lircd needs to be > > restarted, AFAIK > > Well, Why couldn't we develop a service that is launched by root at > the boot time that will change the lircd.conf and restart lircd? > > > About the LIRC config plugin, the lirc elisa input_provider has its own > > config (like all components of Elisa). The most relevant option there is > > the .lirc filename which maps actual remote keys to elisa input_event > > "actions". Elisa will ship with various .lirc files (currently there's > > one for streamzap remote and one for the apple remote). Users are > > welcome to contribute their .lirc files, we can't buy all remotes of the > > market :) > > So configuring a remote controller is in 2 steps : > - set the right .lirc file for elisa > - change the lircd.conf at the OS level > > Am I right ?
AFAIK there is going to be ONE set of keys in lirc soon. So that every remote sends the same LIRC-Internal-Key in pressing an OK-Button. I don't know how far this project is, but when it is fully working, we only have to change the lircd.conf for the remote and the lirc-file of elisa could always be the same, because the buttons stay the same. Please correct me, if I'm wrong... benjamin
