From: "David Härdeman" <david@hardeman.nu>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Sean Young <sean@mess.org>, Jarod Wilson <jwilson@redhat.com>,
linux-media@vger.kernel.org
Subject: Re: [media] rc-core: move timeout and checks to lirc
Date: Tue, 21 Aug 2012 21:44:09 +0200 [thread overview]
Message-ID: <20120821194409.GB4993@hardeman.nu> (raw)
In-Reply-To: <CAGoCfizxSnUgC2Ka5uz3_gXaFf65057kt+EBNz7WassEvVsDHg@mail.gmail.com>
On Mon, Aug 20, 2012 at 06:10:16PM -0400, Devin Heitmueller wrote:
>On Mon, Aug 20, 2012 at 6:02 PM, Mauro Carvalho Chehab
><mchehab@redhat.com> wrote:
>> So, IMO, it makes sense to have a "high end" API that accepts
>> writing keystrokes like above, working with both "raw drivers"
>> using some kernel IR protocol encoders, and with devices that can
>> accept "processed" keystrokes, like HDMI CEC.
>
>It might also make sense to have a third mode for devices that support
>high level protocols such as RC5/NEC but you want to leverage the very
>large existing LIRC database of remote controls. The device would
>advertise all the modes it supports (RC5/NEC/RC6/whatever), and from
>there it can accept the actual RC codes instead of a raw waveform.
That should be pretty trivial with the API I suggested - i.e. that
userspace is expected to do an ioctl first to get the bitmask of
supported modes. This would just be another TX mode.
--
David Härdeman
next prev parent reply other threads:[~2012-08-21 19:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 22:15 [media] rc-core: move timeout and checks to lirc Sean Young
2012-08-16 23:12 ` Mauro Carvalho Chehab
2012-08-20 21:36 ` David Härdeman
2012-08-20 22:02 ` Mauro Carvalho Chehab
2012-08-20 22:10 ` Devin Heitmueller
2012-08-21 19:44 ` David Härdeman [this message]
2012-08-21 12:55 ` Sean Young
2012-08-21 19:55 ` David Härdeman
2012-08-21 19:42 ` David Härdeman
2012-08-24 22:16 ` David Härdeman
2012-08-24 23:19 ` Sean Young
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=20120821194409.GB4993@hardeman.nu \
--to=david@hardeman.nu \
--cc=dheitmueller@kernellabs.com \
--cc=jwilson@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=sean@mess.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.