Mailing List Archive: ivtv: devel

[PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch

1 2

View All

Index | Next | Previous | View Threaded

jarod at wilsonet

Feb 23, 2005, 2:19 PM

Post #1 of 29 (2305 views)
Permalink

[PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch

Here's a cumulative patch against ivtv 0.3.2e, containing Jelle's vsync patch,
Jaap's picture controls patch, Tyler's pg600/150mce patch and a tuner patch
that *hopefully* works with the PVR-500MCE NTSC's tuner.

Almost completely untested, since my 150 and 500 are being stupid right now...

--
Jarod Wilson
jarod [at] wilsonet

Attachments:

ivtv032e-vsync-control-mcefixes-500tuner.patch.gz (5.26 KB)

ivtv-devel at universalmac

Feb 23, 2005, 6:06 PM

Post #2 of 29 (2238 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

Jarod:

I'll roll this out with my PVR-500MCE tonight and let you know how it
goes. Will this work with the stock FC3 2.6.10_766 kernel or does it
still require a no 4K stacks kernel? How about 2.6.11rc4? Anything
else I need or just the proper kernel+3.2.e+this patch?

Noah

On Feb 23, 2005, at 1:19 PM, Jarod Wilson wrote:

> Here's a cumulative patch against ivtv 0.3.2e, containing Jelle's
> vsync patch,
> Jaap's picture controls patch, Tyler's pg600/150mce patch and a tuner
> patch
> that *hopefully* works with the PVR-500MCE NTSC's tuner.
>
> Almost completely untested, since my 150 and 500 are being stupid
> right now...
>
> --
> Jarod Wilson
> jarod [at] wilsonet
> <ivtv032e-vsync-control-mcefixes-500tuner.patch.gz>

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

jarod at wilsonet

Feb 23, 2005, 6:40 PM

Post #3 of 29 (2275 views)
Permalink

Re: Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

On Wednesday 23 February 2005 17:06, Noah Patton wrote:
> Jarod:
>
> I'll roll this out with my PVR-500MCE tonight and let you know how it
> goes.

Unfortunately, two folks have already said no go on the tuner. I'm hoping the
vsync patch will at least let me be able to test mine tonight...

> Will this work with the stock FC3 2.6.10_766 kernel or does it
> still require a no 4K stacks kernel?

Still need a non-4kstacks kernel, haven't got around to the patches that are
supposed to remedy that. I've actually got my 150 and 500 in a Debian
box. :-)

> How about 2.6.11rc4?

Straight 2.6.11-rc4 should work, I think. I tried 2.6.11-rc4 plus the latest
kraxel patch at one point, but I got next to nowhere with it (its pretty
invasive, lots of code refactoring, integration w/dvb, etc). I'm back to a
Debian-provided 2.6.10 for now.

> Anything else I need or just the proper kernel+3.2.e+this patch?

I think that's it...

> On Feb 23, 2005, at 1:19 PM, Jarod Wilson wrote:
> > Here's a cumulative patch against ivtv 0.3.2e, containing Jelle's
> > vsync patch,
> > Jaap's picture controls patch, Tyler's pg600/150mce patch and a tuner
> > patch
> > that *hopefully* works with the PVR-500MCE NTSC's tuner.
> >
> > Almost completely untested, since my 150 and 500 are being stupid
> > right now...

--
Jarod Wilson
jarod [at] wilsonet

ivtv-devel at universalmac

Feb 23, 2005, 11:39 PM

Post #4 of 29 (2275 views)
Permalink

Re: Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

On Feb 23, 2005, at 5:40 PM, Jarod Wilson wrote:

> On Wednesday 23 February 2005 17:06, Noah Patton wrote:
>> Jarod:
>>
>> I'll roll this out with my PVR-500MCE tonight and let you know how it
>> goes.
>
> Unfortunately, two folks have already said no go on the tuner. I'm
> hoping the
> vsync patch will at least let me be able to test mine tonight...

Make that three...no luck with the tuner, but at least I got the card
up and functioning with the no4kstacks kernel and 3.2e+patch. No color
for s-video, only static for a few seconds then black on the tuner, in
about a 3 second loop.

This computer and PVR-500MCE NTSC card are dedicated to this project,
so I'm in a good position to fearlessly test as needed. Currently up
on FC3 2.6.10_760 no4kstacks kernel. I should be able to install the
next patch more quickly now that I have things a bit more setup.

Noah

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

jim at hosemore

Feb 24, 2005, 5:51 AM

Post #5 of 29 (2277 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

On Wed, 23 Feb 2005 13:19:49 -0800
Jarod Wilson <jarod [at] wilsonet> wrote:

> Here's a cumulative patch against ivtv 0.3.2e, containing Jelle's vsync patch,
> Jaap's picture controls patch, Tyler's pg600/150mce patch and a tuner patch
> that *hopefully* works with the PVR-500MCE NTSC's tuner.
>
> Almost completely untested, since my 150 and 500 are being stupid right now...
>

It's close. On my PVR-150-NTSC, with no audiofmt parameter set, I get no tuner audio, but as always, switching to the composite input gives me line input audio mixed with tuner audio. With audiofmt=1, I get white noise on the tuner input but still get line input audio mixed with tuner audio on the composite input.

I've been here before and changing the AUD_STANDARD and AUD_MODE_AUD_SYSTEM registers will affect this. I'm going to play with it.

It does something strange if I switch it from tuner to composite and back...sounds like it sets the audio mode twice. With no RF signal applied, I can hear the de-emphasis curve change in the white noise as it goes back to the tuner input from the composite input.

There's still something wierd going on with the audio routing...by all indications we should be able to seperate the line input and tuner on the composite input and it's not working like it should. There's something wrong in the register defs IMO, but I don't have enough information to figure out exactly what it is.

-----

Jim Reese, WD5IYT jim [at] hosemore

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

ttrafford at gmail

Feb 25, 2005, 8:53 AM

Post #6 of 29 (2281 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

Does the white noise still occur after after completely resetting the
machine? (I had a similar problem, but it went away after temporarily
removing power fromt he machine.)

On Thu, 24 Feb 2005 06:51:03 -0600, James L. Reese <jim [at] hosemore> wrote:
> On Wed, 23 Feb 2005 13:19:49 -0800
> Jarod Wilson <jarod [at] wilsonet> wrote:
>
> > Here's a cumulative patch against ivtv 0.3.2e, containing Jelle's vsync patch,
> > Jaap's picture controls patch, Tyler's pg600/150mce patch and a tuner patch
> > that *hopefully* works with the PVR-500MCE NTSC's tuner.
> >
> > Almost completely untested, since my 150 and 500 are being stupid right now...
> >
>
> It's close. On my PVR-150-NTSC, with no audiofmt parameter set, I get no tuner audio, but as always, switching to the composite input gives me line input audio mixed with tuner audio. With audiofmt=1, I get white noise on the tuner input but still get line input audio mixed with tuner audio on the composite input.
>
> I've been here before and changing the AUD_STANDARD and AUD_MODE_AUD_SYSTEM registers will affect this. I'm going to play with it.
>
> It does something strange if I switch it from tuner to composite and back...sounds like it sets the audio mode twice. With no RF signal applied, I can hear the de-emphasis curve change in the white noise as it goes back to the tuner input from the composite input.
>
> There's still something wierd going on with the audio routing...by all indications we should be able to seperate the line input and tuner on the composite input and it's not working like it should. There's something wrong in the register defs IMO, but I don't have enough information to figure out exactly what it is.
>
> -----
>
> Jim Reese, WD5IYT jim [at] hosemore
>
>
> -------------------------------------------------------
> 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
> ivtv-devel [at] lists
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>

--
Tyler Trafford

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

jim at hosemore

Feb 25, 2005, 3:35 PM

Post #7 of 29 (2259 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

On Fri, 25 Feb 2005 10:53:39 -0500
Tyler Trafford <ttrafford [at] gmail> wrote:

> Does the white noise still occur after after completely resetting the
> machine? (I had a similar problem, but it went away after temporarily
> removing power fromt he machine.)
>

Yes...it did work after a power cycle.

-----

Jim Reese, WD5IYT jim [at] hosemore http://www.speakeasy.net/~jreese
********************************************************************************
Albert Einstein, when asked to describe radio, replied:
"You see, wire telegraph is a kind of a very, very long cat. You pull his tail
in New York and his head is meowing in Los Angeles. Do you understand this? And
radio operates exactly the same way: you send signals here, they receive them
there. The only difference is that there is no cat."
********************************************************************************

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

lists at forevermore

Feb 25, 2005, 4:38 PM

Post #8 of 29 (2276 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

> Here's a cumulative patch against ivtv 0.3.2e, containing Jelle's vsync patch,
> Jaap's picture controls patch, Tyler's pg600/150mce patch and a tuner patch
> that *hopefully* works with the PVR-500MCE NTSC's tuner.

I just applied these and "e" now works for me (it wouldn't without the
patches). s-video is still b&w, but composite works and I think that
the sound quality is a little better. I have no way to test the tuner.

-Chris

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

mirabeaj at aneurysm9

Feb 25, 2005, 5:09 PM

Post #9 of 29 (2240 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

Finally! Complete success with the PVR-500. Or almost complete
success. There doesn't appear to be a radio device, but both tuners are
working properly. I had to import tuner type 47 from 2.6.10-mm1 into
tuner.c from 0.3.2e. It also seems that I get tuner audio on all video
inputs, I don't have any s-vido or composite inputs to test to see if
audio from the RCA jacks are also coming in. Here's a list of the
module paramerters I'm using:

alias char-major-81 videodev
alias char-major-81-0 ivtv
alias char-major-81-1 ivtv
alias char-major-81-2 bttv
options ivtv ivtv_debug=1 ivtv_std=1,1 tuner=54,47
options cx25840 i2c_enable=1,1 debug=1 no_black_magic=1 cardtype=1 audiofmt=1

* Jarod Wilson <jarod [at] wilsonet> [2005-02-23 16:21:51]:
> Here's a cumulative patch against ivtv 0.3.2e, containing Jelle's vsync patch,
> Jaap's picture controls patch, Tyler's pg600/150mce patch and a tuner patch
> that *hopefully* works with the PVR-500MCE NTSC's tuner.
>
> Almost completely untested, since my 150 and 500 are being stupid right now...
>
> --
> Jarod Wilson
> jarod [at] wilsonet

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

ivtv-devel at universalmac

Feb 25, 2005, 5:49 PM

Post #10 of 29 (2271 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

Anthony:

Can you post a patch with the additions from 2.6.10-mm1?

You are running the 0.3.2e with the addition of Jarod's cumulative
patch from this thread, plus your import of the tuner type 47 from
2.6.10-mm1 on a non-4kstacks kernel, right?

Thanks!

Noah

On Feb 25, 2005, at 4:09 PM, Anthony J. Mirabella wrote:

> Finally! Complete success with the PVR-500. Or almost complete
> success. There doesn't appear to be a radio device, but both tuners
> are
> working properly. I had to import tuner type 47 from 2.6.10-mm1 into
> tuner.c from 0.3.2e. It also seems that I get tuner audio on all video
> inputs, I don't have any s-vido or composite inputs to test to see if
> audio from the RCA jacks are also coming in. Here's a list of the
> module paramerters I'm using:
>
> alias char-major-81 videodev
> alias char-major-81-0 ivtv
> alias char-major-81-1 ivtv
> alias char-major-81-2 bttv
> options ivtv ivtv_debug=1 ivtv_std=1,1 tuner=54,47
> options cx25840 i2c_enable=1,1 debug=1 no_black_magic=1 cardtype=1
> audiofmt=1
>
>
> * Jarod Wilson <jarod [at] wilsonet> [2005-02-23 16:21:51]:
>> Here's a cumulative patch against ivtv 0.3.2e, containing Jelle's
>> vsync patch,
>> Jaap's picture controls patch, Tyler's pg600/150mce patch and a tuner
>> patch
>> that *hopefully* works with the PVR-500MCE NTSC's tuner.
>>
>> Almost completely untested, since my 150 and 500 are being stupid
>> right now...
>>
>> --
>> Jarod Wilson
>> jarod [at] wilsonet
>
>
>
>
>
>
> -------------------------------------------------------
> 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
> ivtv-devel [at] lists
> 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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

mirabeaj at aneurysm9

Feb 25, 2005, 6:08 PM

Post #11 of 29 (2239 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

Sure, it's just a quick two-liner. You're right about the setup.

diff -aur ivtv-0.3.2e/driver/tuner.c ivtv-0.3.2e-ajm/driver/tuner.c
--- ivtv-0.3.2e/driver/tuner.c 2005-02-25 20:02:38.000000000 -0500
+++ ivtv-0.3.2e-ajm/driver/tuner.c 2005-02-25 20:03:51.000000000
-0500
@@ -232,8 +232,8 @@
16*141.00,16*464.00,0xa0,0x90,0x30,0x8e,623},
{ "NoTuner", NoTuner, NOTUNER,
0,0,0x00,0x00,0x00,0x00,0x00},
- { "NoTuner", NoTuner, NOTUNER,
- 0,0,0x00,0x00,0x00,0x00,0x00},
+ { "LG NTSC (TAPE series)", LGINNOTEK, NTSC,
+ 16*160.00,16*442.00,0x01,0x02,0x04,0x8e,732 },
{ "NoTuner", NoTuner, NOTUNER,
0,0,0x00,0x00,0x00,0x00,0x00},
{ "NoTuner", NoTuner, NOTUNER,

* Noah Patton <ivtv-devel [at] universalmac> [2005-02-25 19:53:04]:
> Anthony:
>
> Can you post a patch with the additions from 2.6.10-mm1?
>
> You are running the 0.3.2e with the addition of Jarod's cumulative
> patch from this thread, plus your import of the tuner type 47 from
> 2.6.10-mm1 on a non-4kstacks kernel, right?
>
> Thanks!
>
> Noah
>
> On Feb 25, 2005, at 4:09 PM, Anthony J. Mirabella wrote:
>
> >Finally! Complete success with the PVR-500. Or almost complete
> >success. There doesn't appear to be a radio device, but both tuners
> >are
> >working properly. I had to import tuner type 47 from 2.6.10-mm1 into
> >tuner.c from 0.3.2e. It also seems that I get tuner audio on all video
> >inputs, I don't have any s-vido or composite inputs to test to see if
> >audio from the RCA jacks are also coming in. Here's a list of the
> >module paramerters I'm using:
> >
> >alias char-major-81 videodev
> >alias char-major-81-0 ivtv
> >alias char-major-81-1 ivtv
> >alias char-major-81-2 bttv
> >options ivtv ivtv_debug=1 ivtv_std=1,1 tuner=54,47
> >options cx25840 i2c_enable=1,1 debug=1 no_black_magic=1 cardtype=1
> >audiofmt=1

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

ivtv-devel at universalmac

Feb 25, 2005, 8:56 PM

Post #12 of 29 (2277 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

Thanks, that did the trick! I've now got my tuner up and
working, I can switch through channels, sound, etc -
however, picture quality is terrible. The cable line is
good, plugged into a tv it looks great, but with the
PVR-500MCE NTSC quality is terrible. Suggestions?

Thanks!

Noah

INIT IVTV log follows - I had to snip out some parts to
make it fit on the list, let me know if I clipped
something needed...

Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv:
==================== START INIT IVTV ====================
Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: version
0.3.2 (e) loading
Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Linux
version: 2.6.10-1.760_no4kstacks 686 gcc-3.4
Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: In case of
problems please include the debug info
Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: between the
START INIT IVTV and END INIT IVTV lines when
Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: mailing the
ivtv-devel mailinglist.
Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Unknown
card: vendor/device: 4444/0016, subsystem vendor/device:
0070/e807
Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Defaulting
to WinTV PVR 150 card
Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Please mail
the vendor/device and subsystem vendor/device IDs and what
kind of
Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: card you
have to the ivtv-devel mailinglist:
http://sourceforge.net/projects/ivtv
Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Prefix your
subject line with [UNKNOWN CARD].
Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Found an
iTVC16 based chip
Feb 25 18:39:05 c-67-160-121-109 kernel: ACPI: PCI
interrupt 0000:03:08.0[A] -> GSI 3 (level, low) -> IRQ 3
Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: XXX PCI
device: 0x5833 vendor: 0x1002
Feb 25 18:39:05 c-67-160-121-109 kernel: tuner: Ignoring
new-style parameters in presence of obsolete ones
Feb 25 18:39:05 c-67-160-121-109 kernel: tuner: chip found
at addr 0xc2 i2c-bus ivtv i2c driver #0
Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: i2c attach
[client=(tuner unset),ok]
Feb 25 18:39:05 c-67-160-121-109 kernel: cx25840: Ignoring
new-style parameters in presence of obsolete ones
Feb 25 18:39:05 c-67-160-121-109 kernel: cx25840: Unable
to open FW file '/lib/modules/HcwMakoA.ROM'.
Feb 25 18:39:05 c-67-160-121-109 kernel: cx25840: Failed
to load any FW image file
Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: i2c attach
[client=cx25840[0],ok]
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Ignoring
new-style parameters in presence of obsolete ones
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Init
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: starting
probe for adapter ivtv i2c driver #0 (0x10005)
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: detecting
client on address 0x36
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[0]=2e00
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[1]=0e00
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[2]=1600
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[3]=1800
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[4]=1a00
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[5]=1c00
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[6]=1e00
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[7]=2000
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[8]=2200
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[9]=2400
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[10]=2600
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[11]=2800
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[12]=2a00
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Updating
reg[R23]=2e01 added Reset with default 1
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Updating
reg[R7]=0e00 added TOD with default 0
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Updating
reg[R11]=1600 added ADCHPD with default 0
Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Updating
reg[R11]=1600 added ADCMCLK with default 0
<SNIP>
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
reg[R21]=2a00 added MUTELA with default 0
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
reg[R21]=2a00 added MUTERA with default 0
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
reg[R21]=2a01 added AMX with default 1
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
reset.reg[0]=2e01
<SNIP>
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[12]=2a00
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
reg[R23]=2e01 added Reset with default 1
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
reg[R7]=0e00 added TOD with default 0
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
reg[R11]=1600 added ADCHPD with default 0
<SNIP>
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
reg[R21]=2a01 added AMX with default 1
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
reset.reg[0]=2e01
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
reset.reg[1]=0e00
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
reset.reg[2]=1622
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
reset.reg[3]=1802
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
reset.reg[4]=1a00
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
reset.reg[5]=1ccf
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
reset.reg[6]=1ecf
Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
reset.reg[7]=207b
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
reset.reg[8]=2200
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
reset.reg[9]=2432
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
reset.reg[10]=2600
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
reset.reg[11]=2826
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
reset.reg[12]=2a01
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
register ADCFMT (7) to 1, R11.0..1, old value 02
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
register ADCMS (8) to 1, R12.8..8, old value 00
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
register DCY (24) to 8, R18.4..7, old value 03
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
register NGAT (27) to 1, R19.0..0, old value 00
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
register LRBOTH (30) to 1, R21.8..8, old value 00
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
register AMX (33) to 15, R21.0..3, old value 01
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
register 0 (R23), config: 2e01 active: 2e00.
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
register 1 (R7), config: 0e00 active: 0e00.
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
register 2 (R11), config: 1622 active: 1621.
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
register 3 (R12), config: 1802 active: 1902.
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
register 4 (R13), config: 1a00 active: 1a00.
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
register 5 (R14), config: 1ccf active: 1ccf.
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
register 6 (R15), config: 1ecf active: 1ecf.
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
register 7 (R16), config: 207b active: 207b.
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
register 8 (R17), config: 2200 active: 2200.
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
register 9 (R18), config: 2432 active: 2482.
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
register 10 (R19), config: 2600 active: 2601.
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
register 11 (R20), config: 2826 active: 2826.
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
register 12 (R21), config: 2a01 active: 2b0f.
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: i2c attach
[client=wm8775[0],ok]
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Encoder
revision: 0x02040024
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Encoder
Firmware may be buggy, use version 0x02040011
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Configuring
WinTV PVR 150 card with 4 streams
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Create DMA
stream 0 using 256 16384 byte buffers 4194304 kbytes
total
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Registered
v4l2 device, streamtype 0 minor 0
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Create DMA
stream 1
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Registered
v4l2 device, streamtype 1 minor 32
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Create
stream 2 using 40 52224 byte buffers 2097152 kbytes total
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Registered
v4l2 device, streamtype 2 minor 224
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Create DMA
stream 3 using 455 4608 byte buffers 2097152 kbytes total
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Registered
v4l2 device, streamtype 3 minor 24
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Setting
Tuner 54
Feb 25 18:39:07 c-67-160-121-109 kernel: tuner: type set
to 54 (Philips FQ1236A MK4) by ivtv i2c driver #0
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv:
ivtv_enc_thread: pid = 5485, itv = 0xe1342aa0
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Switching
standard to NTSC.
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Initialized
WinTV PVR 150, card #0
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Unknown
card: vendor/device: 4444/0016, subsystem vendor/device:
0070/e817
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Defaulting
to WinTV PVR 150 card
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Please mail
the vendor/device and subsystem vendor/device IDs and what
kind of
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: card you
have to the ivtv-devel mailinglist:
http://sourceforge.net/projects/ivtv
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Prefix your
subject line with [UNKNOWN CARD].
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Found an
iTVC16 based chip
Feb 25 18:39:07 c-67-160-121-109 kernel: ACPI: PCI
interrupt 0000:03:09.0[A] -> GSI 5 (level, low) -> IRQ 5
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: XXX PCI
device: 0x5833 vendor: 0x1002
Feb 25 18:39:07 c-67-160-121-109 kernel: tuner: chip found
at addr 0xc2 i2c-bus ivtv i2c driver #1
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: i2c attach
[client=(tuner unset),ok]
Feb 25 18:39:07 c-67-160-121-109 kernel: cx25840: Unable
to open FW file '/lib/modules/HcwMakoA.ROM'.
Feb 25 18:39:07 c-67-160-121-109 kernel: cx25840: Failed
to load any FW image file
Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: i2c attach
[client=cx25840[1],ok]
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: starting
probe for adapter ivtv i2c driver #1 (0x10005)
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: detecting
client on address 0x36
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[0]=2e00
<SNIP>
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[12]=2a00
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
reg[R23]=2e01 added Reset with default 1
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
reg[R7]=0e00 added TOD with default 0
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
reg[R11]=1600 added ADCHPD with default 0
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
reg[R11]=1600 added ADCMCLK with default 0
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
reg[R11]=1620 added ADCWL with default 2
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
reg[R11]=1620 added ADCBCP with default 0
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
reg[R11]=1620 added ADCLRP with default 0
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
reg[R11]=1622 added ADCFMT with default 2
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
reg[R12]=1800 added ADCMS with default 0
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
reg[R12]=1800 added ADCOSR with default 0
Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
reg[R12]=1802 added ADCRATE with default 2
<SNIP>
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
reg[R21]=2a01 added AMX with default 1
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Final
reset.reg[0]=2e01
<SNIP>
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Offset
reset.reg[12]=2a00
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
reg[R23]=2e01 added Reset with default 1
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
reg[R7]=0e00 added TOD with default 0
<SNIP>
MUTERA with default 0
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
reg[R21]=2a01 added AMX with default 1
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Final
reset.reg[0]=2e01
<SNIP>
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Final
reset.reg[12]=2a01
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
register ADCFMT (7) to 1, R11.0..1, old value 02
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
register ADCMS (8) to 1, R12.8..8, old value 00
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
register DCY (24) to 8, R18.4..7, old value 03
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
register NGAT (27) to 1, R19.0..0, old value 00
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
register LRBOTH (30) to 1, R21.8..8, old value 00
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
register AMX (33) to 15, R21.0..3, old value 01
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
register 0 (R23), config: 2e01 active: 2e00.
<SNIP>
2826 active: 2826.
Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
register 12 (R21), config: 2a01 active: 2b0f.
Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: i2c attach
[client=wm8775[1],ok]
Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Encoder
revision: 0x02040024
Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Encoder
Firmware may be buggy, use version 0x02040011
Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Configuring
WinTV PVR 150 card with 4 streams
Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Create DMA
stream 0 using 256 16384 byte buffers 4194304 kbytes
total
Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Registered
v4l2 device, streamtype 0 minor 1
Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Create DMA
stream 1
Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Registered
v4l2 device, streamtype 1 minor 33
Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Create
stream 2 using 40 52224 byte buffers 2097152 kbytes total
Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Registered
v4l2 device, streamtype 2 minor 225
Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Create DMA
stream 3 using 455 4608 byte buffers 2097152 kbytes total
Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Registered
v4l2 device, streamtype 3 minor 25
Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Setting
Tuner 47
Feb 25 18:39:09 c-67-160-121-109 kernel: tuner: type set
to 47 (NoTuner) by ivtv i2c driver #1
Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Switching
standard to NTSC.
Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Initialized
WinTV PVR 150, card #1
Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv:
==================== END INIT IVTV ====================

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

ivtv-devel at universalmac

Feb 25, 2005, 9:06 PM

Post #13 of 29 (2277 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

Nevermind, reworked the cable routing and things are now
fine. Man, this thing is sensitive! Have it direct first
device now, though, and picture looks great.

Thanks everyone for the great assistance in making this
all work!

Noah

On Fri, 25 Feb 2005 19:56:56 -0800
"Noah Patton" <ivtv-devel [at] universalmac> wrote:
> Thanks, that did the trick! I've now got my tuner up
>and working, I can switch through channels, sound, etc -
>however, picture quality is terrible. The cable line is
>good, plugged into a tv it looks great, but with the
>PVR-500MCE NTSC quality is terrible. Suggestions?
>
> Thanks!
>
> Noah
>
> INIT IVTV log follows - I had to snip out some parts to
>make it fit on the list, let me know if I clipped
>something needed...
>
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv:
>==================== START INIT IVTV ====================
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: version
>0.3.2 (e) loading
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Linux
>version: 2.6.10-1.760_no4kstacks 686 gcc-3.4
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: In case of
>problems please include the debug info
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: between
>the START INIT IVTV and END INIT IVTV lines when
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: mailing
>the ivtv-devel mailinglist.
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Unknown
>card: vendor/device: 4444/0016, subsystem vendor/device:
>0070/e807
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Defaulting
>to WinTV PVR 150 card
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Please
>mail the vendor/device and subsystem vendor/device IDs
>and what kind of
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: card you
>have to the ivtv-devel mailinglist:
>http://sourceforge.net/projects/ivtv
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Prefix
>your subject line with [UNKNOWN CARD].
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Found an
>iTVC16 based chip
>Feb 25 18:39:05 c-67-160-121-109 kernel: ACPI: PCI
>interrupt 0000:03:08.0[A] -> GSI 3 (level, low) -> IRQ 3
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: XXX PCI
>device: 0x5833 vendor: 0x1002
>Feb 25 18:39:05 c-67-160-121-109 kernel: tuner: Ignoring
>new-style parameters in presence of obsolete ones
>Feb 25 18:39:05 c-67-160-121-109 kernel: tuner: chip
>found at addr 0xc2 i2c-bus ivtv i2c driver #0
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: i2c attach
>[client=(tuner unset),ok]
>Feb 25 18:39:05 c-67-160-121-109 kernel: cx25840:
>Ignoring new-style parameters in presence of obsolete
>ones
>Feb 25 18:39:05 c-67-160-121-109 kernel: cx25840: Unable
>to open FW file '/lib/modules/HcwMakoA.ROM'.
>Feb 25 18:39:05 c-67-160-121-109 kernel: cx25840: Failed
>to load any FW image file
>Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: i2c attach
>[client=cx25840[0],ok]
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Ignoring
>new-style parameters in presence of obsolete ones
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Init
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: starting
>probe for adapter ivtv i2c driver #0 (0x10005)
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775:
>detecting client on address 0x36
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[0]=2e00
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[1]=0e00
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[2]=1600
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[3]=1800
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[4]=1a00
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[5]=1c00
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[6]=1e00
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[7]=2000
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[8]=2200
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[9]=2400
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[10]=2600
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[11]=2800
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[12]=2a00
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Updating
>reg[R23]=2e01 added Reset with default 1
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Updating
>reg[R7]=0e00 added TOD with default 0
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Updating
>reg[R11]=1600 added ADCHPD with default 0
>Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Updating
>reg[R11]=1600 added ADCMCLK with default 0
> <SNIP>
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
>reg[R21]=2a00 added MUTELA with default 0
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
>reg[R21]=2a00 added MUTERA with default 0
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
>reg[R21]=2a01 added AMX with default 1
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[0]=2e01
> <SNIP>
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[12]=2a00
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
>reg[R23]=2e01 added Reset with default 1
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
>reg[R7]=0e00 added TOD with default 0
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
>reg[R11]=1600 added ADCHPD with default 0
> <SNIP>
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
>reg[R21]=2a01 added AMX with default 1
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[0]=2e01
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[1]=0e00
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[2]=1622
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[3]=1802
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[4]=1a00
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[5]=1ccf
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[6]=1ecf
>Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[7]=207b
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[8]=2200
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[9]=2432
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[10]=2600
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[11]=2826
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[12]=2a01
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
>register ADCFMT (7) to 1, R11.0..1, old value 02
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
>register ADCMS (8) to 1, R12.8..8, old value 00
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
>register DCY (24) to 8, R18.4..7, old value 03
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
>register NGAT (27) to 1, R19.0..0, old value 00
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
>register LRBOTH (30) to 1, R21.8..8, old value 00
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
>register AMX (33) to 15, R21.0..3, old value 01
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>register 0 (R23), config: 2e01 active: 2e00.
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
>register 1 (R7), config: 0e00 active: 0e00.
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>register 2 (R11), config: 1622 active: 1621.
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>register 3 (R12), config: 1802 active: 1902.
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
>register 4 (R13), config: 1a00 active: 1a00.
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
>register 5 (R14), config: 1ccf active: 1ccf.
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
>register 6 (R15), config: 1ecf active: 1ecf.
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
>register 7 (R16), config: 207b active: 207b.
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
>register 8 (R17), config: 2200 active: 2200.
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>register 9 (R18), config: 2432 active: 2482.
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>register 10 (R19), config: 2600 active: 2601.
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
>register 11 (R20), config: 2826 active: 2826.
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>register 12 (R21), config: 2a01 active: 2b0f.
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: i2c attach
>[client=wm8775[0],ok]
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Encoder
>revision: 0x02040024
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Encoder
>Firmware may be buggy, use version 0x02040011
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv:
>Configuring WinTV PVR 150 card with 4 streams
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Create DMA
>stream 0 using 256 16384 byte buffers 4194304 kbytes
>total
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Registered
>v4l2 device, streamtype 0 minor 0
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Create DMA
>stream 1
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Registered
>v4l2 device, streamtype 1 minor 32
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Create
>stream 2 using 40 52224 byte buffers 2097152 kbytes
>total
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Registered
>v4l2 device, streamtype 2 minor 224
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Create DMA
>stream 3 using 455 4608 byte buffers 2097152 kbytes
>total
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Registered
>v4l2 device, streamtype 3 minor 24
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Setting
>Tuner 54
>Feb 25 18:39:07 c-67-160-121-109 kernel: tuner: type set
>to 54 (Philips FQ1236A MK4) by ivtv i2c driver #0
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv:
>ivtv_enc_thread: pid = 5485, itv = 0xe1342aa0
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Switching
>standard to NTSC.
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv:
>Initialized WinTV PVR 150, card #0
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Unknown
>card: vendor/device: 4444/0016, subsystem vendor/device:
>0070/e817
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Defaulting
>to WinTV PVR 150 card
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Please
>mail the vendor/device and subsystem vendor/device IDs
>and what kind of
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: card you
>have to the ivtv-devel mailinglist:
>http://sourceforge.net/projects/ivtv
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Prefix
>your subject line with [UNKNOWN CARD].
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Found an
>iTVC16 based chip
>Feb 25 18:39:07 c-67-160-121-109 kernel: ACPI: PCI
>interrupt 0000:03:09.0[A] -> GSI 5 (level, low) -> IRQ 5
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: XXX PCI
>device: 0x5833 vendor: 0x1002
>Feb 25 18:39:07 c-67-160-121-109 kernel: tuner: chip
>found at addr 0xc2 i2c-bus ivtv i2c driver #1
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: i2c attach
>[client=(tuner unset),ok]
>Feb 25 18:39:07 c-67-160-121-109 kernel: cx25840: Unable
>to open FW file '/lib/modules/HcwMakoA.ROM'.
>Feb 25 18:39:07 c-67-160-121-109 kernel: cx25840: Failed
>to load any FW image file
>Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: i2c attach
>[client=cx25840[1],ok]
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: starting
>probe for adapter ivtv i2c driver #1 (0x10005)
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775:
>detecting client on address 0x36
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[0]=2e00
> <SNIP>
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[12]=2a00
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>reg[R23]=2e01 added Reset with default 1
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>reg[R7]=0e00 added TOD with default 0
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>reg[R11]=1600 added ADCHPD with default 0
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>reg[R11]=1600 added ADCMCLK with default 0
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>reg[R11]=1620 added ADCWL with default 2
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>reg[R11]=1620 added ADCBCP with default 0
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>reg[R11]=1620 added ADCLRP with default 0
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>reg[R11]=1622 added ADCFMT with default 2
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>reg[R12]=1800 added ADCMS with default 0
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>reg[R12]=1800 added ADCOSR with default 0
>Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
>reg[R12]=1802 added ADCRATE with default 2
> <SNIP>
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
>reg[R21]=2a01 added AMX with default 1
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[0]=2e01
> <SNIP>
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Offset
>reset.reg[12]=2a00
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
>reg[R23]=2e01 added Reset with default 1
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
>reg[R7]=0e00 added TOD with default 0
> <SNIP>
> MUTERA with default 0
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
>reg[R21]=2a01 added AMX with default 1
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[0]=2e01
> <SNIP>
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Final
>reset.reg[12]=2a01
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
>register ADCFMT (7) to 1, R11.0..1, old value 02
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
>register ADCMS (8) to 1, R12.8..8, old value 00
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
>register DCY (24) to 8, R18.4..7, old value 03
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
>register NGAT (27) to 1, R19.0..0, old value 00
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
>register LRBOTH (30) to 1, R21.8..8, old value 00
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
>register AMX (33) to 15, R21.0..3, old value 01
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
>register 0 (R23), config: 2e01 active: 2e00.
> <SNIP>
> 2826 active: 2826.
>Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
>register 12 (R21), config: 2a01 active: 2b0f.
>Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: i2c attach
>[client=wm8775[1],ok]
>Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Encoder
>revision: 0x02040024
>Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Encoder
>Firmware may be buggy, use version 0x02040011
>Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv:
>Configuring WinTV PVR 150 card with 4 streams
>Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Create DMA
>stream 0 using 256 16384 byte buffers 4194304 kbytes
>total
>Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Registered
>v4l2 device, streamtype 0 minor 1
>Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Create DMA
>stream 1
>Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Registered
>v4l2 device, streamtype 1 minor 33
>Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Create
>stream 2 using 40 52224 byte buffers 2097152 kbytes
>total
>Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Registered
>v4l2 device, streamtype 2 minor 225
>Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Create DMA
>stream 3 using 455 4608 byte buffers 2097152 kbytes
>total
>Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Registered
>v4l2 device, streamtype 3 minor 25
>Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Setting
>Tuner 47
>Feb 25 18:39:09 c-67-160-121-109 kernel: tuner: type set
>to 47 (NoTuner) by ivtv i2c driver #1
>Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Switching
>standard to NTSC.
>Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv:
>Initialized WinTV PVR 150, card #1
>Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv:
>==================== END INIT IVTV ====================
>
>
> -------------------------------------------------------
> 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
> ivtv-devel [at] lists
> 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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

mirabeaj at aneurysm9

Feb 25, 2005, 9:24 PM

Post #14 of 29 (2278 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

It seems that type 47 is still being reported as NoTuner. Which device
did you get poor video on, video0 or video1? I got poor UHF reception
with type 50 on video0 and type 39 on video1, perhaps you have one of
those tuners.

* Noah Patton <ivtv-devel [at] universalmac> [2005-02-25 23:01:25]:
> Thanks, that did the trick! I've now got my tuner up and
> working, I can switch through channels, sound, etc -
> however, picture quality is terrible. The cable line is
> good, plugged into a tv it looks great, but with the
> PVR-500MCE NTSC quality is terrible. Suggestions?
>
> Thanks!
>
> Noah
>
> INIT IVTV log follows - I had to snip out some parts to
> make it fit on the list, let me know if I clipped
> something needed...
>
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv:
> ==================== START INIT IVTV ====================
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: version
> 0.3.2 (e) loading
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Linux
> version: 2.6.10-1.760_no4kstacks 686 gcc-3.4
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: In case of
> problems please include the debug info
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: between the
> START INIT IVTV and END INIT IVTV lines when
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: mailing the
> ivtv-devel mailinglist.
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Unknown
> card: vendor/device: 4444/0016, subsystem vendor/device:
> 0070/e807
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Defaulting
> to WinTV PVR 150 card
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Please mail
> the vendor/device and subsystem vendor/device IDs and what
> kind of
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: card you
> have to the ivtv-devel mailinglist:
> http://sourceforge.net/projects/ivtv
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Prefix your
> subject line with [UNKNOWN CARD].
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: Found an
> iTVC16 based chip
> Feb 25 18:39:05 c-67-160-121-109 kernel: ACPI: PCI
> interrupt 0000:03:08.0[A] -> GSI 3 (level, low) -> IRQ 3
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: XXX PCI
> device: 0x5833 vendor: 0x1002
> Feb 25 18:39:05 c-67-160-121-109 kernel: tuner: Ignoring
> new-style parameters in presence of obsolete ones
> Feb 25 18:39:05 c-67-160-121-109 kernel: tuner: chip found
> at addr 0xc2 i2c-bus ivtv i2c driver #0
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: i2c attach
> [client=(tuner unset),ok]
> Feb 25 18:39:05 c-67-160-121-109 kernel: cx25840: Ignoring
> new-style parameters in presence of obsolete ones
> Feb 25 18:39:05 c-67-160-121-109 kernel: cx25840: Unable
> to open FW file '/lib/modules/HcwMakoA.ROM'.
> Feb 25 18:39:05 c-67-160-121-109 kernel: cx25840: Failed
> to load any FW image file
> Feb 25 18:39:05 c-67-160-121-109 kernel: ivtv: i2c attach
> [client=cx25840[0],ok]
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Ignoring
> new-style parameters in presence of obsolete ones
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Init
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: starting
> probe for adapter ivtv i2c driver #0 (0x10005)
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: detecting
> client on address 0x36
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[0]=2e00
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[1]=0e00
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[2]=1600
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[3]=1800
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[4]=1a00
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[5]=1c00
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[6]=1e00
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[7]=2000
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[8]=2200
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[9]=2400
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[10]=2600
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[11]=2800
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[12]=2a00
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Updating
> reg[R23]=2e01 added Reset with default 1
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Updating
> reg[R7]=0e00 added TOD with default 0
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Updating
> reg[R11]=1600 added ADCHPD with default 0
> Feb 25 18:39:05 c-67-160-121-109 kernel: wm8775: Updating
> reg[R11]=1600 added ADCMCLK with default 0
> <SNIP>
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
> reg[R21]=2a00 added MUTELA with default 0
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
> reg[R21]=2a00 added MUTERA with default 0
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
> reg[R21]=2a01 added AMX with default 1
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[0]=2e01
> <SNIP>
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[12]=2a00
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
> reg[R23]=2e01 added Reset with default 1
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
> reg[R7]=0e00 added TOD with default 0
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
> reg[R11]=1600 added ADCHPD with default 0
> <SNIP>
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Updating
> reg[R21]=2a01 added AMX with default 1
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[0]=2e01
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[1]=0e00
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[2]=1622
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[3]=1802
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[4]=1a00
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[5]=1ccf
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[6]=1ecf
> Feb 25 18:39:06 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[7]=207b
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[8]=2200
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[9]=2432
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[10]=2600
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[11]=2826
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[12]=2a01
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
> register ADCFMT (7) to 1, R11.0..1, old value 02
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
> register ADCMS (8) to 1, R12.8..8, old value 00
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
> register DCY (24) to 8, R18.4..7, old value 03
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
> register NGAT (27) to 1, R19.0..0, old value 00
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
> register LRBOTH (30) to 1, R21.8..8, old value 00
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Setting
> register AMX (33) to 15, R21.0..3, old value 01
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> register 0 (R23), config: 2e01 active: 2e00.
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
> register 1 (R7), config: 0e00 active: 0e00.
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> register 2 (R11), config: 1622 active: 1621.
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> register 3 (R12), config: 1802 active: 1902.
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
> register 4 (R13), config: 1a00 active: 1a00.
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
> register 5 (R14), config: 1ccf active: 1ccf.
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
> register 6 (R15), config: 1ecf active: 1ecf.
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
> register 7 (R16), config: 207b active: 207b.
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
> register 8 (R17), config: 2200 active: 2200.
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> register 9 (R18), config: 2432 active: 2482.
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> register 10 (R19), config: 2600 active: 2601.
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Skipping
> register 11 (R20), config: 2826 active: 2826.
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> register 12 (R21), config: 2a01 active: 2b0f.
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: i2c attach
> [client=wm8775[0],ok]
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Encoder
> revision: 0x02040024
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Encoder
> Firmware may be buggy, use version 0x02040011
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Configuring
> WinTV PVR 150 card with 4 streams
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Create DMA
> stream 0 using 256 16384 byte buffers 4194304 kbytes
> total
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Registered
> v4l2 device, streamtype 0 minor 0
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Create DMA
> stream 1
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Registered
> v4l2 device, streamtype 1 minor 32
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Create
> stream 2 using 40 52224 byte buffers 2097152 kbytes total
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Registered
> v4l2 device, streamtype 2 minor 224
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Create DMA
> stream 3 using 455 4608 byte buffers 2097152 kbytes total
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Registered
> v4l2 device, streamtype 3 minor 24
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Setting
> Tuner 54
> Feb 25 18:39:07 c-67-160-121-109 kernel: tuner: type set
> to 54 (Philips FQ1236A MK4) by ivtv i2c driver #0
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv:
> ivtv_enc_thread: pid = 5485, itv = 0xe1342aa0
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Switching
> standard to NTSC.
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Initialized
> WinTV PVR 150, card #0
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Unknown
> card: vendor/device: 4444/0016, subsystem vendor/device:
> 0070/e817
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Defaulting
> to WinTV PVR 150 card
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Please mail
> the vendor/device and subsystem vendor/device IDs and what
> kind of
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: card you
> have to the ivtv-devel mailinglist:
> http://sourceforge.net/projects/ivtv
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Prefix your
> subject line with [UNKNOWN CARD].
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: Found an
> iTVC16 based chip
> Feb 25 18:39:07 c-67-160-121-109 kernel: ACPI: PCI
> interrupt 0000:03:09.0[A] -> GSI 5 (level, low) -> IRQ 5
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: XXX PCI
> device: 0x5833 vendor: 0x1002
> Feb 25 18:39:07 c-67-160-121-109 kernel: tuner: chip found
> at addr 0xc2 i2c-bus ivtv i2c driver #1
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: i2c attach
> [client=(tuner unset),ok]
> Feb 25 18:39:07 c-67-160-121-109 kernel: cx25840: Unable
> to open FW file '/lib/modules/HcwMakoA.ROM'.
> Feb 25 18:39:07 c-67-160-121-109 kernel: cx25840: Failed
> to load any FW image file
> Feb 25 18:39:07 c-67-160-121-109 kernel: ivtv: i2c attach
> [client=cx25840[1],ok]
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: starting
> probe for adapter ivtv i2c driver #1 (0x10005)
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: detecting
> client on address 0x36
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[0]=2e00
> <SNIP>
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[12]=2a00
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> reg[R23]=2e01 added Reset with default 1
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> reg[R7]=0e00 added TOD with default 0
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> reg[R11]=1600 added ADCHPD with default 0
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> reg[R11]=1600 added ADCMCLK with default 0
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> reg[R11]=1620 added ADCWL with default 2
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> reg[R11]=1620 added ADCBCP with default 0
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> reg[R11]=1620 added ADCLRP with default 0
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> reg[R11]=1622 added ADCFMT with default 2
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> reg[R12]=1800 added ADCMS with default 0
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> reg[R12]=1800 added ADCOSR with default 0
> Feb 25 18:39:07 c-67-160-121-109 kernel: wm8775: Updating
> reg[R12]=1802 added ADCRATE with default 2
> <SNIP>
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
> reg[R21]=2a01 added AMX with default 1
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[0]=2e01
> <SNIP>
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Offset
> reset.reg[12]=2a00
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
> reg[R23]=2e01 added Reset with default 1
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
> reg[R7]=0e00 added TOD with default 0
> <SNIP>
> MUTERA with default 0
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
> reg[R21]=2a01 added AMX with default 1
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[0]=2e01
> <SNIP>
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Final
> reset.reg[12]=2a01
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
> register ADCFMT (7) to 1, R11.0..1, old value 02
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
> register ADCMS (8) to 1, R12.8..8, old value 00
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
> register DCY (24) to 8, R18.4..7, old value 03
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
> register NGAT (27) to 1, R19.0..0, old value 00
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
> register LRBOTH (30) to 1, R21.8..8, old value 00
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Setting
> register AMX (33) to 15, R21.0..3, old value 01
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
> register 0 (R23), config: 2e01 active: 2e00.
> <SNIP>
> 2826 active: 2826.
> Feb 25 18:39:08 c-67-160-121-109 kernel: wm8775: Updating
> register 12 (R21), config: 2a01 active: 2b0f.
> Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: i2c attach
> [client=wm8775[1],ok]
> Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Encoder
> revision: 0x02040024
> Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Encoder
> Firmware may be buggy, use version 0x02040011
> Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Configuring
> WinTV PVR 150 card with 4 streams
> Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Create DMA
> stream 0 using 256 16384 byte buffers 4194304 kbytes
> total
> Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Registered
> v4l2 device, streamtype 0 minor 1
> Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Create DMA
> stream 1
> Feb 25 18:39:08 c-67-160-121-109 kernel: ivtv: Registered
> v4l2 device, streamtype 1 minor 33
> Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Create
> stream 2 using 40 52224 byte buffers 2097152 kbytes total
> Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Registered
> v4l2 device, streamtype 2 minor 225
> Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Create DMA
> stream 3 using 455 4608 byte buffers 2097152 kbytes total
> Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Registered
> v4l2 device, streamtype 3 minor 25
> Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Setting
> Tuner 47
> Feb 25 18:39:09 c-67-160-121-109 kernel: tuner: type set
> to 47 (NoTuner) by ivtv i2c driver #1
> Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Switching
> standard to NTSC.
> Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv: Initialized
> WinTV PVR 150, card #1
> Feb 25 18:39:09 c-67-160-121-109 kernel: ivtv:
> ==================== END INIT IVTV ====================
>
>
> -------------------------------------------------------
> 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
> ivtv-devel [at] lists
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>

jim at hosemore

Feb 26, 2005, 3:59 AM

Post #15 of 29 (2275 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

On Fri, 25 Feb 2005 15:38:22 -0800
Chris Petersen <lists [at] forevermore> wrote:

> > Here's a cumulative patch against ivtv 0.3.2e, containing Jelle's vsync patch,
> > Jaap's picture controls patch, Tyler's pg600/150mce patch and a tuner patch
> > that *hopefully* works with the PVR-500MCE NTSC's tuner.
>
> I just applied these and "e" now works for me (it wouldn't without the
> patches). s-video is still b&w, but composite works and I think that
> the sound quality is a little better. I have no way to test the tuner.
>
> -Chris

Does your composite work without both tuner and line audio at the same time? Mine still has both tuner and composite audio mixed on input 2.

-----

Jim Reese, WD5IYT jim [at] hosemore

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

knisleyjw at yahoo

Feb 26, 2005, 7:00 AM

Post #16 of 29 (2280 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

Well, I should've moved up to e with the patches and
now feel like an ass because tuner=54,54 (the FQ1236A
MK4 def therein) works now that I'm using e. I'm not
sure what's different as I haven't sifted through the
code, but woo.

Back a bit, someone suggested using type 47,54, which
doesn't work at all for me. Type 54 on both works and
I'm able to change channels on video0/tuner0. I get a
beautiful picture on video1 (with t47 I got a big mass
of red), but I can't change the channel. I've tried
tuner0/1 of video 1 and tuner1 of video0 and I don't
get anything.

I haven't tested the sound, yet, but I remember that
when I was using d, I got composite sound, and then
static on the tuner, but they were never mixed when I
flipped back to composite.

Thanks for all the hard work. I suppose the tuner
settings were right there under my nose, I just didn't
realize how concretely necessary the patch was and
it's yet another learning experience I won't soon
forget. :)

