From: lirc@bartelmus.de (Christoph Bartelmus)
To: vincent.vanackere@gmail.com
Cc: linux-input@atrey.karlin.mff.cuni.cz
Cc: linux-kernel@vger.kernel.org
Cc: penberg@cs.helsinki.fi
Subject: Re: [PATCH] lirc: remove backwards compatibility macro obfuscation
Date: 04 Feb 2007 04:04:00 +0100 [thread overview]
Message-ID: <AAEizONrB9B@bartelmus.de> (raw)
In-Reply-To: <65258a580702020304m52283349ne4ba2895d9ce7188@mail.gmail.com>
Hi Vincent,
on 02 Feb 07 at 12:04, you wrote:
> On 2/2/07, Pekka J Enberg <penberg@cs.helsinki.fi> wrote:
>> From: Pekka Enberg <penberg@cs.helsinki.fi>
>> [...]
>> drivers/lirc_atiusb/lirc_atiusb.c | 102 -----------------
> ^^^^^^^^^^^^^^
>
> I may be mistaken, but the lirc_atiusb module looks redondant with
> the driver already in drivers/usb/input/ati_remote.c.
> Moreover, I was under the impression that the input layer was
> currently considered the "right way" to implement the kernel side lirc
> needs
No. Using the input layer makes no sense for most lirc drivers. The
hardare used does not decode the IR signals itself but only provides raw
signal timings. Those signals are decoded in userspace by lircd.
It would be a really bad idea trying to do this decoding in kernel
space.
Christoph
next prev parent reply other threads:[~2007-02-04 3:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 8:39 [PATCH] lirc: remove backwards compatibility macro obfuscation (Was: Free Linux Driver Development!) Pekka J Enberg
2007-02-02 11:04 ` Vincent Vanackere
2007-02-04 3:04 ` Christoph Bartelmus [this message]
2007-02-02 11:10 ` Jan Dittmer
2007-02-02 11:32 ` Pekka Enberg
2007-02-02 12:51 ` Jan Dittmer
2007-02-04 3:03 ` [PATCH] lirc: remove backwards compatibility macro obfuscation Christoph Bartelmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AAEizONrB9B@bartelmus.de \
--to=lirc@bartelmus.de \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=vincent.vanackere@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox