public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarod Wilson <jarod@wilsonet.com>
To: Andy Walls <awalls@radix.net>
Cc: Jarod Wilson <jarod@redhat.com>, Janne Grunau <j@jannau.net>,
	linux-media@vger.kernel.org,
	Brandon Jenkins <bcjenkins@tvwhere.com>
Subject: Re: [PATCH] hdpvr: i2c fixups for fully functional IR support
Date: Tue, 01 Sep 2009 23:26:54 -0400	[thread overview]
Message-ID: <4A9DE5FE.8060409@wilsonet.com> (raw)
In-Reply-To: <1251855051.3926.34.camel@palomino.walls.org>

On 09/01/2009 09:30 PM, Andy Walls wrote:
> On Tue, 2009-09-01 at 10:19 -0400, Jarod Wilson wrote:
>> Patch is against http://hg.jannau.net/hdpvr/
>>
>> 1) Adds support for building hdpvr i2c support when i2c is built as a
>> module (based on work by David Engel on the mythtv-users list)
>>
>> 2) Refines the hdpvr_i2c_write() success check (based on a thread in
>> the sagetv forums)
>>
>> With this patch in place, and the latest lirc_zilog driver in my lirc
>> git tree, the IR part in my hdpvr works perfectly, both for reception
>> and transmitting.
>>
>> Signed-off-by: Jarod Wilson<jarod@redhat.com>
>
> Jarod,
>
> I recall a problem Brandon Jenkins had from last year, that when I2C was
> enabled in hdpvr, his machine with multiple HVR-1600s and an HD-PVR
> would produce a kernel oops.
>
> Have you tested this on a machine with both an HVR-1600 and HD-PVR
> installed?

Hrm, no, haven't tested it with such a setup, don't have an HVR-1600. I 
do have an HVR-1250 that I think might suffice for testing though, if 
I'm thinking clearly.

Ugh. And I just noticed that while everything works swimmingly with a 
2.6.30 kernel base, the i2c changes in 2.6.31 actually break it, so 
there's gonna be at least one more patch coming... I'm an idjit for not 
testing w/2.6.31 before sending this in, I *knew* there were major i2c 
changes to account for... (Its actually the hdpvr driver oopsing, before 
one even tries loading lirc_zilog).

-- 
Jarod Wilson
jarod@wilsonet.com

  reply	other threads:[~2009-09-02  3:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-01 14:19 [PATCH] hdpvr: i2c fixups for fully functional IR support Jarod Wilson
2009-09-02  1:30 ` Andy Walls
2009-09-02  3:26   ` Jarod Wilson [this message]
2009-09-03  3:33     ` Jarod Wilson
2009-09-03 11:50       ` Andy Walls
2009-09-03 20:02         ` Jarod Wilson
2009-09-03 21:32           ` Janne Grunau
2009-09-04  5:05             ` Jarod Wilson
2009-09-13 17:23   ` Brandon Jenkins
2009-09-13 21:04     ` Jarod Wilson
2009-09-13 22:13       ` Janne Grunau
2009-09-14  1:06         ` Jarod Wilson
2009-09-14 13:32           ` Brandon Jenkins
2009-09-14 14:34             ` 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=4A9DE5FE.8060409@wilsonet.com \
    --to=jarod@wilsonet.com \
    --cc=awalls@radix.net \
    --cc=bcjenkins@tvwhere.com \
    --cc=j@jannau.net \
    --cc=jarod@redhat.com \
    --cc=linux-media@vger.kernel.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