From: Nicolas Will <nico@youplala.net>
To: Jonas Anden <jonas@anden.nu>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
Date: Tue, 19 Feb 2008 22:16:48 +0000 [thread overview]
Message-ID: <1203459408.28796.19.camel@youkaida> (raw)
In-Reply-To: <1203457264.8019.6.camel@anden.nu>
On Tue, 2008-02-19 at 22:41 +0100, Jonas Anden wrote:
>
> > In any case, especially to that problem with "unknown key code" I
> think it
> > is time to change the IR-behavior of the DVB-USB.
> >
> > My problem is, I don't know how.
> >
> > My naive idea would be, that the IR-code is reporting each key (as
> raw as
> > possible) without mapping it to an event to the event interface and
> then
> > someone, somewhere is interpreting it. Also forward any
> repeat-attribute.
>
> I would suggest creating a netlink device which lircd (or similar) can
> read from.
Be ready to discount my opinion, I'm not too good at those things.
Wouldn't going away from an event interface kill a possible direct link
between the remote and X?
The way I see it, LIRC is an additional layer that may be one too many
in most cases. From my point of view, it is a relative pain I could do
without. But I may have tunnel vision by lack of knowledge.
Nico
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-02-19 22:17 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 15:17 [linux-dvb] [patch] support for key repeat with dib0700 ir receiver Filippo Argiolas
2008-02-19 17:21 ` Nicolas Will
2008-02-19 17:30 ` Filippo Argiolas
2008-02-19 19:19 ` Nicolas Will
2008-02-19 19:30 ` Nicolas Will
2008-02-19 21:10 ` Matthew Vermeulen
2008-02-19 22:09 ` Nicolas Will
2008-02-20 7:39 ` Matthew Vermeulen
2008-02-20 7:54 ` Nicolas Will
2008-02-20 13:10 ` Matthew Vermeulen
2008-02-20 8:22 ` Filippo Argiolas
2008-02-20 8:27 ` Filippo Argiolas
2008-02-20 12:36 ` Matthew Vermeulen
2008-02-20 13:23 ` Nicolas Will
2008-02-20 13:43 ` Matthew Vermeulen
2008-02-20 14:15 ` Filippo Argiolas
[not found] ` <1203517472.6682.37.camel@acropora>
2008-02-20 20:09 ` Patrik Hansson
2008-02-20 22:57 ` Matthew Vermeulen
2008-02-20 23:08 ` Matthew Vermeulen
2008-02-20 8:22 ` Filippo Argiolas
2008-02-19 21:14 ` Patrick Boettcher
2008-02-19 21:41 ` Jonas Anden
2008-02-19 22:16 ` Nicolas Will [this message]
2008-02-19 22:29 ` Patrick Boettcher
2008-02-19 22:50 ` hermann pitton
2008-02-20 4:18 ` Supported device? Lyal Collins
2008-02-19 22:52 ` [linux-dvb] [patch] support for key repeat with dib0700 ir receiver Nicolas Will
2008-02-20 9:00 ` Jonas Anden
2008-02-20 2:05 ` Darren Salt
2008-02-20 9:27 ` Filippo Argiolas
2008-02-20 9:39 ` Nicolas Will
2008-02-20 10:06 ` Filippo Argiolas
2008-03-02 19:45 ` Filippo Argiolas
2008-03-10 22:17 ` Nicolas Will
2008-02-27 11:04 ` Nicolas Will
-- strict thread matches above, loose matches on Subject: below --
2008-02-19 16:33 Eduard Huguet
2008-02-19 16:49 ` Filippo Argiolas
2008-02-19 17:07 ` Eduard Huguet
[not found] <mailman.77.1203547335.926.linux-dvb@linuxtv.org>
2008-02-21 9:54 ` Eduard Huguet
2008-02-21 15:42 ` Filippo Argiolas
2008-02-22 10:56 ` Matthew Vermeulen
2008-02-22 11:07 ` Nicolas Will
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=1203459408.28796.19.camel@youkaida \
--to=nico@youplala.net \
--cc=jonas@anden.nu \
--cc=linux-dvb@linuxtv.org \
/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