Jason

--- "James L. Reese" <jim [at] hosemore> wrote:

> On Fri, 25 Feb 2005 15:38:22 -0800
> Chris Petersen <lists [at] forevermore> wrote:
>
> > > Here's a cumulative patch against ivtv 0.3.2e,
> containing Jelle's vsync patch,
> > > Jaap's picture controls patch, Tyler's
> pg600/150mce patch and a tuner patch
> > > that *hopefully* works with the PVR-500MCE
> NTSC's tuner.
> >
> > I just applied these and "e" now works for me (it
> wouldn't without the
> > patches). s-video is still b&w, but composite
> works and I think that
> > the sound quality is a little better. I have no
> way to test the tuner.
> >
> > -Chris
>

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

ivtv-devel at universalmac

Feb 26, 2005, 11:25 AM

Post #17 of 29 (2267 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

Jason:

I had the same problem that I could only change channels using ptune-ui
on video0/tuner0, but not video1 with either tuner.

However, I fired up MythTV and don't have any difficulty changing
channels on both video0 and video1, and recording shows works normally
changing the channels, etc.

I figured that either I was doing something wrong with ptune-ui or it
simply wasn't configured right or needed to be updated to work with the
new tuner.

In any case, this was fine with me as the end purpose for me is MythTV
anyways, so I'm happy!

