mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: columbus@hit.handshake.de (Christoph Bartelmus)
To: lirc-list@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	pavel@suse.cz
Subject: Re: [PATCH] lirc for 2.5/2.6 kernels - 20030802
Date: 09 Aug 2003 14:46:00 GMT	[thread overview]
Message-ID: <8rZ2nqa1z9B@hit-columbus.hit.handshake.de> (raw)
In-Reply-To: <1059820741.3116.24.camel@laurelin> <20030807214311.GC211@elf.ucw.cz> <1060334463.5037.13.camel@defiant.flameeyes> <20030808231733.GF389@elf.ucw.cz>

Hi!

Pavel Machek "pavel@suse.cz" wrote:

[...]
>>> * This looks like it should be integrated with drivers/input. After
>>>   all remote control is just a strange keyboard. What are reasons that
>>>   can't be done?

Because for most drivers the decoding is done in user space by the lircd
daemon.

[...]
> I know about lirc project, and I'd like to see it merged, but if lirc
> uses wrong interface, it is unsuitable for the kernel.

Is it the wrong interface?

> Motivation for having same code for infrared controls and normal
> keyboards: normal keyboards tend to have "play"/"stop"/"vol+"/"vol-"
> keys these days; certainly HP omnibook xe3 has them. It would be nice
> to handle them in an uniform way.

No problem. Feed these keys to lircd. Voila: uniform interface to all
applications.

There already is a patch for exactly that here:
http://sourceforge.net/tracker/
index.php?func=detail&aid=670000&group_id=5444&atid=305444

I didn't have the time yet to have a closer look at this patch.

Christoph

  reply	other threads:[~2003-08-09 17:17 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 [this message]
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
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=8rZ2nqa1z9B@hit-columbus.hit.handshake.de \
    --to=columbus@hit.handshake.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lirc-list@lists.sourceforge.net \
    --cc=pavel@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®