On Wednesday 02 February 2005 05:39 pm, John Harvey wrote:
> Attached is the re-worked pvr-350 patch. I have removed all the region
> update code so this now has an option to include installed ivtv header file
> in settings.pro and if its there it uses the BLT_FILL ioctl instead of the
> memset /pr
Attached is the re-worked pvr-350 patch. I have
removed all the region update code so this now has an option to include
installed ivtv header file in settings.pro and if its there it uses the
BLT_FILL ioctl instead of the memset /prep_frame method. Some of the other code
is re-organised to
On Wednesday 02 February 2005 04:39 am, John Harvey wrote:
> I just changed my mind 3 times while replying.
Hehe. =)
> I suspect in the end you may be right since i want to
> get the driver to be able to update a rectangular
> region we could/should add an interface for that and
> then make the d
I just changed my mind 3 times while replying.
I suspect in the end you may be right since i want to
get the driver to be able to update a rectangular
region we could/should add an interface for that and
then make the driver optimise that as best as it can.
If i rework the patch to just do the bi
On Wednesday 02 February 2005 03:13 am, John Harvey wrote:
> Isaac
> Any news on what I need to do to this patch before you commit it?
I don't know, the patch just seems really messy to me and it doesn't seem like
an application is the best place for it. Don't you think the driver should
be ha
;ll rework it.
>
> John
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:mythtv-dev-
> [EMAIL PROTECTED]
> > On Behalf Of John Harvey
> > Sent: 21 January 2005 08:58
> > To: Development of mythtv
> > Subject: Re: [mythtv] [PATCH]pvr-
> Sent: 21 January 2005 08:58
> To: Development of mythtv
> Subject: Re: [mythtv] [PATCH]pvr-350 performance patch
>
> Probably because i didnt find it.
> Can you point me in the right direction and i'll take
> a look again.
>
> >From memory this does use most
Probably because i didnt find it.
Can you point me in the right direction and i'll take
a look again.
>From memory this does use most of the region code but
passes the information out so the ivtv driver can use
it since the regions werent available internally.
John
--- Isaac Richards <[EMAIL
On Sunday 09 January 2005 04:52 pm, John Harvey wrote:
> The attached patch is a slightly cleaned up version of a patch several
> people have been using with recent ivtv drivers.
Any reason why the existing region code wasn't used more directly? Seems
you're duplicating logic..
Isaac
No its nothing to do with this. This patch just
affects the performance of the OSD when watching live
tv or a recording.
It sounds like you are still using X to display the
tv. The 350 support needs to be enabled in the
setup/.../playback section and mythtv needs to be able
to succesfully open play
I have X working on the PVR-350 output with the latest ivtvdev driver
(v0.8) but I'm really confused with mythtv : I can't watch MPEG-2
recordings or live tv except sometimes at really poor framrate but xvid
transcoded files are working, besides that the GUI of the frontend is
displayed without
It isn't a massive difference now that most of the
driver is stable and seems to cope with playing,
recording & OSD updates, but it does reduce the amount
of data transfered significantly which helps when
something like when the new channel information is
faded out after switching channel in live t
John,
applied the patch to my CVS-build; all seems to work fine. Didn't
notice performance improvements but then again, it doesn't seem slower
either (speed you get used to, slowness not...). No errors, lock-ups
or anything so far and I've tried using the OSD extensivelly.
N.
On Sun, 9 Jan 2005
The attached patch is a slightly cleaned up version
of a patch several people have been using with recent ivtv drivers.
I have modified the original patch to
1) Work
with older ivtv code
2) Have
an option in settigs.pro to allow the inclusion of an installed ivtv header
14 matches
Mail list logo