Noah

On Feb 26, 2005, at 6:00 AM, Jason Knisley wrote:

> Well, I should've moved up to e with the patches and
> now feel like an ass because tuner=54,54 (the FQ1236A
> MK4 def therein) works now that I'm using e. I'm not
> sure what's different as I haven't sifted through the
> code, but woo.
>
> Back a bit, someone suggested using type 47,54, which
> doesn't work at all for me. Type 54 on both works and
> I'm able to change channels on video0/tuner0. I get a
> beautiful picture on video1 (with t47 I got a big mass
> of red), but I can't change the channel. I've tried
> tuner0/1 of video 1 and tuner1 of video0 and I don't
> get anything.
>
> I haven't tested the sound, yet, but I remember that
> when I was using d, I got composite sound, and then
> static on the tuner, but they were never mixed when I
> flipped back to composite.
>
> Thanks for all the hard work. I suppose the tuner
> settings were right there under my nose, I just didn't
> realize how concretely necessary the patch was and
> it's yet another learning experience I won't soon
> forget. :)
>
> Jason
>
> --- "James L. Reese" <jim [at] hosemore> wrote:
>
>> On Fri, 25 Feb 2005 15:38:22 -0800
>> Chris Petersen <lists [at] forevermore> wrote:
>>
>>>> Here's a cumulative patch against ivtv 0.3.2e,
>> containing Jelle's vsync patch,
>>>> Jaap's picture controls patch, Tyler's
>> pg600/150mce patch and a tuner patch
>>>> that *hopefully* works with the PVR-500MCE
>> NTSC's tuner.
>>>
>>> I just applied these and "e" now works for me (it
>> wouldn't without the
>>> patches). s-video is still b&w, but composite
>> works and I think that
>>> the sound quality is a little better. I have no
>> way to test the tuner.
>>>
>>> -Chris
>>
>
>
>
> -------------------------------------------------------
> 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
> ivtv-devel [at] lists
> 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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

