On Sat, Mar 12, 2011 at 9:22 PM, Jean-Michel Bruenn <jean.bruenn@xxxxxxxxxxx> wrote: > So i guess, nobody here can help me to solve that problems? > > xc2028 1-0064: i2c output error: rc = -6 (should be 64) > xc2028 1-0064: -6 returned from send > xc2028 1-0064: Error -22 while loading base firmware > xc2028 1-0064: Loading firmware for type=BASE F8MHZ (3), id > 0000000000000000. > > and nobody can tell me, whether thats a firmware problem, or is it an > i2c problem? At least someone who could explain me, what the above > errors mean? It means the i2c bus failed to get an ACK back when talking to the xc3028. It could be a number of different things: * broken cx23885 i2c master implementation * bug in the xc3028 driver * screwed up GPIOs causing the xc3028 to be held in reset * i2c bus wedged > Also, nobody has any idea what i could try (except for what > i already did, including reverting patches and downgrading the kernel)? If you're knowledgeable enough to downgrade the kernel, then your best bet is to learn how to use git bisect so you can identify exactly which patch introduced the regression. > I don't think the card is that uncommon, because i've already seen some > pages stating problems with that card, at least 3 on this maillinglist > with exactly the same problem (not to talk about those people, who just > send the card back and replace it with something else/people who don't > use maillinglists/bugtracker) however, whether the card is common or > uncommon is not very helpful/useful, so.. it shouldn't really matter. Tens of thousands of cards sold. Three complaints. That should indeed give you an idea how few people are using the card under Linux. That said, the likelihood of a card getting fixed is largely related to how popular it is and the probability that some developer who actually cares has the card. > heh. I'm about to give up. just a pity because the card wasn't > cheap when it came out and every page states "supported in linux" which > seems to be not true anymore. I know that it was, back in 2008 when i > wrote with S. Toth about it. Well with Linux and open source in general, you get what you paid for. The only reason the card worked at all is because of the thousands of dollars worth of man-hours that developers like Steve donated to bring up the board in the first place. The downside of course is that since you paid *nothing* for Linux support, you cannot really complain when it stops working. If the card is unpopular and therefore there aren't developers willing to work on it, and you're not knowledgeable enough to fix it yourself, then you are largely SOL. > http://git.linuxtv.org/anttip/media_tree.git?a=commit;h=6676237398d0c2e61e5a3a27e0951f60d6ef6fe3 > > Here's the commit when the card was added. I was using it without any > trouble around that time. Well if someone knows what i could try (i > could also hack around in the source if someone tells me what to > change/where to change) i'd be very happy about ANY information. Yeah, if you can git bisect to identify which patch broke the support, Andy can probably offer some idea what is going on. 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
