public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Flameeyes <daps_mls@libero.it>,
	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: Mon, 11 Aug 2003 17:41:43 +0200	[thread overview]
Message-ID: <20030811154143.GD2627@elf.ucw.cz> (raw)
In-Reply-To: <20030811144242.GE4562@www.13thfloor.at>

Hi!

> > > I converted lirc_gpio into input/ layer (and killed support for
> > > hardware I do not have; sorry but it was essential to keep code
> > > small). Ported driver looks like this; I believe it looks better than
> > > old code. Patch is here.
> > You can here see the problem... not all tv cards use the same remote,
> > the switch doesn't work with my remote for example, so we have 2
> > possibilities:
> > 
> > a) hardcode all the possible remotes adding these as new one come up,
> > this is a big work in the kernel source, and also we lost compatibility
> > with remotes that use the same frequency of the ones with the tv card,
> > and that now can be used.
> > 
> > b) create an userspace utility that read the input layer for codes an
> > then translates them in user-definable commands. This is what lircd do
> > now...
> 
> what about 
>   
>   c) hardcode the basic decoding and use a mapping table
>      which can be configure from userspace ...
>      (like dvbs haupauge or xmodmap)

Acceptable, too; but I'd like remotes to work out-of-the-box, without
any config.

Of course, if you have homemade serial receiver, you should still be
able to use it, but in such case lircd solution is acceptable.
								Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  reply	other threads:[~2003-08-11 15:42 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-02 10:39 [PATCH] lirc for 2.5/2.6 kernels - 20030802 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 [this message]
2003-08-11 18:40               ` Gerd Knorr
2003-08-11 15:38             ` Pavel Machek
2003-08-11 15:48               ` Flameeyes
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=20030811154143.GD2627@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=columbus@hit.handshake.de \
    --cc=daps_mls@libero.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lirc-list@lists.sourceforge.net \
    --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