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

[roger]

FYI: Just read this quickly and noted you wanting to upgrade to
mythtv-0.21.  Mythtv-0.21 is still HARD MASKED within Gentoo's Portage
build system.  If it were just masked by keywords to prevent bringing
into a stable system, I'd upgrade also with minimal problems.  HOWEVER.
Being hard-masked means something is more then likely broken and needs
work. (ie. one or more severe bug report filed on bugs.gentoo.org)

Be informed.  Be forewarned. ;-)

For kicks, I'm going to browse bugs.gentoo.org for mythtv-0.21 related
bug reports  ... knowing mythtv's history and Gentoo's masking history,
something probably *is* severely broken. 

Seems just yesterday mythtv went stable with 0.21 too... but still,
knowing mythtv's past history, something usually does break... such as
having to rebuild mythtv's mysql database ... worse case scenario,
installing new or from scratch!

On Sun, 2008-03-09 at 08:11 -0700, 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
> 
> Mark
> _______________________________________________
> pvrusb2 mailing list
> pvrusb2 at isely.net
> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
> 
--
Roger
http://www.eskimo.com/~roger/index.html
Key fingerprint = 8977 A252 2623 F567 70CD 1261 640F C963 1005 1D61

Sun Mar 9 14:29:49 AKDT 2008