lists at forevermore

Feb 26, 2005, 12:17 PM

Post #18 of 29 (2245 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

> Does your composite work without both tuner and line audio at the same time? Mine still has both tuner and composite audio mixed on input 2.

I don't have anything to plug into the tuner, but I don't hear any
static or anything like that.

-Chris

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

jarod at wilsonet

Feb 26, 2005, 4:38 PM

Post #19 of 29 (2275 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

On Friday 25 February 2005 20:24, Anthony J. Mirabella wrote:
> It seems that type 47 is still being reported as NoTuner. Which device
> did you get poor video on, video0 or video1? I got poor UHF reception
> with type 50 on video0 and type 39 on video1, perhaps you have one of
> those tuners.

I screwed something up in that cumulative patch referenced in the title of
this thread, causing all defs after 45 to be off by one, so 47 getting
reported as NoTuner is because its proper def is sitting in slot 46.

> * Noah Patton <ivtv-devel [at] universalmac> [2005-02-25 23:01:25]:
> > Thanks, that did the trick! I've now got my tuner up and
> > working, I can switch through channels, sound, etc -
> > however, picture quality is terrible. The cable line is
> > good, plugged into a tv it looks great, but with the
> > PVR-500MCE NTSC quality is terrible. Suggestions?

And on the 500, what should have been type 55 is sitting in slot 54, thus the
apparent reports of people getting it working with type 54, which is actually
supposed to be the FQ1286 NTSC-J tuner. I'm about to play with my own 500
some more and a proper patch, to see if I've finally got video with type
55...

