From: Mark Zimmerman <markzimm@frii.com>
To: linux-media@vger.kernel.org
Cc: Jarod Wilson <jarod@redhat.com>
Subject: [get-bisect results]: DViCO FusionHDTV7 Dual Express I2C write failed
Date: Sat, 12 Feb 2011 08:29:54 -0700 [thread overview]
Message-ID: <20110212152954.GA20838@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...
>
I did a git bisect on this and finally reached the end of the line.
Here is what it said:
qpc$ git bisect bad
82ce67bf262b3f47ecb5a0ca31cace8ac72b7c98 is the first bad commit
commit 82ce67bf262b3f47ecb5a0ca31cace8ac72b7c98
Author: Jarod Wilson <jarod@redhat.com>
Date: Thu Jul 29 18:20:44 2010 -0300
V4L/DVB: staging/lirc: fix non-CONFIG_MODULES build horkage
Fix when CONFIG_MODULES is not enabled:
drivers/staging/lirc/lirc_parallel.c:243: error: implicit declaration of function 'module_refcount'
drivers/staging/lirc/lirc_it87.c:150: error: implicit declaration of function 'module_refcount'
drivers/built-in.o: In function `it87_probe':
lirc_it87.c:(.text+0x4079b0): undefined reference to `init_chrdev'
lirc_it87.c:(.text+0x4079cc): undefined reference to `drop_chrdev'
drivers/built-in.o: In function `lirc_it87_exit':
lirc_it87.c:(.exit.text+0x38a5): undefined reference to `drop_chrdev'
Its a quick hack and untested beyond building, since I don't have the
hardware, but it should do the trick.
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
:040000 040000 f645b46a07b7ff87a2c11ac9296a5ff56e89a0d0 49e50945ccf8e1c8567c049908890d2752443b72 M drivers
next prev parent reply other threads:[~2011-02-12 15:29 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 ` DViCO FusionHDTV7 Dual Express I2C write failed Mark Zimmerman
2011-01-19 15:59 ` 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 ` Mark Zimmerman [this message]
2011-02-12 16:27 ` [get-bisect results]: " 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=20110212152954.GA20838@io.frii.com \
--to=markzimm@frii.com \
--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