From: "Jon Smirl" <jonsmirl@gmail.com>
To: linux-kernel@vger.kernel.org, lirc-list@lists.sourceforge.net
Subject: Re: [RFC PATCH 0/4] V3 - Implementation of IR support using the input subsystem
Date: Mon, 6 Oct 2008 15:46:11 -0400 [thread overview]
Message-ID: <9e4733910810061246t3d0f4671se3cef6813a96e84e@mail.gmail.com> (raw)
In-Reply-To: <20081006194032.15992.8393.stgit@terra>
On Mon, Oct 6, 2008 at 3:43 PM, Jon Smirl <jonsmirl@gmail.com> wrote:
> Third pass at implementing evdev support for IR. The goal of in-kernel IR is to integrate IR events into the evdev input event queue and maintain ordering of events from all input devices.
Mail to LIRC list still bounces because it is slightly too big - over
the 20K limit.
Messages are here:
http://lkml.org/lkml/2008/10/6/202
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-10-06 19:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 19:43 Jon Smirl
2008-10-06 19:43 ` [RFC PATCH 1/4] Changes to core input subsystem to allow send and receive of IR messages. Encode and decode state machines are provided for common IR porotocols such as Sony, JVC, NEC, Philips, etc Jon Smirl
2009-05-28 23:23 ` Maxim Levitsky
2009-05-29 1:15 ` Jon Smirl
2008-10-06 19:43 ` [RFC PATCH 2/4] GPT driver for in-kernel IR support Jon Smirl
2008-10-06 19:43 ` [RFC PATCH 3/4] Example of PowerPC device tree support for GPT based IR Jon Smirl
2008-10-06 19:43 ` [RFC PATCH 4/4] Microsoft mceusb2 driver for in-kernel IR subsystem Jon Smirl
2008-10-06 19:46 ` Jon Smirl [this message]
2008-10-09 12:03 ` [RFC PATCH 0/4] V3 - Implementation of IR support using the input subsystem Pavel Machek
2008-10-10 4:11 ` Jarod Wilson
2008-10-10 5:04 ` Jon Smirl
2008-10-10 13:42 ` Jarod Wilson
2008-10-10 14:08 ` Jon Smirl
2008-10-10 21:10 ` Jarod Wilson
2009-05-28 15:06 ` Maxim Levitsky
2009-05-28 15:58 ` Maxim Levitsky
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=9e4733910810061246t3d0f4671se3cef6813a96e84e@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lirc-list@lists.sourceforge.net \
/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®