--
Jarod Wilson
jarod [at] wilsonet

knisleyjw at yahoo

Feb 26, 2005, 5:23 PM

Post #20 of 29 (2282 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

Actually, I'm using the correct FQ1236A MK4. I'm using
the patched kernel, but it seems to be working
correctly and showing "FQ1236A MK4" in messages when I
use tuner=54,54.

I'm also getting tuner sound mixed in with the
composite sound. When using 0.3.2d, I got rather
severe static on the tuner, of course, which wasn't
present when I used the composite input. So something
recent is causing trouble? I'll test 0.3.2e later with
just the tuner patch.

Jason

--- Jarod Wilson <jarod [at] wilsonet> wrote:

> On Friday 25 February 2005 20:24, Anthony J.
> Mirabella wrote:
> > It seems that type 47 is still being reported as
> NoTuner. Which device
> > did you get poor video on, video0 or video1? I
> got poor UHF reception
> > with type 50 on video0 and type 39 on video1,
> perhaps you have one of
> > those tuners.
>
> I screwed something up in that cumulative patch
> referenced in the title of
> this thread, causing all defs after 45 to be off by
> one, so 47 getting
> reported as NoTuner is because its proper def is
> sitting in slot 46.
>
>
> > * Noah Patton <ivtv-devel [at] universalmac>
> [2005-02-25 23:01:25]:
> > > Thanks, that did the trick! I've now got my
> tuner up and
> > > working, I can switch through channels, sound,
> etc -
> > > however, picture quality is terrible. The cable
> line is
> > > good, plugged into a tv it looks great, but with
> the
> > > PVR-500MCE NTSC quality is terrible.
> Suggestions?
>
> And on the 500, what should have been type 55 is
> sitting in slot 54, thus the
> apparent reports of people getting it working with
> type 54, which is actually
> supposed to be the FQ1286 NTSC-J tuner. I'm about to
> play with my own 500
> some more and a proper patch, to see if I've finally
> got video with type
> 55...
>
> --
> Jarod Wilson
> jarod [at] wilsonet
>

