0.3.2f doesn't work for me (PVR150MCE PAL), no sound ... Neither did
0.3.2e... I'm still using a full functional 0.3.2d driver (no patch
needed)
I'll try to locate the significant differences.
Jaap...
Chris Kennedy wrote:
This merges all recent patches except the most recent 4k stacks o
On Tue, 01 Mar 2005 23:13:01 +0100, Jelte van der Hoek
<[EMAIL PROTECTED]> wrote:
> It seems that you're querying the AFD_FMT_STAT based on the video
> presented before switching the source. Is that correct?
Yes.
--
Tyler Trafford
---
SF email
On Tue, 01 Mar 2005 23:13:01 +0100, Jelte van der Hoek
<[EMAIL PROTECTED]> wrote:
> This does not work for me either. I have a PVR500MCE PAL (rev D391).
>
> It seems that you're querying the AFD_FMT_STAT based on the video
> presented before switching the source. Is that correct?
>
> Anyway, the
On Tue, 1 Mar 2005 14:02:39 -0800, Jarod Wilson <[EMAIL PROTECTED]> wrote:
> On Tuesday 01 March 2005 08:05, Chris Kennedy wrote:
> > This merges all recent patches except the most recent 4k stacks one
>
> And one more -- the updated tuner defs for the FQ1236A MK4. I'll send along a
> new patch mo
This does not work for me either. I have a PVR500MCE PAL (rev D391).
It seems that you're querying the AFD_FMT_STAT based on the video
presented before switching the source. Is that correct?
Anyway, the biggest problem for the PVR500MCE PAL seems to be the
CH_SEL_ADC2=0. If I ioctl that register
On Tuesday 01 March 2005 08:05, Chris Kennedy wrote:
> This merges all recent patches except the most recent 4k stacks one
And one more -- the updated tuner defs for the FQ1236A MK4. I'll send along a
new patch momentarily that overhauls the ivtv-provided tuner module to be
more in line with the
On Sunday 27 February 2005 19:15, Jason Knisley wrote:
> Nope, actually, it's supposed to be on 0061. I deleted
> the ivtv-0.3.2e driver and started afresh and
> repatched and it's working now. The patched tuner
> module from ivtv shows that I have two of them on 61
> while the kernel tuner module
On Tuesday 01 March 2005 02:52, Todd Tidwell wrote:
> I'm gonna add a little more fuel to this fire ;)
>
> So after playing with this most of the day, I discovered something. My
> locking problem *only* happens in Myth in Live TV mode. If I record or I
> use mplayer to view the device, it works g
On Tue, 1 Mar 2005 02:52:07 -0800, Todd Tidwell <[EMAIL PROTECTED]> wrote:
> I'm gonna add a little more fuel to this fire ;)
>
> So after playing with this most of the day, I discovered something. My
> locking problem *only* happens in Myth in Live TV mode. If I record or I
> use mplayer to vie
This merges all recent patches except the most recent 4k stacks one
(need to redo that for the changes from the other patches fully broke it,
plus need the extra fix included which would enable me to quickly apply it
without manually fixing which I unfortunately don't have any time for at the
m
Hi all
Currently I am setting up the tda9887 by using i2cset:
i2cset 0 0x43 0x00 0x16
i2cset 0 0x43 0x01 0x70
i2cset 0 0x43 0x02 0x4a
I looked at tda9887.c and found that for "V4L2_STD_PAL_I" the values would be
set slightly differently to 0x14, 0x70 and 0x0a. I tried setting them
manually to
On Tue, 1 Mar 2005, Jason Knisley wrote:
well.. :P Not a picker of nits, or anything. Maybe
someone could throw together a bug/need-to-do tracking
database to make things a bit more organized?
...and a common source for all the patches floating around (a cvs/svn
server)? Right now it is a bit hard
I'm going to have to add a few things into this, as
well.. :P Not a picker of nits, or anything. Maybe
someone could throw together a bug/need-to-do tracking
database to make things a bit more organized? As for
the errors, see below.
--- Todd Tidwell <[EMAIL PROTECTED]> wrote:
> So after playing w
Note that many (all?) PVR-350s contain SAA7129 rather than 7127, and the
7129 has dedicated RGB/Cr-Y-Cb outputs.
Has anyone investigated this (or similar) at a hardware level, and if so,
any joy?
I only got as far as noting that these RGB pins didn't seem to go anywhere
useful. Unless your PCB is d
In article <[EMAIL PROTECTED]>, Matthew Hodgson
mailto:[EMAIL PROTECTED]> wrote:
> Has anybody had any success in extracting RGB+sync from the Philips
> SAA-7127 video encoder on their PVR-350 or similar? According to the
> Philips datasheet at
>
> http://www.semiconductors.philips.com/pip/SAA7
I'm gonna add a little more fuel to this fire ;)
So after playing with this most of the day, I discovered something. My
locking problem *only* happens in Myth in Live TV mode. If I record or I
use mplayer to view the device, it works great.
Also, The video quality is just lousy. Before this ca
> The attached patch is against the latest video4linux snapshot
> (20050224-133230), and adds tuner and tveeprom support for the Hauppauge
> PVR-500MCE (NTSC).
Merged, thanks.
Gerd
--
#define printk(args...) fprintf(stderr, ## args)
---
On Sunday 27 February 2005 19:15, Jason Knisley wrote:
> Nope, actually, it's supposed to be on 0061. I deleted
> the ivtv-0.3.2e driver and started afresh and
> repatched and it's working now. The patched tuner
> module from ivtv shows that I have two of them on 61
> while the kernel tuner module
On Monday 28 February 2005 21:38, Jarod Wilson wrote:
> On Monday 28 February 2005 20:03, Winston Chang wrote:
> > Hi Jarod -
> >
> > First off, thanks for all the hard work!
> >
> > I have a PVR-500MCE (NTSC) that gives the exact same tveeprom output,
> > except that my serial# is 7749933. ÂIt's n
19 matches
Mail list logo
