From: Janne Grunau <j@jannau.net>
To: Jarod Wilson <jarod@wilsonet.com>
Cc: Andy Walls <awalls@radix.net>, Jarod Wilson <jarod@redhat.com>,
linux-media@vger.kernel.org,
Brandon Jenkins <bcjenkins@tvwhere.com>
Subject: Re: [PATCH] hdpvr: i2c fixups for fully functional IR support
Date: Thu, 3 Sep 2009 23:32:26 +0200 [thread overview]
Message-ID: <20090903213226.GF7962@aniel.lan> (raw)
In-Reply-To: <30AAA297-A772-40B1-8C03-441CC6D3C5BC@wilsonet.com>
On Thu, Sep 03, 2009 at 04:02:12PM -0400, Jarod Wilson wrote:
> On Sep 3, 2009, at 7:50 AM, Andy Walls wrote:
>
> >> Hrm. A brief google search suggests the 1250 IR part isn't enabled. I
> >> see a number of i2c devices in i2cdetect -l output, but none that say
> >> anything about IR... I could just plug the hdpvr in there and see
> >> what
> >> happens, I suppose...
> >
> > You should try that. It was an issue of legacy I2C driver probing
> > that
> > caused the hdpvr module to have problems. The cx18 driver simply
> > stimulated the i2c subsystem to do legacy probing (via the tuner
> > modules
> > IIRC)? See the email I sent you.
>
> So from what I can tell, the i2c changes in 2.6.31 *should* prevent
> that from happening, and now that I've got everything working on
> 2.6.31 too, I'll try hooking up my hdpvr to my box w/an hvr-1250,
> hvr-1800 and pchdtv hd-3000 in it and see what blows up (hopefully
> nothing...).
We still need something to prevent it from happening with older kernels.
Easiest solution would be to disable it for 2.6.30 and earlier.
Janne
next prev parent reply other threads:[~2009-09-03 21:31 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
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 [this message]
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=20090903213226.GF7962@aniel.lan \
--to=j@jannau.net \
--cc=awalls@radix.net \
--cc=bcjenkins@tvwhere.com \
--cc=jarod@redhat.com \
--cc=jarod@wilsonet.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