> ATTACHMENT part 2 application/pgp-signature

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

ttrafford at gmail

Feb 26, 2005, 5:31 PM

Post #21 of 29 (2267 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

On Sat, 26 Feb 2005 16:23:45 -0800 (PST), Jason Knisley
<knisleyjw [at] yahoo> wrote:
> Actually, I'm using the correct FQ1236A MK4. I'm using
> the patched kernel, but it seems to be working
> correctly and showing "FQ1236A MK4" in messages when I
> use tuner=54,54.
>
> I'm also getting tuner sound mixed in with the
> composite sound. When using 0.3.2d, I got rather
> severe static on the tuner, of course, which wasn't
> present when I used the composite input. So something
> recent is causing trouble? I'll test 0.3.2e later with
> just the tuner patch.

Everyone has had that particular problem since the inception of the
cx25840 driver. That and the b&w s-video.
--
Tyler Trafford

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

jarod at wilsonet

Feb 26, 2005, 10:15 PM

Post #22 of 29 (2243 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

On Saturday 26 February 2005 16:23, Jason Knisley wrote:
> Actually, I'm using the correct FQ1236A MK4. I'm using
> the patched kernel, but it seems to be working
> correctly and showing "FQ1236A MK4" in messages when I
> use tuner=54,54.

Ah, I presume you patched the kernel tuner module, but aren't using the very
latest kraxel patch. In the latest kraxel patch, type 54 is a Philips FQ1286,
upon which the FQ1236A MK4 defs are based. For simplicity of rebuilding and
testing, I've been using the ivtv tuner module, and made the 1236A line up
with where it'd be if the patch got to Gerd before much longer. I plan to
whip up some patches for him tomorrow...

