-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of Jesse Guardiani
Sent: 28 September 2005 18:07
To: Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] PVR 350 host uptimes?
John Harvey wrote:
Which version
Probably not till the end of the week.
Sorry going to be busy most nights until then and any
spare time i have i want to try and get one more fix
to reduce the cpu usage in before Hans releases 0.3.9.
John
--- Petter Gundersen [EMAIL PROTECTED]
wrote:
On 10/4/05, John Harvey
[EMAIL PROTECTED
Hans
I have one more fix for the yuv code but I'm really busy and I don't
think I'll get it in until Saturday morning at the moment but I'll see if I
can find half an hour before then. Sorry but the cpu savings I have made for
playback are probably worth it, especially given that the 350
I have just submitted a patch for the YUV playback
code which significantly reduces the cpu used during playback using the Xv
code.
Now the CPU usage for X has dropped from about 30-35%
to about 0.5 2%. So I can now play back stuff with mplayer burning
~13%cpu and I have between 80 85%
Just tried with 2.95.3 on a sun machine at work and
get parse error before `)'
adding ,1 removed the error.
John
--- Hans Verkuil [EMAIL PROTECTED] wrote:
Gcc 2.95 will compile kernels up to 2.6.12.6 and
probably also newer
ones
without problems, because no one there does
#define
for these tests.
All of this made me wonder about the recommended configuration for use
of Xv. John (or others), do you have any such recommendations or
should we just figure it out using trial-and-error?
Cheers,
Wilf.
On 07/10/05, John Harvey [EMAIL PROTECTED] wrote:
I have just submitted
Have you tried enableing or disabling flicker
reduction for the OSD?
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ruud Huynen
Sent: 15 October 2005 19:52
To: Discussion list for
development of the IVTV driver
Subject: Re: [ivtv-devel] Feedback
on xdriver
The owner field the priv fields have been removed from the v4l
video_device structure.
Deleting the 2 lines (78 196) are enough to make it compile.
The first is fine. The second should be safe since it was setting private
data that never appears to be used.
John
-Original Message-
I did look at the time to see if there was
any support for changing the mode. If you find a good place to do it I could
add an atom the xdriver to change.
That way you wouldnt need to make
ivtv specific calls but the xdriver would do it for you. Similar to the way the
color key stuff is
Mail me your xorg. Conf log file and I'll take a look.
JOhn
-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of Rudy Zijlstra
Sent: 22 October 2005 23:06
To: ivtv-devel@ivtvdriver.org
Subject: [ivtv-devel] xorg problem
Dear,
I had a
-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of Andrew Kohlsmith
Sent: 24 October 2005 21:03
To: ivtv-devel@ivtvdriver.org
Subject: Re: [ivtv-devel] Someone with a PVR-350 please spot-check
thisstatement from the MythTV HOWTO
On
The file /lib/modules/ivtv_init_mpeg.bin is used to initialise the decoder
so that xv playback works. It does not have any effect on decoding. Anyway
does that file exist? If not then it should be in the sources if you built
from source so you should be able to copy it there manually to remove
Are you using a boot image built with mkinitrd? If so then then
ivtv_init_mpeg.bin probably isn't in it.
Failing to load this file is why you get the YUV message at the end of
dmesg.
John
-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of
Assuming freevo has Xv support why don't you just run X on the framebuffer
and use the Xv support for playback?
John
-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of Duncan Webb
Sent: 05 November 2005 04:36
To: Discussion list for
anything that talks to X is also an advantage
occasionaly.
Thanks for the feedback on the documentation in the
code. I'll fix it later and check the readme i added
as well.
Thanks
John
--- Duncan Webb [EMAIL PROTECTED] wrote:
John Harvey wrote:
Assuming freevo has Xv support why don't you just
--- Nick Rosier [EMAIL PROTECTED] wrote:
On 11/8/05, Stef Bon [EMAIL PROTECTED]
wrote:
Hello,
I've got a PVR-150, and I can't get it working.
I've got it for almost a year
now, and never got it working.
Now I'm using ivtv-0.4.0.
ivtv-detect gives:
driver: ivtv-0.4.0
So surely what we need then is a statement that as of
0.6 (or whatever it's called when it is released) ivtv
is compatible with kernel 2.6.xx (15?) or requires
this release of v4l2.
This would of course mean that probably we would want
a kernel v4l2 release to happen before we can
release ivtv
What software is everyone using? There is a known problem with myth 0.18
release that causes systems to hang/crash.
This happens during playback in myth when the screen is cleared after
displaying menus.
If people are using myth 0.18 this is the most likely cause of the problem.
John
-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of Steve Laurie Sanders
Sent: 13 November 2005 16:02
To: Discussion list for development of the IVTV driver
Subject: RE: [ivtv-devel] ivtv framebuffer is broken with PVR350
Well, I tried
-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of Jacques Facquet
Sent: 14 November 2005 01:35
To: ivtv-devel@ivtvdriver.org
Subject: Re: [ivtv-devel] ivtv framebuffer is broken with PVR350
Le Dimanche 13 Novembre 2005 21:07, John
]
[mailto:[EMAIL PROTECTED] Behalf Of John
Harvey
Sent: Monday, November 14, 2005 1:24 PM
To: 'Discussion list for development of the IVTV
driver'
Subject: RE: [ivtv-devel] ivtv framebuffer is broken with PVR350
Apologies if you've already done some of this but the thread is getting long
]
[mailto:[EMAIL PROTECTED] Behalf Of John Harvey
Sent: Monday, November 14, 2005 1:24 PM
To: 'Discussion list for development of the IVTV driver'
Subject: RE: [ivtv-devel] ivtv framebuffer is broken with PVR350
Apologies if you've already done some of this but the thread is getting
long
would have a good dose of the information they
require to resolve problems.
I believe SuSE has a similar tool called siga.
Thanks,
Greg
From: John Harvey [EMAIL PROTECTED]
Reply-To: Discussion list for development of the
IVTV
driverivtv-devel@ivtvdriver.org
To: 'Discussion list
-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of Duncan Webb
Sent: 15 November 2005 22:06
To: Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] ivtv framebuffer is broken with PVR350
John Harvey wrote
It's not a problem as such, it's just the way it
works.
Sollutions are to use window managers that allow you
to choose a smaller virtual desktop.
Or if you are running mythtv then you can set it's
overscan settings to work round this.
We are however working on implementing something that
will
The Htiming Vtiming lines in your config tell X to run with 800x600
resolution.
I'm not sure where these values came from but they don't match those in
either README.xdriver or ivtv-osd.c.
If you make them match those it should run at 720x480 correctly.
John
-Original Message-
From:
-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of Hans Verkuil
Sent: 04 January 2006 22:21
To: [EMAIL PROTECTED]; Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] ivtvdriver.org: Firmware section rewrite
On
-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: 08 January 2006 10:26
To: ivtv-devel@ivtvdriver.org
Subject: Re: [ivtv-devel] MythTV-ivtv volunteer wanted!
Well, I have a PVR-350 (well, actually 2; still
if
anyone is working on trac bug #55 (XV/YUV video output
on PVR 350 drops frames while encoder is encoding).
I was the one who submitted the bug report. I sure
wish I had the ability to go in and debug the issue
myself, but it's way over my head. I suspect John
Harvey would like to work
I haven't used it in ages. Nothing has changed for quite a while though in
that area for ages either but I'll try to take a look over the next few
days.
What version of myth are you using?
What is your input source (I assume it's the 350)?
What resolution do you record at?
john
-Original
-
[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: 12 January 2006 00:36
To: John Harvey; 'Discussion list for development of the IVTV driver'
Subject: Re: [ivtv-devel] XV/YUV mode and broken Myth EPG
1) mythtv 0.18.1 latest from svn (saw the same
behavior from a ~4 month old version of myth
-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of Joe Votour
Sent: 15 January 2006 02:08
To: Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] [Fwd: X problems with 0.4.1]
--- Rudy Zijlstra [EMAIL
-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of Fredrik Trotzig
Sent: 17 January 2006 22:38
To: ivtv-devel@ivtvdriver.org
Subject: [ivtv-devel] ivtv-0.4.2 ivtvctrl -H
Hi.
After upgrading i had just clutter on the screen when
They should be info's not warnings. I'll change them over the next few days.
Thanks for pointing it out.
John
-Original Message-
From: Graeme Wilford [mailto:[EMAIL PROTECTED]
Sent: 19 January 2006 10:32
To: ivtv-devel@ivtvdriver.org; John Harvey
Subject: ivtv-osd warnings after
-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of Harley Peters
Sent: 29 January 2006 00:26
To: Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] time out waiting for firmware
Martin Dauskardt wrote:
PVR350
Probably.
I'll have a think about it but no promises on time frame.
John
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilhelm Eger
Sent: 06 February 2006 15:11
To: ivtv-devel@ivtvdriver.org
Subject: [ivtv-devel] xdriver glx extension
Hello,
Anybody has succes with YUV (nv12) output ?
yuv_fixup compleatly broken ?
John Harvey might know this.
Yes it has worked but I never use it. Mplayer can play the nv12 without
enabling yuv_fixup (at least on my 350).
JOhn
___
ivtv-devel
just ask
TIA
Dunc
John Harvey wrote:
These come from the Xv attribute setting getting methods.
For some
reason they are being asked to set or get attributes that the ivtv
driver doesn't understand.
I have no idea what would cause this unless somehow myth is getting
Which version of the X driver are you using?
John
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Wilfried Philips
Sent: 27 February 2006 23:32
To: ivtv-devel@ivtvdriver.org
Subject: [ivtv-devel] kernel-oops ivitv-0.4.2 kernel 2.6.15.4
is unwatchable.
IIRC, John Harvey thought he knew what was causing this back
in October last year but I don't think he's had time to work
on it since...
Regards,
Wilf.
On 25/02/06, bbee [EMAIL PROTECTED] wrote:
Hi all,
I recently bumped my PVR350 box from a old 0.1.9 ivtv / old
2.6
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of bbee
Sent: 12 March 2006 01:33
To: Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] The xdriver/xv drama (stutter)
Hi,
On Sat, 11 Mar 2006, John Harvey wrote:
I
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Axel Thimm
Sent: 04 April 2006 21:57
To: D. Hageman; Discussion list for development of the IVTV driver
Subject: [ivtv-devel] forking ivtv xdriver (was:
xorg-x11-drv-ivtv-0.10.6)
On Thu, Mar
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeff Simpson
Sent: 05 April 2006 20:48
To: D. Hageman; Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] forking ivtv xdriver
On 4/5/06, D. Hageman dhageman@dracken.com
No those aren't errors just debugging.
That all looks fine.
What actually happens?
John
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matthias Meyer
Sent: 22 May 2006 20:23
To: ivtv-devel@ivtvdriver.org
Subject: [ivtv-devel] Fwd: [ivtv-users]
The path given to xmkmf should be to the xc directory within the source
directory.
Normall I would expect that to be
xmkmf /usr/src/xorg-x11-6.9.0/xc
Imake.tmpl should be within your X source tree.
John
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
] Please test: 0.4.6/0.6.3 prerelease
Hmm, that's decoder stuff. Unfortunately, that's not my area
of expertise. Perhaps John Harvey can help here?
Anyway, I think it is unrelated to the frequency change fix.
Hans
On Friday 16 June 2006 23:53, Stanley Merkx wrote:
Well, perhaps
stuff. Unfortunately, that's not my area
of expertise. Perhaps John Harvey can help here?
Anyway, I think it is unrelated to the frequency change fix.
Hans
On Friday 16 June 2006 23:53, Stanley Merkx wrote:
Well, perhaps the hang-while-watching-recording is not completely
Myth's
Thanks.
I'll fix this in svn in the next day or two.
John
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Graham
Sent: 15 May 2006 11:53
To: ivtv-devel@ivtvdriver.org
Subject: [ivtv-devel] a patch for segfault on loading ivtv-fb
(ivtv-0.4.5)
--- Duncan Webb [EMAIL PROTECTED] wrote:
John Harvey wrote:
Can you also determine if it's the same cmd (ie
0x60).
What do you mean the same cmd? Do you mean each time
it crashes?
0x60 isn't an ioctl command, is it a X driver
command?
The video is being played
I don't understand your'e question. The mmap does nothing other than
printing the warning.
Implementing mmap with the 350 is dificult to do efficiently.
John
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matthias Meyer
Sent: 07 July 2006 16:23
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jelle
Sent: 02 December 2006 21:57
To: Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] 50% CPU usage while using PVR350
tv-out and mythtv
Hans Verkuil wrote:
On
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hans Verkuil
Sent: 30 January 2007 06:45
To: Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] Fixed bug in trunk, please test!
On Tuesday 30 January 2007 01:51,
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ian Armstrong
Sent: 02 February 2007 17:52
To: Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] Fixed bug in trunk, please test!
On Friday 02 February 2007 16:40,
I'll try to take a look tomorrow.
John
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin R. Page
Sent: 05 June 2007 18:05
To: ivtv-devel@ivtvdriver.org
Subject: [ivtv-devel] ivtv_xdriver fails to build
Having worked around my ivtv-fb
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Greg Hormann
Sent: 28 August 2007 02:11
To: ivtv-devel@ivtvdriver.org
Subject: [ivtv-devel] ivtv-fb: Oops: mtrr: type mismatch
I've tried to use ivtv-fb from both 1.0.0 and 1.0.2. With
awhile
ago, but it's been so long since I've used the PVR-350 for output I'm
probably mistaken. Anyway, if someone has any idea why this is happening, or
can point me in some direction (such as this is a mythtv-issue) I'd
appreciate it.
I'd also like to thank the developers (Ian Armstrong, John Harvey
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of James Angi
Sent: 26 December 2007 18:54
To: ivtv-devel@ivtvdriver.org
Subject: Re: [ivtv-devel] PVR-350 MythTV
I normally use Xv for display rather than the 350 output directly so i
wouldn't normally see this problem. Is
-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of Mark Bryars
Sent: 09 January 2008 12:15
To: Hans Verkuil
Cc: Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] Crashes with ivtv on 2.6.24-rc3
Hans Verkuil
58 matches
Mail list logo