I am attempting to build the driver in the 0.2.3.h version and am getting
the following on my 2.6.9 kernel (built from scratch) system. It builds
d, e, and f just fine:
[EMAIL PROTECTED] driver]# make
make CONFIG_VIDEO_IVTV=m -C /lib/modules/2.6.9/build
M=/home/Share/Public/MythStuff/IVTV/ivtv-0.3
Hey Tyler,
No! I was loading the wrong module until now!
I assumed the new 'make install' would overwrite the earlier version.
modinfo instantly showed i was loading the old 0.3.2d version. the
0.3.2h loads perfectly and audio also works with my PVR150.
thank you,
R
On Mon, 7 Mar 2005 22:41:2
On Monday 07 March 2005 19:41, Tyler Trafford wrote:
> On Mon, 7 Mar 2005 22:31:44 -0500, Ram Yalamanchili <[EMAIL PROTECTED]>
wrote:
> > Actually, i just tried the 0.3.2h on the stock fc3 2.6.10-1.766 4k
> > stack kernel and it hung up the machine. I notice the same erorrs
> > which i had with 0.
On Mon, 7 Mar 2005 22:31:44 -0500, Ram Yalamanchili <[EMAIL PROTECTED]> wrote:
> Actually, i just tried the 0.3.2h on the stock fc3 2.6.10-1.766 4k
> stack kernel and it hung up the machine. I notice the same erorrs
> which i had with 0.3.2d. I am not sure what could be wrong, did you
> just compi
Actually, i just tried the 0.3.2h on the stock fc3 2.6.10-1.766 4k
stack kernel and it hung up the machine. I notice the same erorrs
which i had with 0.3.2d. I am not sure what could be wrong, did you
just compile the driver or did you have to apply a patch to make it
work with stock 4k kernels?
Hi, I get the following errors when I compiled the
latest ivtv driver version 0.2.0 (rc3h). I am using a
Pentium 3 550
running Redhat Linux 2.4.20-31.9 kernel
pvr 350 card
512 megs ram
Compiling ivtv driver version 0.2.0 (rc3f) is fine.
[EMAIL PROTECTED] driver]# make
cp ../utils/videodev2.h
The attached patch against v4l snap 20050307-161051 adds tveeprom support for
the PAL Hauppauge WinTV PVR-150 and 500 cards (idx 91 and 97), as well as
cleaning up their associated tuner descriptions just a touch. According to
the Hauppauge tveeprom, type 56 is not FM1216ME, its a FQ1216AME MK4
On Monday 07 March 2005 16:36, Roel Teuwen wrote:
> Jarod : the card now shows an image with your patches, only ivtv needs
> to be loaded, the rest is pulled in. thanks for your work !
>
> Sorry for wasting your time, all.
No problem, I'm just happy to hear it works! Hard for me to test it myself,
Justin wrote:
>
> Just looking for info on how to get both cards to run in my
> MythTV box, I'm getting this error -
>
> Mar 2 20:35:22 myth kernel: tveeprom: Encountered bad packet
> header [04]. Corrupt or not a Hauppauge eeprom.
>
> using kernel 2.6.10-1.760 - FC3
>
> Anyone running both
On Mon, 7 Mar 2005 19:17:57 -0500, Tyler Trafford <[EMAIL PROTECTED]> wrote:
> Roel Teuwen <[EMAIL PROTECTED]> wrote:
> > There isn't, this was the first thing I checked :(
> > If anyone has any ideas on how to troubleshoot this, let me know
> >
> > I have tried the following : removed all ivtv and
Boleslaw Ciesielski wrote:
Chris Kennedy wrote:
And second my pvr500, just got around to trying them
finally, and they randomly reboot my system, seems like possibly
heat, they
get really hot, it's also a cheap VIA motherboard, anyone else seen
this.
This could also be a borderline power supply.
Roel Teuwen <[EMAIL PROTECTED]> wrote:
> There isn't, this was the first thing I checked :(
> If anyone has any ideas on how to troubleshoot this, let me know
>
> I have tried the following : removed all ivtv and tuner modules from
> my system, rebooted, did a make install, modprobe ivtv by hand:
On Mon, 7 Mar 2005 15:13:25 -0800, Jarod Wilson <[EMAIL PROTECTED]> wrote:
> On Monday 07 March 2005 15:07, Roel Teuwen wrote:
> > Using a PVR150 PAL and ivtv-0.3.2g or 0.3.2h with both patches applies
> > still only gives out static. I get the following :
> [...]
> > tveeprom: Hauppauge: model = 2
In article <[EMAIL PROTECTED]>, Matthew Hodgson
mailto:[EMAIL PROTECTED]> wrote:
> Thomas Olsson wrote:
>
> >> Note that many (all?) PVR-350s contain SAA7129 rather than 7127, and the
> >> 7129 has dedicated RGB/Cr-Y-Cb outputs.
>
> Hm, that's strange - I have 5 PAL WinTV PVR-350 cards here, and
On Monday 07 March 2005 15:07, Roel Teuwen wrote:
> On Mon, 7 Mar 2005 00:24:22 -0800, Jarod Wilson <[EMAIL PROTECTED]> wrote:
> > If some PAL PVR-150 and/or 500 users could give these a shot, it'd be
> > much appreciated. When coupled with Tyler's
> > audiofmt-makefile-autotune.032g.patch patch, t
On Mon, 7 Mar 2005 00:24:22 -0800, Jarod Wilson <[EMAIL PROTECTED]> wrote:
> If some PAL PVR-150 and/or 500 users could give these a shot, it'd be much
> appreciated. When coupled with Tyler's audiofmt-makefile-autotune.032g.patch
> patch, this *should* auto-detect and auto-configure both the LG an
On Monday 07 March 2005 14:09, Ram Yalamanchili wrote:
> Hey,
>
> Is the problem of driver hanging up the 4k stack 2.6 kernels solved?
>
> I tried 0.3.2d with the pvr-150 audio patch and it just hung up my machine
> :(
The 0.3.2g and later releases contain a 4kstacks patch, and the driver now
loa
Hi,
I have build a xine plugin for the PVR-350 TV output.
This plugin uses the osd for output.
To use the pluging you have to set the FRAMEBUFFER environment variable.
You can use it without X using the following command:
#> export FRAMEBUFFER=/dev/fb2
#> fbxine -V ivtvfb -A alsa dvd:// --stdctl
al
Another point of reference, I have a PVR-250 MCE and have no luck
getting radio to play. I get staticy TV tuner audio instead. This is using
the 0.3.2.f version.
Rob
Louie Ilievski wrote:
Lars Kellogg-Stedman wrote:
I recently bought a PVR-150 PAL. Tuner and composite input work
apparently without
Hey,
Is the problem of driver hanging up the 4k stack 2.6 kernels solved?
I tried 0.3.2d with the pvr-150 audio patch and it just hung up my machine :(
Thanks,
R
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews
Lars Kellogg-Stedman wrote:
I recently bought a PVR-150 PAL. Tuner and composite input work
apparently without problems with 0.3.2f.
Since I don't have an antenna plugged to the card and I planned to buy
one, I need to know if the FM tuner/audio is currently supported.
As a reference point, I've g
Most of this conversation is correct.
YUV output will allow less data to be sent per frame to the card. This means
we can achieve a higher frame rate and their should be less chance of
tearing though it does not eliminate it(unless we can get fancy and dma to a
spare location and then blt the data
> Oh, I'd take any patches that apply cleanly I guess.
Attached. Really three small patches:
1. Make newer kernel msp3400 drivers just work (no more ivtv msp3400)
2. Increase the mpeg buffer size (the current default is too small)
3. Patch chann.c so you can pass in the device (and switch it to u
On March 7, 2005 02:21 pm, Kohlsmith, Andrew wrote:
>> without any tearing. Of course the quality of playback will be dependent
>> upon the speed of the computer's processor since the computer will be
>> decoding the video to YUV before passing it along to the PVR-350.
>
>Well it's currently conver
A related question: is there any chance that at some point in the
future we'll be able to send arbitrary sound out through the PVR-350
TV-out (not just sound muxed with MPEG-2 video)? This would eliminate
the need to pass the TV-out sound through the audio card to get all
types of audio to the so
> I recently bought a PVR-150 PAL. Tuner and composite input work
> apparently without problems with 0.3.2f.
> Since I don't have an antenna plugged to the card and I planned to buy
> one, I need to know if the FM tuner/audio is currently supported.
As a reference point, I've got a PVR-350, and I'
On Monday 07 March 2005 09:37, Peter Martens wrote:
> > If some PAL PVR-150 and/or 500 users could give these a shot, it'd be
> > much appreciated. When coupled with Tyler's
> > audiofmt-makefile-autotune.032g.patch patch, this *should* auto-detect
> > and auto-configure both the LG and Philips tun
On March 7, 2005 02:14 pm, Sager, Jim wrote:
> without any tearing. Of course the quality of playback will be dependent
> upon the speed of the computer's processor since the computer will be
> decoding the video to YUV before passing it along to the PVR-350.
Well it's currently converting between
You're correct that we can play things through the framebuffer, however,
we get some tearing because the framebuffer is too slow to keep up with
the video. Although things work, it's not the appropriate way to use the
framebuffer. YUV decoding support should allow us to play back video
without any
On March 7, 2005 01:50 pm, Sager, Jim wrote:
> I don't mean to be pushy since my ability to help develop the driver is
> quite lacking. This, to me, is the one last area that would give MythTV
> a real boost with respect to playing virtually any type of video format
> thru the PVR-350 tv-out.
I th
Basically yes that is the current state.
I have the start of the Xv support but can't work out
where to push the data reliably.
Axel was asking them for the information and the
response time was previously 4-6 weeks so i'm hoping
that means we should get something soon but i've been
trying not to
I'm trying to remember where the driver was at with respect to YUV decoding.
If memory serves me right, we know what the YUV format should be but we don't
know precisely how to push it out to the buffers on the card. Is this correct?
I would imagine that Hauppauge needs to figure out what they can
Hello,
I recently bought a PVR-150 PAL. Tuner and composite input work
apparently without problems with 0.3.2f.
Since I don't have an antenna plugged to the card and I planned to buy
one, I need to know if the FM tuner/audio is currently supported.
This is the output of my modprobe:
Mar 6 19:36:07
I'm still waiting for feedback from Hauppaugge.
John
--- "Sager, Jim" <[EMAIL PROTECTED]> wrote:
> I haven't seen any buzz as of late with respect to
> YUV decoding. I was just curious as to what state
> this is in. Is anyone doing any developing on this?
>
> Thanks,
> Jim
>
--
Oh, I'd take any patches that apply cleanly I guess, just can't manage
both sources at the same time, and must have missed the msp3400 changes
from lack of time to read through the mailing list closely, but just
consider me dense if missed a patch and re-email, I don't mind and know
I miss things s
> If some PAL PVR-150 and/or 500 users could give these a shot, it'd be much
> appreciated. When coupled with Tyler's audiofmt-makefile-autotune.032g.patch
> patch, this *should* auto-detect and auto-configure both the LG and Philips
> tuners on PAL PVR-150 cards.
>
> FYI:
> The only difference on
Hi,
my PVR350 also have an SAA7127 decoder. I traced the 'B' or 'CVBS'
Signal to the backside of the PCB near the PCI connector (right edge,
approx. 2cm towards the PCB) . There is a unpopulated pad called "R118"
where it should be easy to solder a wire at.
Looking forward to get RGB Output :-)
Title: YUV Decoding
I haven't seen any buzz as of late with respect to YUV decoding. I was just curious as to what state
this is in. Is anyone doing any developing on this?
Thanks,
Jim
My Myth box is *so* close to being finished, but I'm stuck with a
semi-frequent (every day or two) lock-up that means I can never
guarantee I'll get a recording OK :(
Every so often, a recording generates zero bytes, and Myth becomes
deeply unhappy about this (it doesn't seem to realise, it
Thomas Olsson wrote:
Note that many (all?) PVR-350s contain SAA7129 rather than 7127, and the
7129 has dedicated RGB/Cr-Y-Cb outputs.
Hm, that's strange - I have 5 PAL WinTV PVR-350 cards here, and they all
have an SAA7127H chip as the decoder. The board revision silkscreened to
the topright of
Hi everybody!
I've been trying to get the radio of my PVR 350 running... no success so
far. TV and VBI works perfect (thanks for the good work, guys!!), but with
'radio -f xxx.xx' I just get noise, doesn't matter what frequency I use
(tuning TV with ptune-ui.pl works fine) Running 'radio -f xxx.xx
as a slight aside, when i run X on my 350, i've found it not fast
enuff to run pre-archived xvids on my 2.6 celly in a pundit-r.
On Sun, 6 Mar 2005 14:23:34 -0600, Joseph Burdick
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> Like many, I am following Jarod Wilson's Howto for a mythtv using FC3
> and t
I am using a pvr-150 OEM card with the composite input and I am seeing a
strange picture quality issue. Sometimes the picture appears to have a
second ghost image overlaid on top of the main image. This second image is
about 2 or 3 scan lines higher than the main picture and is quite noisy,
mak
Op ma 07-03-2005, om 09:03 schreef Jarod Wilson:
> > (Or they have to depend on there distro makers.)
>
> Also not necessarily. :-)
>
> ATrpms.net provides v4l builds in rpm form for Fedora Core and Red Hat.
You make it sound that using a distro is almost easyer than building
from source ;-)
-
Op ma 07-03-2005, om 09:24 schreef Jarod Wilson:
> If some PAL PVR-150 and/or 500 users could give these a shot, it'd be much
> appreciated. When coupled with Tyler's audiofmt-makefile-autotune.032g.patch
> patch, this *should* auto-detect and auto-configure both the LG and Philips
> tuners on
If some PAL PVR-150 and/or 500 users could give these a shot, it'd be much
appreciated. When coupled with Tyler's audiofmt-makefile-autotune.032g.patch
patch, this *should* auto-detect and auto-configure both the LG and Philips
tuners on PAL PVR-150 cards.
FYI:
The only difference on the tuner
On Sunday 06 March 2005 19:13, Jeffrey Zellman wrote:
> ivtv: Setting Tuner 47
> tuner 0-0061: type set to 47 (LG NTSC (TAPE series))
NTSC tuner...
> ivtv: Setting audio matrix to input 3, output 1
> ivtv: Switching standard to PAL.
> ivtv: ivtv_enc_thread: pid = 2539, itv = 0xd09ab780
> ivtv: iv
On Sunday 06 March 2005 12:23, Joseph Burdick wrote:
> I presume that Jarod's statement under Running X on the PVR-350's
> TV-Out - "Note that the ivtvdev X driver is included with the
> ck-series ivtv drivers, so no need to fetch it, just use it." somehow
> isn't working for me.
Always, alwa
On Sunday 06 March 2005 10:48, Jaap Struyk wrote:
> Op zo 06-03-2005, om 18:52 schreef Jarod Wilson:
> > We'd eventually like to stop including a tuner module at all with ivtv,
> > and stick to using strictly the v4l one
>
> I yust installed 2.6.11 so went diggin trough the v4l/tuner docs, but
> "L
49 matches
Mail list logo
