From: <loi...@gm...> - 2007-02-28 20:56:55
|
2007/2/28, Arnaud Quette <aqu...@gm...>: > > Hi Christoph, > > 28 Feb 2007 08:11:00 +0100, Christoph Bartelmus <li...@ba...>: > > Hi! > > > > Arnaud Quette "aqu...@gm..." wrote: > > > this is the continuation of a thread started a long time ago (in a > > > galaxy not so far away ;) ): > > > http://sourceforge.net/mailarchive/message.php?msg_id=3D10666620 > > > > > > This time, I will address each point separately, starting with the ke= y > > > namespace. Also, this time I have some help (thanks to Loic Dardant), > > > and another interest > > > (https://wiki.ubuntu.com/MediaCenter/RemoteSupport). > > > > > > Well, the LIRC namespace issue is well known: > > > - there is no common namespace to describe the keys in lircd.conffile= s. > > > > I still think that we should use the namespace defined in > > /usr/include/linux/input.h > > That would enable lircd to automatically generate input events, which > > has been discussed here recently. > > as per my original post (2 years ago), so do I ;-) > I've cc'ed Vojtech Pavlik for info. > > For the recall, the linux input naming is located in > linux-X.Y.Z/include/linux/input.h > iirc again, there was some extension needed (for aux<more than 2> and > maybe other things). > > I've not digged, nor planned to, the thread you mentioned above. If > you think there are things interesting for the present sudject, please > let me know. > > > [...] > > > 2) case: upper, lower or mixed (lower with upper for the first > letter). > > > ie: FORWARD, forward, Forward > > > > Button name handling in LIRC ignores case: I don't care. > > for the signal handling no. > but for homogeneity accross the lircd.conf, and compliance to the > linux input naming, that's better. > > > [...] > > > 4) Some remote have both <button>_UP and <button>_DOWN signals. > > > What to do with these. Duplicate the signal, or keep only one (the > down > > > one)? > > > > There are very few remotes with this feature. I would probably remove > > the _DOWN from button names and keep the _UP. > > seems 1 (remote) already did so (don't recall which, but I've seen an > occurence of _UP, without _DOWN...) > > @Loic: the path seems clear. Can you take over the creation of the new > namespace? > If it's ok, let's followup priv. between frenchies ;-) It's ok for the creation of the new namespace. I'm waiting for the direction of the work. Arnaud > -- > Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt > Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ > Debian Developer - http://people.debian.org/~aquette/ > OpenSource Developer - http://arnaud.quette.free.fr/ > --=20 Lo=EFc Dardant |