From: Andy Walls <awalls@md.metrocast.net>
To: Jarod Wilson <jarod@wilsonet.com>
Cc: "David Härdeman" <david@hardeman.nu>,
"Jarod Wilson" <jarod@redhat.com>,
"Mauro Carvalho Chehab" <mchehab@redhat.com>,
linux-media@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 3/4] ir-core: move decoding state to ir_raw_event_ctrl
Date: Thu, 17 Jun 2010 08:14:19 -0400 [thread overview]
Message-ID: <1276776859.2461.16.camel@localhost> (raw)
In-Reply-To: <AANLkTil6P0rnmViLwpkiBOYoC6qF217V90g7Nslk3DHN@mail.gmail.com>
On Wed, 2010-06-16 at 16:41 -0400, Jarod Wilson wrote:
> On Wed, Jun 16, 2010 at 4:04 PM, Jarod Wilson <jarod@wilsonet.com> wrote:
> ...
> >> I have another suggestion, let's keep the client register/unregister
> >> callbacks for decoders (but add a comment that they're only used for
> >> lirc). Then teach drivers/media/IR/ir-raw-event.c to keep track of the
> >> raw clients so that it can pass all pre-existing clients to newly added
> >> decoders.
> >>
> >> I'll post two patches (compile tested only) in a few seconds to show
> >> what I mean.
> >
> > Consider them now runtime tested as well. They appear to do the trick,
> > the lirc bridge comes up just fine, even when ir-lirc-codec isn't
> > loaded until after mceusb. *Much* better implementation than my ugly
> > trick. I'll ack your patches and submit a series on top of them for
> > lirc support, hopefully this evening (in addition to a few other fixes
> > that aren't dependent on any of them).
>
> A fully functional tree carrying both of David's patches and the
> entire stack of other patches I've submitted today, based on top of
> the linuxtv staging/rc branch, can be found here:
>
> http://git.wilsonet.com/linux-2.6-ir-wip.git/?a=shortlog;h=refs/heads/patches
>
> Also includes the lirc patches that I believe are ready to be
> submitted for actual consideration (note that they're dependent on
> David's two patches).
I'll try and play with this this weekend along with some cx23885
cleanup.
Regards,
Andy
next prev parent reply other threads:[~2010-06-17 12:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 21:13 [PATCH 0/4] ir-core sysfs protocol selection simplification David Härdeman
2010-04-24 21:14 ` [PATCH 1/4] ir-core: remove IR_TYPE_PD David Härdeman
2010-04-24 21:14 ` [PATCH 2/4] ir-core: centralize sysfs raw decoder enabling/disabling David Härdeman
2010-05-03 19:49 ` Mauro Carvalho Chehab
2010-06-07 18:48 ` David Härdeman
2010-04-24 21:14 ` [PATCH 3/4] ir-core: move decoding state to ir_raw_event_ctrl David Härdeman
2010-05-03 20:00 ` Mauro Carvalho Chehab
2010-06-07 19:00 ` David Härdeman
2010-06-07 20:15 ` Jarod Wilson
2010-06-08 17:50 ` David Härdeman
2010-06-09 3:46 ` Jarod Wilson
2010-06-09 13:29 ` Jarod Wilson
2010-06-09 17:56 ` David Härdeman
2010-06-09 18:15 ` Jarod Wilson
2010-06-10 1:25 ` Jarod Wilson
2010-06-13 20:29 ` David Härdeman
2010-06-16 20:04 ` Jarod Wilson
2010-06-16 20:41 ` Jarod Wilson
2010-06-17 12:14 ` Andy Walls [this message]
2010-06-17 15:11 ` Jarod Wilson
2010-06-21 0:47 ` Andy Walls
2010-06-21 3:51 ` Jarod Wilson
2010-06-21 11:04 ` Andy Walls
2010-07-06 17:12 ` Jarod Wilson
2010-04-24 21:14 ` [PATCH 4/4] ir-core: remove ir-functions usage from cx231xx David Härdeman
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=1276776859.2461.16.camel@localhost \
--to=awalls@md.metrocast.net \
--cc=david@hardeman.nu \
--cc=jarod@redhat.com \
--cc=jarod@wilsonet.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).