Very common infrared remotes not registered

[Claudiu Vlad]

Binary package hint: hal-info

Relevant code is missing for some very common infrared remotes, so those are not registered. For example, the Conexant cxx remote, found on the very popular Winfast tv tuners. I attached the lirc.fdi file as it was modified by me, in order to be able to use my Winfast 2000XP IR remote.

[Martin Pitt (pitti)]

Can you please explain how setting info.ignore makes it work, and why? How does that device appear in lshal if you arne't using those rules?

[Claudiu Vlad (claudiu-vlad)]

It seems that the ignore rule makes the hal system IGNORE the infrared
remote, so that lirc can register the remote.
Without this rule, the computer thinks my remote is a keyboard, reading only
the Enter key and the digits. So, basicly, the rule says something like
"this is a IR remote, m.f., leave it alone, its for LIRC to use".

Cheers,

On Tue, Feb 10, 2009 at 5:16 PM, Martin Pitt <email address hidden> wrote:

> Can you please explain how setting info.ignore makes it work, and why?
> How does that device appear in lshal if you arne't using those rules?
>
> ** Changed in: hal-info (Ubuntu)
> Status: New => Incomplete
>
> --
> Very common infrared remotes not registered
> https://bugs.launchpad.net/bugs/322483
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Martin Pitt (pitti)]

Ah, thanks. Can you please do

  lshal > /tmp/hal.txt

and attach it here?

[Claudiu Vlad (claudiu-vlad)]

Here it is...

Cheers,

[Martin Pitt (pitti)]

Thanks. Currently discussing with upstream where this file should be placed best; I'm currently leaning towards lirc, thus tentatively reassinging this. I'll wait a couple of days for comments, and then apply it.

http://lists.freedesktop.org/archives/hal/2009-February/012977.html

[Claudiu Vlad (claudiu-vlad)]

If theyre planning to have evdev work with IR remotes, they will have to
collect lots of remote specs. Maybe the HardwareTesting info collector
in System->Administration could include scanning for IRremotes keycodes.

Anywas, for the time, evdev should IGNORE the remotes, as long as its
not capable of handling them.

Cheers,

On Thu, 2009-02-12 at 19:54 +0000, Martin Pitt wrote:
> Thanks. Currently discussing with upstream where this file should be
> placed best; I'm currently leaning towards lirc, thus tentatively
> reassinging this. I'll wait a couple of days for comments, and then
> apply it.
>
> http://lists.freedesktop.org/archives/hal/2009-February/012977.html
>
> ** Changed in: lirc (Ubuntu)
> Sourcepackagename: hal-info => lirc
> Assignee: (unassigned) => Martin Pitt (pitti)
> Status: Incomplete => Triaged
>

[Martin Pitt (pitti)]

Do the other keys not produce any input event at all (in input-events), or are they just >= 256, so that X.org cannot use them?

[Claudiu Vlad (claudiu-vlad)]

I can't tell, but I think this file should give all the info we need...
I has the remote key codes - ALL WORKING AND TESTED.
I would like to stress the fact that this is a more general problem, as
the bug title says! So its not about a stupid Winfast remote, but its a
real need to include in the ubuntu configurations files the most common
hardware, so that most complains wouldnt happen at all.

On Fri, 2009-02-13 at 10:41 +0000, Martin Pitt wrote:
> Do the other keys not produce any input event at all (in input-events),
> or are they just >= 256, so that X.org cannot use them?
>

[Claudiu Vlad (claudiu-vlad)]

I just upgraded to Jaunty J amd64 and noticed this file
[00:57][claudiu:/>~]$ cat /usr/share/hal/fdi/preprobe/20thirdparty/lirc.fdi
<?xml version="1.0" encoding="UTF-8"?>

<deviceinfo version="0.2">
  <device>
     <match key="info.product" contains_ncase="saa7134 ir">
        <merge key="info.ignore" type="bool">true</merge>
     </match>
     <match key="info.product" contains_ncase="IR-Receiver">
        <merge key="info.ignore" type="bool">true</merge>
     </match>
     <match key="info.product" contains_ncase="cx88 IR">
        <merge key="info.ignore" type="bool">true</merge>
     </match>
     <match key="info.product" contains_ncase="bttv IR">
        <merge key="info.ignore" type="bool">true</merge>
     </match>
  </device>
</deviceinfo>

Does this mean it is fixed in Ubuntu 9.04 ? Can you confirm it ?