On Thu, 9 Jul 2009 11:44:46 -0400, Jarod Wilson wrote:
> 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 ca
On Thu, Jul 9, 2009 at 11:44 AM, Jarod Wilson wrote:
> 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
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
On Tue, 7 Apr 2009, Jean Delvare wrote:
> I'll rework my patch set to implement strategy #1 and post it when I'm
> done. As far as I can see this should be very similar to my original
> attempt, with just "ir_video" devices instead or "ir-kbd" devices, and
> also fixes for the minor issues that ha
Hi Mauro,
On Tue, 7 Apr 2009 07:50:29 -0300, Mauro Carvalho Chehab wrote:
> On Tue, 7 Apr 2009 12:02:09 +0200
> Jean Delvare wrote:
>
> > Hi Mike,
> >
> > Glad to see we all mostly agree on what to do now. I'll still answer
> > some of your questions below, to clarify things even more.
>
> I d
On Tue, 7 Apr 2009 12:02:09 +0200
Jean Delvare wrote:
> Hi Mike,
>
> Glad to see we all mostly agree on what to do now. I'll still answer
> some of your questions below, to clarify things even more.
I don't understand why you are preferring to do some workaround, spending
energy to add hooks at
Hi Mike,
Glad to see we all mostly agree on what to do now. I'll still answer
some of your questions below, to clarify things even more.
On Tue, 7 Apr 2009 01:19:02 -0500 (CDT), Mike Isely wrote:
> On Mon, 6 Apr 2009, Jean Delvare wrote:
> > The bottom line is that we have to instantiate I2C devi
Hi Andy,
On Mon, 06 Apr 2009 21:20:37 -0400, Andy Walls wrote:
> On Mon, 2009-04-06 at 17:44 +0200, Jean Delvare wrote:
> > The bottom line is that we have to instantiate I2C devices for IR
> > components regardless of the driver which will handle them (ir-kbd-i2c,
> > lirc_i2c or another one). I
On Mon, 6 Apr 2009, Jean Delvare wrote:
> Hi all,
>
> In the light of recent discussions and planed changes to the i2c
> subsystem and the ir-kbd-i2c driver, I will try to summarize the
> situation and make some proposals. Note that I am really not sure what
> we want to do, so this is a true req
Hi,
Am Montag, den 06.04.2009, 21:20 -0400 schrieb Andy Walls:
> On Mon, 2009-04-06 at 17:44 +0200, Jean Delvare wrote:
> > Hi all,
> >
> > In the light of recent discussions and planed changes to the i2c
> > subsystem and the ir-kbd-i2c driver, I will try to summarize the
> > situation and make
On Mon, 6 Apr 2009 17:44:48 +0200
Jean Delvare wrote:
> Hi all,
>
> In the light of recent discussions and planed changes to the i2c
> subsystem and the ir-kbd-i2c driver, I will try to summarize the
> situation and make some proposals. Note that I am really not sure what
> we want to do, so thi
On Mon, 2009-04-06 at 17:44 +0200, Jean Delvare wrote:
> Hi all,
>
> In the light of recent discussions and planed changes to the i2c
> subsystem and the ir-kbd-i2c driver, I will try to summarize the
> situation and make some proposals. Note that I am really not sure what
> we want to do, so this
Hi all,
In the light of recent discussions and planed changes to the i2c
subsystem and the ir-kbd-i2c driver, I will try to summarize the
situation and make some proposals. Note that I am really not sure what
we want to do, so this is a true request for opinions.
First of all, the original reason
13 matches
Mail list logo
