Linux Infrared Remote Control

Hi,

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=10666620

This time, I will address each point separately, starting with the key
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.conf files.
- there is so a wide variety of names defined in the various
lircd.conf files existing, all for the same key. For example, the play
button can be named
    * "PLAY" (streamzap),
    * "PLAY_DOWN" and "PLAY_UP" (animax),
    * "Play" (mceusb), ...

There are some interesting stats there:
http://arnaud.quette.free.fr/lirc/lirc-cns.html
- 104 remote definitions,
- 1073 unique key names (in case insensitive: 830)

This lack of standard has the major drawback to force a user to create
a new lircrc file which matches his remote's signal names and the
desired actions, which stops most basic user.

This also make the creation of configuration GUIs for LIRC a really hard task.
This finally do not allow remote makers to ship an LIRC conf with
their devices and officially support LIRC.

I will propose a RFC soon to begin discussion, but need the following
to be answered first:

1) the general keyname: complete name, abrev, or symbol
ie: Forward, Fwd, >>

I'm personaly for the complete, with an exception for:
- numbers: 0 to 9
- special symbols such as # * .

2) case: upper, lower or mixed (lower with upper for the first letter).
ie: FORWARD, forward, Forward

I'm personaly for the mixed.

3) separator: case, underscore, ...
ie: FastForward, FAST_FORWARD, ...

I'm personaly for the case.

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)?

Comments and feedback welcome.

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/

Hi Everyone,

I've just purchased a Logitech UltraX Media Remote which is a media
center "compatible" (whatever that means...) remote with an RF USB
dongle. A quick google before purchasing showed that is was somehow
supported under Linux but I didn't investigate to what extent. The USB
HID driver supports this remote:

http://lkml.org/lkml/2005/9/10/197

So now I'd like to use this remote with LIRC, but I'm not sure how to
do this. If I load the USB modules and then the evdev module I can see
data received on /dev/input/event1 for some keys but not others. I
understand that lircd supports reading /dev/input/event* devices but I
assume that events needs to be generated for all keys in order for
lircd to see them. Am I loading the wrong modules? Looking at the
wrong device files?

This remote seems very hard to find any information about on the
Logitech website actually, I don't know if it is maybe just an OEM
product really. All google results points to mostly European
distributors, maybe it doesn't exist on the US market? Here's a
picture anyway...

http://www.webhallen.com/prod.php?id=42167

Searching the lirc list archives didn't give any information, so any
help appreciated.

Thanks
-- 
Daniel Nilsson

Hi!

Horia Valentin CHV. Corcalciuc "sr@..." wrote:
> 	I propose a piece of code for the dev/input driver. It seems EV_SYN and
> EV_RST are identical in functionality but named different. However, the
> dev/input driver has EV_SYN which would wield an undeclared error.
> Something like:
>
> 	#ifndef EV_SYN
> 	#define EV_SYN EV_RST
> 	#fi
>
> in daemons/hw_devinput.c, or of course, better options...

Applied to CVS.

Christoph