From: "David Härdeman" <david@hardeman.nu>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
linux-input@vger.kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Jarod Wilson <jarod@wilsonet.com>
Subject: Re: [PATCH 00/15] ir-core: Several improvements to allow adding LIRC and decoder plugins
Date: Fri, 2 Apr 2010 12:20:11 +0200 [thread overview]
Message-ID: <20100402102011.GA6947@hardeman.nu> (raw)
In-Reply-To: <t2z9e4733911004011844pd155bbe8g13e4cbcc1a5bf1f6@mail.gmail.com>
On Thu, Apr 01, 2010 at 09:44:12PM -0400, Jon Smirl wrote:
> On Thu, Apr 1, 2010 at 1:56 PM, Mauro Carvalho Chehab
> <mchehab@redhat.com> wrote:
> > This series of 15 patches improves support for IR, as discussed at the
> > "What are the goals for the architecture of an in-kernel IR system?"
> > thread.
> >
> > It basically adds a raw decoder layer at ir-core, allowing decoders to plug
> > into IR core, and preparing for the addition of a lirc_dev driver that will
> > allow raw IR codes to be sent to userspace.
> >
> > There's no lirc patch in this series. I have also a few other patches from
> > David Härdeman that I'm about to test/review probably later today, but
> > as I prefer to first merge what I have at V4L/DVB tree, before applying
> > them.
>
> Has anyone ported the MSMCE driver onto these patches yet? That would
> be a good check to make sure that rc-core has the necessary API.
I still plan to make lots of changes to the rc-core API (I just have to
convince Mauro first, but I'll get there). What I have done is to port
your port of the msmce driver to the suggested rc-core subsystem I sent
you in private a week or so ago, and it works fine (I've bought the
hardware and tested it with 20 or so different protocols).
The subsystem I suggested is basically what I'm using as inspiration
while working with Mauro in improving rc-core so msmce should work well
with the end product...but there's still some ground to cover.
Porting the msmce driver to rc-core will be high on my list of
priorities once I've done some more changes to the API.
> Cooler if it works both through LIRC and with an internal protocol
> decoder. The MSMCE driver in my old patches was very simplified, it
> removed about half of the code from the LIRC version.
Yes, and it was a great help to me at least...thanks :)
--
David Härdeman
next prev parent reply other threads:[~2010-04-02 10:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 17:56 [PATCH 00/15] ir-core: Several improvements to allow adding LIRC and decoder plugins Mauro Carvalho Chehab
2010-04-02 1:44 ` Jon Smirl
2010-04-02 10:20 ` David Härdeman [this message]
2010-04-05 20:49 ` Jarod Wilson
2010-04-07 9:32 ` David Härdeman
2010-04-23 17:40 ` Jarod Wilson
2010-04-23 18:06 ` Jon Smirl
2010-04-23 18:29 ` Mauro Carvalho Chehab
2010-04-23 22:20 ` Andy Walls
2010-04-24 5:22 ` David Härdeman
2010-04-24 12:35 ` Jon Smirl
2010-04-24 14:15 ` David Härdeman
2010-04-24 15:07 ` Jon Smirl
2010-04-24 21:23 ` David Härdeman
2010-04-24 21:59 ` Jon Smirl
2010-04-24 5:12 ` David Härdeman
2010-04-28 4:32 ` Jarod Wilson
2010-05-25 21:05 ` Jarod Wilson
2010-05-26 18:28 ` Jarod Wilson
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=20100402102011.GA6947@hardeman.nu \
--to=david@hardeman.nu \
--cc=jarod@wilsonet.com \
--cc=jonsmirl@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).