From: Jarod Wilson <jarod@redhat.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Mike Isely <isely@pobox.com>,
isely@isely.net, LMML <linux-media@vger.kernel.org>,
Andy Walls <awalls@radix.net>, Hans Verkuil <hverkuil@xs4all.nl>,
Janne Grunau <j@jannau.net>
Subject: Re: [RFC] Anticipating lirc breakage
Date: Thu, 9 Jul 2009 11:44:46 -0400 [thread overview]
Message-ID: <200907091144.48125.jarod@redhat.com> (raw)
In-Reply-To: <20090407143617.2c2adbf7@hyperion.delvare>
On Tuesday 07 April 2009 08:36:17 Jean Delvare wrote:
> > So, let's just forget the workarounds and go straight to the point: focus on
> > merging lirc-i2c drivers.
>
> Will this happen next week? I fear not. Which is why I can't wait for
> it. And anyway, in order to merge the lirc_i2c driver, it must be
> turned into a new-style I2C driver first, so bridge drivers must be
> prepared for this, which is exactly what my patches are doing.
For what its worth, I fixed up lirc_i2c a few days ago, and now have
it working just fine with my pvr-250 under 2.6.31-rc2.
Real Soon Now (I swear), I'm hoping to get up another head of steam
for submitting lirc upstream. Multiple drivers have received a bunch
of love in the past few weeks, so I think we're in a pretty good state
to have another go at it...
--
Jarod Wilson
jarod@redhat.com
next prev parent reply other threads:[~2009-07-09 15:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 15:44 [RFC] Anticipating lirc breakage Jean Delvare
2009-04-07 1:20 ` Andy Walls
2009-04-07 3:15 ` hermann pitton
2009-04-07 9:08 ` Jean Delvare
2009-04-07 2:30 ` Mauro Carvalho Chehab
2009-04-07 6:19 ` Mike Isely
2009-04-07 10:02 ` Jean Delvare
2009-04-07 10:50 ` Mauro Carvalho Chehab
2009-04-07 12:36 ` Jean Delvare
2009-07-09 15:44 ` Jarod Wilson [this message]
2009-07-09 15:52 ` Devin Heitmueller
2009-07-09 16:08 ` Jean Delvare
2009-04-08 17:22 ` Mike Isely
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=200907091144.48125.jarod@redhat.com \
--to=jarod@redhat.com \
--cc=awalls@radix.net \
--cc=hverkuil@xs4all.nl \
--cc=isely@isely.net \
--cc=isely@pobox.com \
--cc=j@jannau.net \
--cc=khali@linux-fr.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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