[pvrusb2] New driver snapshot: pvrusb2-mci-20080210

[Mike Isely]

On Sun, 9 Mar 2008, Mark Goldberg wrote:

> On Feb 11, 2008 11:01 PM, Mike Isely <isely at isely.net> wrote:
> > OK, I will try to reproduce it here.  In the mean time I don't have any
> > other suggestions, since the changes with this snapshot didn't direclty
> > involve anything that controls the digitizer or the encoder :-( Maybe
> > this is another initialization timing effect but even that seems pretty
> > far-fetched in this case.  I'll let you know what happens.
> 
> Do you have any ideas about this shifted vertical interval problem?
> I'm about to embark on an upgrade from myth .20 to .21, so it
> is as good a time as any to debug stuff.
> 
> Thanks

No, unfortunately I do not have any idea for the cause.  I do intend on 
attempting to reproduce what you are seeing, but I have some other tasks 
still in line before doing that however.

I can tell you however that it's the programming of the video digitizer 
that should be affecting this.  That is controlled by either saa7115.ko 
or cx25840.ko (depending on if you are using a 29xxx or a 24xxx device, 
respectively).  The pvrusb2 driver itself doesn't directly set up 
details like that - it just tells the module "use video standard XYZ and 
I want the capture resolution to be H x V", the rest is pretty much up 
to the module (i.e. saa7115.ko or cx25840.ko).  This is why I'm doubtful 
that recent pvrusb2 driver changes could be responsible.  This 
unfortunately doesn't align with your observations, so I really have no 
idea what is going on here.

  -Mike


-- 

Mike Isely
isely @ pobox (dot) com
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8