Skip to contentSkip to conversation

In-kernel IR remote control support

DISCUSSION Maxim Levitsky 1 participant 1 message Nov 14, 2008 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 13134331.2018681226657305244.JavaMail.www@wwinf8303

#1 lore raw
Quoted 62 lines · Emmanuel Fust

Hi,

Quoted 9 lines
Quoted 8 lines · Christoph Bartelmus

Hi,

on 12 Nov 08 at 14:39, J.R. Mauro wrote:
[...]

Quoted 4 lines · Jon Smirl
Quoted 3 lines · J.R. Mauro
Quoted 2 lines · Jon Smirl
Quoted 1 line

New release of in-kernel IR support implementing evdev support.

The goal

Quoted 12 lines
Quoted 12 lines
Quoted 11 lines
Quoted 11 lines
Quoted 8 lines
Quoted 3 lines

of in-kernel IR is to integrate IR events into the evdev input event queue and maintain ordering of events from all input devices. Still looking for help with this project.

(Forgive me if this has already been asked or dealt with)

Have you contacted the LIRC developers? Is there any overlap between your projects?

The LIRC people know about this. Pieces of the code are coming from the LIRC source base and being reworked for kernel inclusion.

Quoted 6 lines
Quoted 6 lines
Quoted 1 line

Great, it's nice to see there's cooperation.

LOL. There's just a small omission from Jon's side... Yes, LIRC people know about this. And Jon has a no-go from me.

Decoding IR protocols in-kernel is the wrong way IMHO and this will

not be

Quoted 2 lines
Quoted 2 lines

supported by LIRC as long as I maintain LIRC.
It's simply not possible to decode all existing IR protocols and

LIRC just

Quoted 1 line
Quoted 1 line

stores the timing data for these protocols as-is without trying to

decode

Quoted 2 lines
Quoted 2 lines

them. With the in-kernel decoding approach these remotes cannot be supported. I'm not willing to sacrifice the support for these even

though

Quoted 7 lines
Quoted 1 line

they only consist of a very small fraction of remotes in use.

+1

I agree completely.
This way we can make lirc to recognize any remote.

Don't yet have a general receiver, but when I have one, I would like

to use my remotes,

Quoted 4 lines

and who knows what protocols they use...

Best solution is to make new input layer message, a raw PCM data.

No, raw PCM data has nothing to do as an input layer message. Is is not an input event.

Quoted 1 line

or, you can even keep the daemon, but make it inject input events back

to input system.

Quoted 1 line

Exactly as Jon designed it. Use the raw sysfs interface to get raw data and inject input events back to input system.

Quoted 1 line

The only think I don't like at all about lirc is that you need special

library to talk

Quoted 2 lines

to it while I want remotes to be used as a keyboards.

Quoted 7 lines
Quoted 3 lines

Btw, one can write a lirc client that does the above, but this is hackish.

Some standard ir protocols can be decoded in kernel, but there should

be standard

Quoted 1 line

(not debug) way to do so in userspace.

Call it raw instead of debug and you're done. Lircd will be the main if not the only regular user of this raw interface.

I was under impression that sysfs interface isn't fit for everyday use. Is it at least possible to receive a continuous stream of data? Then lets rename it to regular not debug interface.

Quoted 2 lines

Jon did a wonderful jobs, it's thin, simple, clean and fit perfectly with the input system. No more specialized libs. With a little work, existing decoders could cover more than 70% the IR remotes. With more engines, we could rapidly cover more than 95% of know IR protocols. A simplified lircd could at any time cover the rest.

Best regards,
Maxim Levitsky

Quoted 9 lines

Bests regards,
Emmanuel.
---

/Créez votre adresse <http://www.laposte.net> électronique [email protected] 1 Go d'espace de stockage, anti-spam et anti-virus intégrés./