On Friday 23 December 2005 14:20, Mark Weaver wrote:
> Hans Verkuil wrote:
> > Hi all,
> >
> > I've started off 0.4.2 by applying the i2c patch from Mark Weaver
> > (ticket #29). I'd like people to try the 0.4.2 from svn whether or
> > not you have a IR blaster.
>
> Still working here. I have also tried it on a PVR-350, and another
> PVR-150 (total of 3). Seems to run OK on all of them. In the
> changelog you said:
>
> "- ticket #29: apply i2c patch to address PVR-150 IR chip issues.
> Also seems to fix i2c detection problems that occur in rare cases."
>
> would this be simply not finding a chip @ an i2c address? I've had
> plenty of reports of this (IR chip not found loading the driver, and
> i2c-detect not finding it either), but have never really made any
> progress with it.
No. The whole i2c bus seems to be unreachable. It happened only when
several PVR cards are present. Pull one out and the other works again.
I've seen two cases of this now and it seems that this patch fixes the
problem. It was really a case where the i2c subsystem simply could not
open the i2c bus.
Hans
>
> Hauppauge have released a new stable PVR-150 so if I get a chance
> I'll disassemble that as well and see if the i2c implementation has
> changed since the beta.
>
> On a slightly related note, I updated my codeset capture with the
> debug log hacked driver to include the new codesets that hauppauge
> have released (they have a supported STB list on the website as
> well). This was a lot less painful that fiddling about with a couple
> of PCs and some short wires, so thanks very much for that. I just
> hope I don't have to do it too often in future (I have to borrow a
> windows machine and rip apart my myth box to do so!)
>
> Thanks,
>
> Mark
>
>
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