> I'm also getting tuner sound mixed in with the
> composite sound. When using 0.3.2d, I got rather
> severe static on the tuner, of course, which wasn't
> present when I used the composite input. So something
> recent is causing trouble? I'll test 0.3.2e later with
> just the tuner patch.

Haven't tried anything but tuner yet myself. I don't have any svid or
composite sources I care to use -- I'm yanking video off my cable box via
FireWire now. :-)

--
Jarod Wilson
jarod [at] wilsonet

knisleyjw at yahoo

Feb 26, 2005, 10:48 PM

Post #23 of 29 (2289 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

At the risk of sounding stupid, I didn't. With 0.3.2d,
I didn't have the tuner static mixed into the
composite input's video. Is this because the tuner
couldn't be controlled properly until recently, or is
this something with the cx25840 recently?

I had absolutely perfect composite video and audio
that I could've recorded off of. I don't really care
hugely about the composite in right now, but it, as
the FM tuner, would be nice icing to have.

Thanks,
Jason

> Everyone has had that particular problem since the
> inception of the
> cx25840 driver. That and the b&w s-video.
> --
> Tyler Trafford
>
>
>
-------------------------------------------------------
> 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
> ivtv-devel [at] lists
>
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

ttrafford at gmail

Feb 26, 2005, 11:14 PM

