From: Flameeyes <dgp85@users.sourceforge.net>
To: Pavel Machek <pavel@suse.cz>
Cc: Christoph Bartelmus <columbus@hit.handshake.de>,
LIRC list <lirc-list@lists.sourceforge.net>,
LKML <linux-kernel@vger.kernel.org>,
vojtech@suse.cz
Subject: Re: [PATCH] lirc for 2.5/2.6 kernels - 20030802
Date: 11 Aug 2003 17:48:52 +0200 [thread overview]
Message-ID: <1060616931.8472.22.camel@defiant.flameeyes> (raw)
In-Reply-To: <20030811153821.GC2627@elf.ucw.cz>
On Mon, 2003-08-11 at 17:38, Pavel Machek wrote:
> I guess a) is okay. There are not *so* many remote controls out there.
I think more than one per card model. Other Kworld Card have different
remote than mine, as you can see on my homepage, my lircd.conf isn't one
of the ones in lirc remotes list.
> I guess thats okay; if I want decoder-that-decodes-anything, I need
> one that connects to serial port and has non-trivial configuration.
But I can't take a new tv card, plug it into my machine, start up,
configure the remote, and use xine.
Also, from user apps dev view, I think is more difficult to check for
input events knowing that every remote has different buttons, instead of
configure the .lircrc and use lirc_client for receive directly
software-commands.
We can drop /dev/lirc*, and use input events with received codes, but I
think that lircd is still needed to translate them into userland
commands...
--
Flameeyes <dgp85@users.sf.net>
next prev parent reply other threads:[~2003-08-11 15:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 10:39 Flameeyes
2003-08-07 21:43 ` Pavel Machek
2003-08-08 9:21 ` Flameeyes
2003-08-08 23:17 ` Pavel Machek
2003-08-09 14:46 ` Christoph Bartelmus
2003-08-11 12:47 ` Pavel Machek
2003-08-11 13:11 ` Flameeyes
2003-08-11 14:42 ` Herbert Pötzl
2003-08-11 15:41 ` Pavel Machek
2003-08-11 18:40 ` Gerd Knorr
2003-08-11 15:38 ` Pavel Machek
2003-08-11 15:48 ` Flameeyes [this message]
2003-08-11 16:39 ` Gerd Knorr
2003-08-11 17:56 ` Johannes Stezenbach
2003-08-11 18:55 ` Pavel Machek
2003-08-11 18:59 ` Vojtech Pavlik
2003-08-11 19:17 ` Pavel Machek
2003-08-11 19:34 ` Vojtech Pavlik
2003-08-11 19:55 ` Pavel Machek
2003-08-11 19:59 ` Valdis.Kletnieks
2003-08-11 20:13 ` Vojtech Pavlik
2003-08-11 19:22 ` Pavel Machek
2003-08-14 15:22 ` Dennis Björklund
2003-08-14 16:06 ` Gerd Knorr
2003-08-11 18:52 ` Pavel Machek
2003-08-11 20:01 ` Flameeyes
2003-08-11 17:35 ` Johannes Stezenbach
2003-08-11 18:57 ` Pavel Machek
2003-08-11 18:31 ` Gerd Knorr
2003-08-11 18:59 ` Pavel Machek
2003-08-11 19:54 ` Gerd Knorr
2003-08-11 20:04 ` Pavel Machek
2003-08-11 13:14 ` Pavel Machek
2003-08-09 19:15 ` Flameeyes
2003-08-11 11:10 ` Pavel Machek
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=1060616931.8472.22.camel@defiant.flameeyes \
--to=dgp85@users.sourceforge.net \
--cc=columbus@hit.handshake.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lirc-list@lists.sourceforge.net \
--cc=pavel@suse.cz \
--cc=vojtech@suse.cz \
/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
all inboxes | Powered by JetHome®