From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx2.redhat.com ([66.187.237.31]:47521 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755289AbZGIPqi (ORCPT ); Thu, 9 Jul 2009 11:46:38 -0400 From: Jarod Wilson To: Jean Delvare Subject: Re: [RFC] Anticipating lirc breakage Date: Thu, 9 Jul 2009 11:44:46 -0400 Cc: Mauro Carvalho Chehab , Mike Isely , isely@isely.net, LMML , Andy Walls , Hans Verkuil , Janne Grunau References: <20090406174448.118f574e@hyperion.delvare> <20090407075029.21d14f4a@pedra.chehab.org> <20090407143617.2c2adbf7@hyperion.delvare> In-Reply-To: <20090407143617.2c2adbf7@hyperion.delvare> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907091144.48125.jarod@redhat.com> Sender: linux-media-owner@vger.kernel.org List-ID: 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