Am Montag, den 13.07.2009, 16:36 +0200 schrieb Samuel Rakitnican: > Hi Hermann, > > On Sun, 12 Jul 2009 23:33:06 +0200, hermann pitton > <hermann-pitton@xxxxxxxx> wrote: > > [snip] > > Hm, if I get it right, without using windows previously the XCeive at > > 0x61 is not found and then it is tried in vain to use the qt1010 at > > 0x62. > > > > Also, after using windows gpio20 seems to be high. > > Maybe that is the gpio to get the tuner out of reset. > > > > Please try the attached patch as a shot into the dark. > > > [snip] > > No, I pay attention when I test for channel that XCeive gets recognized > as 0x61. When I do cold boot, or windows reboot its always gets > recognized at 0x61. Sometimes (I don't know exactly what triggers that) > the 0x61 gets omitted, and the result is that XCeive get recognized as > 0x62. The result is that channel is not showing any more, apparently. > > I think that xc2028-27.fw file load failures triggers that behavior, > because when I reboot linux with loading firmware failures, that > behavior is showing (from what I have noticed). > > Sorry for the gpio alert, but I did some logging, and the gpio value > varies, and depends on computer state. But it seems that is same in both > cases after all. (details http://pastebin.com/f4c511dfc) > > I tried your patch, too, and it's not working. Thank you for trying. Hi Samuel, thanks for that clarification. I don't know, if Markus has something better in his binary blob meanwhile, he was initially interested at least, but how to comment on stuff not shown anymore ... At least, the remote will be operable for cheap. Does anybody know, why Compro doesn't clear the eeprom byte for the analog demodulator since years (0x86)? F* it. Cheers, Hermann -- 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
