Re: drop lircd!

[Christoph B. <bar...@gm...>]

Gerd Knorr wrote:
> > This is exactly what I have planned and Manuel already has made some  
> > restructuring of the code. The major problem is time.
> 
> If you don't have time, why do you want to waste it by reimplementing
> something you could have for free?  Is there anything /dev/lirc does
> which the input layer can't handle?

Transmitting? Multiple distinguishable IR transceiver devices? Support for
pulse/space mode hardware?
Can't you see that there always will have to be a /dev/lirc device (actually
I want several minor devices) and a lirc daemon. Why should we force the TV
card IR receivers to use the input layer if we already have working drivers
that use /dev/lirc.

> I'm looking for a maintainable solution for IR support in saa7134 + cx88
> (also investigating bttv) drivers which will work _now_.  IMHO using the

Could you tell me exactly which problems with maintainability you had with
the bttv <-> lirc_gpio interface. There havn't been any changes there in
years.
The lirc_i2c drivers are mostly independent from the TV card drivers, so
what's all the fuss about.

> I'd rather hack lircd and/or liblirc_client to support the input layer
> than putting any effort into /dev/lirc.

Please go ahead.

Christoph

PS: I have committed the patch to CVS last week that adds support for the
input layer.

-- 
COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test
--------------------------------------------------
1. GMX TopMail - Platz 1 und Testsieger!
2. GMX ProMail - Platz 2 und Preis-Qualitätssieger!
3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post