Strange.
No there shouldn't be any dependencies other than a
reasonably current version of myth. I think anything
0.17 or newer will be ok. 
I would probably suggest using 0.2 driver unless you
have a good reason to go to 0.3. That is what i have
been using and there are some small issues with 0.3
that i'll work around at some point.
Those X errors can be ignored and one day i'll remove
them from the X driver.

John
--- Roger James <[EMAIL PROTECTED]> wrote:
> 
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> [mailto:ivtv-devel-
> > [EMAIL PROTECTED] On Behalf Of John
> Harvey
> > Sent: 20 March 2005 22:01
> > To: [email protected]
> > Subject: RE: [ivtv-devel] Black screen after EPG
> fix - exacerbates jump
> > forward/back hang
> > 
> > Well I can't work out what is wrong in the driver
> and I have become
> > increasingly suspicious that the BltFill in the
> firmware is going wrong
> > occasionally.  But having said that this is
> absolutely repeatable with my
> > new code and I don't understand why.
> > So anyway attached are 2 files for myth (that go
> in libs/libmythtv that
> > avoid using bltfill and seem to work for me.
> > 
> > Any problems (or success) let me know, and if it
> all looks good I'll
> > prepare
> > another patch properly for myth.
> > 
> > John
> > 
> 
> John
> 
> Are there any particular dependencies from this code
> to versions of the ivtv
> driver or your ivtvdev X driver. I am using rc3f but
> my ivtvdev driver may
> be a little older.
> 
> I am afraid I did not have much success with the
> latest patch. I did not get
> as far as checking whether the hang had improved,
> because the EPG display
> was broken. The start up of the EPG was very jerky
> and took a while, when it
> stabilised a portion of it was missing (the bottom
> half of the detailed info
> of the current selected program) by paging up and
> down a few times I was
> able to get it all painted. However when I exited
> the black screen was still
> there :-(
> 
> Thanks for all the effort you are putting in.
> 
> It does not go unnoticed!
> 
> I notice that the XFree86 log has the following
> errors in it.
> 
> (EE) IVTVDEV(0): FBIOPAN_DISPLAY: Invalid argument
> (EE) IVTVDEV(0): FBIOBLANK: Invalid argument
> 
> I don't know of they are relevant. They are also
> present with the current
> CVS build of myth.
> 
> Roger
> 
> 
> 
> 
>
-------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT
> Products from real users.
> Discover which products truly live up to the hype.
> Start reading now.
>
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to