All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Zimmerman <markzimm@frii.com>
To: linux-media@vger.kernel.org
Subject: Re: DViCO FusionHDTV7 Dual Express I2C write failed
Date: Sun, 9 Jan 2011 19:14:39 -0700	[thread overview]
Message-ID: <20110110021439.GA70495@io.frii.com> (raw)
In-Reply-To: <20101207190753.GA21666@io.frii.com>

On Tue, Dec 07, 2010 at 12:07:53PM -0700, Mark Zimmerman wrote:
> Greetings:
> 
> I have a DViCO FusionHDTV7 Dual Express card that works with 2.6.35 but
> which fails to initialize with the latest 2.6.36 kernel. The firmware
> fails to load due to an i2c failure. A search of the archives indicates
> that this is not the first time this issue has occurred.
> 
> What can I do to help get this problem fixed?
> 
> Here is the dmesg from 2.6.35, for the two tuners: 
> 
> xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)... 
> xc5000: firmware read 12401 bytes. 
> xc5000: firmware uploading... 
> xc5000: firmware upload complete... 
> xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)... 
> xc5000: firmware read 12401 bytes. 
> xc5000: firmware uploading... 
> xc5000: firmware upload complete..
> 
> and here is what happens with 2.6.36: 
> 
> xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)... 
> xc5000: firmware read 12401 bytes. 
> xc5000: firmware uploading... 
> xc5000: I2C write failed (len=3) 
> xc5000: firmware upload complete... 
> xc5000: Unable to initialise tuner 
> xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)... 
> xc5000: firmware read 12401 bytes. 
> xc5000: firmware uploading... 
> xc5000: I2C write failed (len=3) 
> xc5000: firmware upload complete...
> 

More information about this: I tried 2.6.37 (vanilla source from
kernel.org) and the problem persisted. So, I enabled these options:
CONFIG_I2C_DEBUG_CORE=y                                                         
CONFIG_I2C_DEBUG_ALGO=y
CONFIG_I2C_DEBUG_BUS=y
hoping to get more information but this time the firmware loaded
successfully and the tuner works properly.

This leads me to suspect a race condition somewhere, or maybe a
tunable parameter that can be adjusted. The fact that the 'write
failed' message occurs before the 'upload complete' message would tend
to support this. Can anyone suggest something I might try?

-- Mark

       reply	other threads:[~2011-01-10  2:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101207190753.GA21666@io.frii.com>
2011-01-10  2:14 ` Mark Zimmerman [this message]
2011-01-19 15:59   ` DViCO FusionHDTV7 Dual Express I2C write failed VDR User
2011-01-19 16:13     ` Devin Heitmueller
2011-01-19 17:22       ` VDR User
2011-01-19 17:39         ` Mark Zimmerman
2011-01-24 15:49           ` Mark Zimmerman
2011-01-24 15:57             ` Devin Heitmueller
2011-01-25 14:27               ` Mark Zimmerman
2011-01-19 19:01       ` Timothy D. Lenz
2011-01-17 23:12 ` Timothy D. Lenz
2011-02-12 15:29 ` [get-bisect results]: " Mark Zimmerman
2011-02-12 16:27   ` Andy Walls
2011-02-12 16:36     ` Mark Zimmerman
2011-02-12 16:46       ` Andy Walls
2011-02-12 17:03         ` Mark Zimmerman
2011-02-12 19:05         ` Mark Zimmerman
2011-02-12 20:48           ` Andy Walls
2011-02-13 14:47   ` [corrected get-bisect " Mark Zimmerman
2011-02-13 14:52     ` Devin Heitmueller
2011-02-13 20:26       ` Mark Zimmerman
2011-02-13 21:26         ` Andy Walls
2011-02-14  0:16           ` Andy Walls
2011-02-14 14:29             ` Devin Heitmueller
2011-02-14  0:37           ` Mark Zimmerman
2011-02-14  8:05     ` Jean Delvare

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=20110110021439.GA70495@io.frii.com \
    --to=markzimm@frii.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.