Post #24 of 29 (2278 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

It's possible that it worked fine for some other reason- but my guess
would be that the tuner just happened to be defaulting to a frequency
that was silent.

On Sat, 26 Feb 2005 21:48:34 -0800 (PST), Jason Knisley
<knisleyjw [at] yahoo> wrote:
> At the risk of sounding stupid, I didn't. With 0.3.2d,
> I didn't have the tuner static mixed into the
> composite input's video. Is this because the tuner
> couldn't be controlled properly until recently, or is
> this something with the cx25840 recently?
>
> I had absolutely perfect composite video and audio
> that I could've recorded off of. I don't really care
> hugely about the composite in right now, but it, as
> the FM tuner, would be nice icing to have.
>
> Thanks,
> Jason
>
> > Everyone has had that particular problem since the
> > inception of the
> > cx25840 driver. That and the b&w s-video.
> > --
> > Tyler Trafford
> >
> >
> >
> -------------------------------------------------------
> > 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
> > ivtv-devel [at] lists
> >
> 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
> ivtv-devel [at] lists
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>

--
Tyler Trafford

-------------------------------------------------------
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

knisleyjw at yahoo

Feb 26, 2005, 11:27 PM

Post #25 of 29 (2244 views)
Permalink

Re: [PATCH] Cumulative vsync, picture controls, pg600/150mce and 500mce tuner patch [In reply to]

Possibly.. when I flipped to the tuner, I got a lot of
static and hiss... So it didn't sound terribly silent.
Just weird. I'll look into it more when I have time.

Jason
--- Tyler Trafford <ttrafford [at] gmail> wrote:

> It's possible that it worked fine for some other
> reason- but my guess
> would be that the tuner just happened to be
> defaulting to a frequency
> that was silent.
>
>
> On Sat, 26 Feb 2005 21:48:34 -0800 (PST), Jason
> Knisley
> <knisleyjw [at] yahoo> wrote:
> > At the risk of sounding stupid, I didn't. With
> 0.3.2d,
> > I didn't have the tuner static mixed into the
> > composite input's video. Is this because the tuner
> > couldn't be controlled properly until recently, or
> is
> > this something with the cx25840 recently?
> >
> > I had absolutely perfect composite video and audio
> > that I could've recorded off of. I don't really
> care
> > hugely about the composite in right now, but it,
> as
> > the FM tuner, would be nice icing to have.
> >
> > Thanks,
> > Jason
> >
> > > Everyone has had that particular problem since
> the
> > > inception of the
> > > cx25840 driver. That and the b&w s-video.
> > > --
> > > Tyler Trafford
> > >
> > >
> > >
> >
>
-------------------------------------------------------
> > > 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
> > > ivtv-devel [at] lists
> > >
> >
>
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
> > ivtv-devel [at] lists
> >
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
> >
>
>
> --
> Tyler Trafford
>
>
>
-------------------------------------------------------
> 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
> ivtv-devel [at] lists
>
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
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

1 2

View All

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads