On Fri, Mar 11, 2011 at 6:04 PM, <jean.bruenn@xxxxxxxxxxx> wrote: > > Hey, > > i tried to revert that patch manually (e.g. switching into the directory, > vim cx23885-i2c.c, removing the stuff which was added), then "make clean" > "make distclean" followed by "./build.sh" then make rmmod, then plugged in > the card, dmesg shows it loaded the card correctly, all fine, then i did > ./scan Scanlist.txt and i get the same i2c related errors. Did a reboot > just to verify, still getting those, scan gives no results always "tuning > failed". > > Then i reverted another patch (just to make sure.. > http://git.kernel.org/?p=linux/kernel/git/mchehab/linux-2.6.git;a=commit;h=f4acb3c4ccca74f5448354308f917e87ce83505a) > - However, this didn't help. So, the problem might be somewhere else. > > I did some more research and it seems i'm not the only one with those > issues, tho nearly none gets answers regarding this trouble, e.g.: > > (same card - also expresscard, december 2010) > http://www.spinics.net/lists/linux-media/msg27042.html > (not the same card, tho similar error, hvr 1500, i got hvr 1400 - februar > 2009) > http://www.linuxtv.org/pipermail/linux-dvb/2009-February/031839.html > > I'm running out of ideas where the problem might be located. i also tried > to switch the firmware by extracting the firmware manually, didn't help. > There's a low power version and another one available, tried to replace, > didn't work neither. > > So it seems, this driver is broken at least since december 2010. Totally > weird why there's such a mess, i know for sure that this WAS working. Doesn't seem weird to me at all. This is a pretty uncommon card, so it is entirely possible that many revisions could go by without someone noticing a regression. I know for example that the HVR-1500Q (the US version of that board) was broken for months and nobody noticed. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
