From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: darius@dons.net.au
Cc: linux-media@vger.kernel.org
Subject: Re: DViCo Dual Fusion Express (cx23885) remote control issue
Date: Fri, 23 Apr 2010 00:52:11 -0700 [thread overview]
Message-ID: <4BD151AB.7070701@vorgon.com> (raw)
In-Reply-To: <201004231000.07508.darius@dons.net.au>
On 4/22/2010 5:29 PM, Daniel O'Connor wrote:
> On Fri, 23 Apr 2010, Timothy D. Lenz wrote:
>> On 4/22/2010 6:11 AM, Daniel O'Connor wrote:
>>> On Thu, 15 Apr 2010, Daniel O'Connor wrote:
>>>> I haven't delved much further yet (planning to printf my way
>>>> through the probe routines) as I am a Linux kernel noob (plenty of
>>>> FreeBSD experience though!).
>>>
>>> I found that it is intermittent with no pattern I can determine.
>>>
>>> When it doesn't work the probe routine is not called, but I am not
>>> sure how i2c_register_driver decides to call the probe routine.
>>>
>>> Does anyone have an idea what the cause could be? Or at least
>>> somewhere to start looking :)
>>
>> A patch was posted that was suposed to be merged that fixed the ir
>> problem, at least for me. Though my problem was not intermittent. The
>> patch worked for me. Now if I could just get both tuners to keep
>> working
>
> Hmm do you have a subject line or message ID I can search for?
>
> I haven't found any problems with tuners not working although I don't
> often fire them both up at once.
>
[PATCH] FusionHDTV: Use quick reads for I2C IR device probing
next prev parent reply other threads:[~2010-04-23 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 5:49 DViCo Dual Fusion Express (cx23885) remote control issue Daniel O'Connor
2010-04-22 13:11 ` Daniel O'Connor
2010-04-22 18:41 ` Timothy D. Lenz
2010-04-23 0:29 ` Daniel O'Connor
2010-04-23 7:52 ` Timothy D. Lenz [this message]
2010-05-22 3:47 ` Daniel O'Connor
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=4BD151AB.7070701@vorgon.com \
--to=tlenz@vorgon.com \
--cc=darius@dons.net.au \
--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