From: Andy Walls <awalls@md.metrocast.net>
To: Jarod Wilson <jarod@wilsonet.com>
Cc: Jason Gauthier <jgauthier@lastar.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Janne Grunau <j@jannau.net>
Subject: Re: Enable IR on hdpvr
Date: Mon, 10 Jan 2011 07:07:52 -0500 [thread overview]
Message-ID: <1294661272.2084.10.camel@morgan.silverblock.net> (raw)
In-Reply-To: <8AFBEFD7-69E3-4E71-B155-EA773C2FED43@wilsonet.com>
On Mon, 2011-01-10 at 01:05 -0500, Jarod Wilson wrote:
> On Jan 9, 2011, at 7:36 PM, Jason Gauthier wrote:
> Janne, I've heard many success stories w/the hdpvr IR lately, and almost no reports
> of lockups, so I'm thinking a firmware update may have helped out here, and thus,
> maybe its time we just go ahead and push this patch along upstream? We still
> require someone to load lirc_zilog manually, so it seems like a fairly low-risk
> thing to do.
FYI, the code I added to hdpvr-i2c.c will perform 2 accesses to the chip
to check for existence, by virtue of a call to i2c_new_probed_device()
(or whatever it is called). The I2C subsystem tries to talk the chip to
see if it exists.
If you are really concerned about corner cases that may hang, add a
module option to hdpvr to disable I2C and/or IR in the hdpvr driver.
With that users in the field can work-around the problem without
rebuilding modules.
Regards,
Andy
next prev parent reply other threads:[~2011-01-10 12:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 0:36 Enable IR on hdpvr Jason Gauthier
[not found] ` <8AFBEFD7-69E3-4E71-B155-EA773C2FED43@wilsonet.com>
2011-01-10 12:07 ` Andy Walls [this message]
2011-01-10 12:12 ` Maybe I'll hack on lirc_zilog.c this coming weekend (Re: Enable IR on hdpvr) Andy Walls
2011-01-10 19:51 ` Jarod Wilson
2011-01-10 12:24 ` Enable IR on hdpvr Janne Grunau
2011-01-10 14:25 ` Jason Gauthier
2011-01-10 19:50 ` Jarod Wilson
2011-01-12 4:40 ` Jarod Wilson
2011-01-12 13:49 ` Jason Gauthier
2011-01-12 23:45 ` Andy Walls
2011-01-13 2:16 ` Jason Gauthier
2011-01-13 5:31 ` Andy Walls
2011-05-21 18:19 ` Jason Gauthier
2011-05-21 18:46 ` Jason Gauthier
2011-05-22 2:02 ` [SOLVED] " Jason Gauthier
2011-05-22 2:13 ` [SOLVED (not really)] " Jason Gauthier
2011-05-22 3:02 ` [SOLVED] " Andy Walls
2011-05-22 3:17 ` Jason Gauthier
2011-01-13 5:23 ` Andy Walls
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=1294661272.2084.10.camel@morgan.silverblock.net \
--to=awalls@md.metrocast.net \
--cc=j@jannau.net \
--cc=jarod@wilsonet.com \
--cc=jgauthier@lastar.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