Well, what I need is to exclude adapter 0 in the
scanning. I tried something like i2c_enable=0,1,1 - it
looks like the correct format for the parameter from
reading the code. That didn't solve my problem. Only
the little haphazard code addition did. Am I doing
something wrong with the syntax? Also,
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 and the updated module
from v4l that Jarod posted is giving me 00
On Sun, 27 Feb 2005, James L. Reese wrote:
Agreed, and I've spent about three weeks worth of spare time bit-banging
the driver and I have so far found no combination of register settings
that affect either one of these problems. Based on i2c captures from a
windows machine, if everything is doin
I'm getting video on both video devices and from separate sources, so I know
that works right. So I probably can't help you with the rest of your
question. I do think your assumption is correct that the two 150s are
supposed to be identical, but perhaps the difference you're seeing is a
numbering
Hi Todd,
Have you checked video1? With the patches, I'm getting
video1 all of the time, but video0 only intermittantly
(on both machines; the one with the i2c issues and the
one without any other i2c devices). I've tried various
modified tuner modules, but can't seem to figure out
what the problem
Well, I'm partially an idiot.
Helps if you put it in NTSC mode.
SO now I'm getting signal on both tuners *and* audio. However, on the
second tuner it only plays for about 15 seconds and then stops. No video or
audio and no errors in any of the logs.
Any thoughts on that?
-Todd
-Original
Cool. I'd love to think all the latest patches (removal of osd vsync
irq stuff) help out the IRQ lockup's I'm having. I'm totally convinced
the problem is because the onboard VGA and the PVR-350 are sharing the
same IRQ in my box. Unfortunately, the BIOS won't let me change them
independently. I mo
Jarod Wilson wrote:
I patched support for 47 back into the 0.3.x tuner module along with support
for the tuner on my PVR-500, so both my PVR-150MCE and 500MCE work with the
0.3.2e+megapatch+500tveeprom patches recently posted to the list. The stuff
for the 500 has been submitted upstream, will h
On Sunday 27 February 2005 15:32, Todd Tidwell wrote:
>
>
> SO I tried what you said and removed all the tuner.ko files except for the
> one from IVTV and made sure both videos were set to input 6.
>
> Same problem. I did notice that things are now autodetecting the tuner
> correctly, but all I g
SO I tried what you said and removed all the tuner.ko files except for the
one from IVTV and made sure both videos were set to input 6.
Same problem. I did notice that things are now autodetecting the tuner
correctly, but all I get is static.
Any more thoughts?
-Todd
-Original Message---
Hi, this might be off-topic, but I guess someone here might be able to
help.
I am using the the IVTV driver with my adaptec avc-2010 capture card. I
use cat /dev/video0 > temp.mpg to generate an mpg2 file. This file plays
back fine with mplayer.
However, I then try to use ffmpeg or transcode to b
The vdr-pvr350 plugin currently uses the low-level fwapi ioctl interface
to control the size of the video output window. This interface has
been marked as being for internal ivtv use only so the patch attached
adds a new ioctl to control the output window size. It also adds a new
option to ivtvfb
If I understand you correctly, you should look at the i2c_enable paramter.
On Sun, 27 Feb 2005 02:33:29 -0800 (PST), Jason Knisley
<[EMAIL PROTECTED]> wrote:
> Whee! I've found the source of the problem, just
> trying to see the format of probe or ignore while
> searching through the code to find
On Sunday 27 February 2005 05:28, Michael T. Dean wrote:
> Maverick wrote:
> >I had static on my type 47 until I forced the tuner type to 44,
>
> That's because your kernel doesn't have support for type 47. If you
> upgrade to 2.6.10 or patch your kernel as described at
> http://ivtv.no-ip.info/ne
On Sunday 27 February 2005 03:24, Joe Briggs wrote:
> Jarod,
>
> So if we get a clean .3.2e and apply your vsync patch, we can skip the
> megapatch?
I didn't write any vsync patch, that was someone else... What I'm using is the
megapatch I posted along with this tveeprom patch. The tveeprom patch
> >I had static on my type 47 until I forced the tuner type to 44,
> >
> That's because your kernel doesn't have support for type 47. If you
> upgrade to 2.6.10 or patch your kernel as described at
> http://ivtv.no-ip.info/new_tuners, type 47 will work as autodetected.
I am on kernel 2.6.10, I ha
On Sun, 27 Feb 2005, David Cain wrote:
I'm expecting to be schooled here, but if I remember correctly, dB in
isolation is the logarithmic expression of a ratio.
In the case of the 2-way splitter it would refer to the ratio of input
level to level on a given outut from the splitter. No reference lev
Hi,
I think I remember that a while ago someone mentioned that in the wm8775
all 4 mixer inputs are activated and that someone posted a patch to make
the mixer selection configurable via a module parameter.
I didn't find the patch quickly, so I re-did it. I can now select the
different audio so
I'm expecting to be schooled here, but if I remember correctly, dB in
isolation is the logarithmic expression of a ratio.
In the case of the 2-way splitter it would refer to the ratio of input
level to level on a given outut from the splitter. No reference level
needed.
However, the "measurement"
I'm trying to make my pv150 work (secam mode), kernel 2.6.11-rc5 / ivtv
0.3.2d
I found that i can have sound or video from tuner, but not both...
Here is the script i use to test :
#!/bin/sh
modprobe ivtv ivtv_std=3 tun
trev a écrit :
Hi
I am in the UK ( PAL I) and my card (an Adaptec AVC-2410) also has an
FQ1216ME/I H-3 tuner and I also found that type 38 works. However the tuner
only works with the settings from my kernel module version of tuner.c.(not
ivtv version which has 0xce instead of the 0x8e) these
Cory Papenfuss wrote:
My only question is:
3.5 dB whats? dBm, dBW, dBuV, dBarbitrary_cable_number?
|
\ /
cable from (+3.5dB in)
cable co --> 2-way splitter --> cable modem
(+3.5dB | (0 dB)
measured) |
I'm trying to make my pv150 work, kernel 2.6.11-rc5 / ivtv 0.3.2d
I found that i can have sound or video from tuner, but not both...
Here is the script i use to test :
#!/bin/sh
modprobe ivtv ivtv_std=3 tuner=38 tda9887=0
Well I finally upgraded to the 2.6 kernel and fought the ir remote and
that is working. However, I can't get the consoles on the tv out
either. When fbcon loads I get
Console: switching to colour frame buffer device 90x30
I didn't check what happens to vga out when this happens but I only
have
Hi
I am in the UK ( PAL I) and my card (an Adaptec AVC-2410) also has an
FQ1216ME/I H-3 tuner and I also found that type 38 works. However the tuner
only works with the settings from my kernel module version of tuner.c.(not
ivtv version which has 0xce instead of the 0x8e) these settings are:
Jeffrey Zellman wrote:
ok, when i load the ivtv module and run the tac command, this is the
output to /var/log/messages
...
Feb 25 20:57:30 localhost kernel: tuner 0-0061: chip found @ 0xc2
(ivtv i2c driv er #0)
good
...
Feb 25 20:57:30 localhost kernel: saa7127: Selecting NTSC video Standard
Axel Thimm a écrit :
Hi,
you can find the tuners' specs under
http://dl.ivtvdriver.org/datasheets/tuners/
Check the *-Amity2 subdirs.
I'm trying to get the tuner specs for the PVR 500 as well.
Is there any PVR 150 user that has a different tuner than the above?
In France (secam), PVR 150 have
Maverick wrote:
I had static on my type 47 until I forced the tuner type to 44,
That's because your kernel doesn't have support for type 47. If you
upgrade to 2.6.10 or patch your kernel as described at
http://ivtv.no-ip.info/new_tuners, type 47 will work as autodetected.
I may
have also upgrad
Maverick wrote:
Only way I could get my tuner type 47 to tune channels is to force it
to type 44 in mod*.conf. I still haven't resolved the dma lockup
problem when you ff/rew alot.
That's because your kernel doesn't have support for type 47. If you
upgrade to 2.6.10 or patch your kernel as des
On Sat, 26 Feb 2005 22:27:38 -0800 (PST)
Jason Knisley <[EMAIL PROTECTED]> wrote:
> 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
That would be good info. I haven't
On Sat, 26 Feb 2005 19:31:04 -0500
Tyler Trafford <[EMAIL PROTECTED]> wrote:
> On Sat, 26 Feb 2005 16:23:45 -0800 (PST), Jason Knisley
> <[EMAIL PROTECTED]> wrote:
> > Actually, I'm using the correct FQ1236A MK4. I'm using
> > the patched kernel, but it seems to be working
> > correctly and showin
Quick fix to anyone who needs a, well, quick fix for
the i2c level transfer thing:
If you notice that the cx25840 driver is attaching to
things that it shouldn't attach to and you know the
i2c adapter of the thing that's jerking it around,
here's something really quick and dirty and very
unclean,
Jarod,
So if we get a clean .3.2e and apply your vsync patch, we can skip the
megapatch?
On Sun, 2005-02-27 at 01:09, Jarod Wilson wrote:
> With the attached patch, tveeprom now reads the following off my NTSC
> PVR-500MCE:
>
> tveeprom: Hauppauge: model = 23552, rev = D292, serial# = 7725799
>
On Sun, Feb 27, 2005 at 11:41:31AM +0100, Jose Alberto Reguero wrote:
> wget http://dl.ivtvdriver.org/datasheets/tuners/PAL-tuners-Amity2/FQ1216LME\
> Mk3.pdf
> http://dl.ivtvdriver.org/datasheets/tuners/PAL-tuners-Amity2/FQ1216LME%20Mk3.pdf
>=> `FQ1216LME Mk3.pdf'
> Resolviendo dl.ivt
wget http://dl.ivtvdriver.org/datasheets/tuners/PAL-tuners-Amity2/FQ1216LME\
Mk3.pdf
--11:38:59--
http://dl.ivtvdriver.org/datasheets/tuners/PAL-tuners-Amity2/FQ1216LME%20Mk3.pdf
=> `FQ1216LME Mk3.pdf'
Resolviendo dl.ivtvdriver.org... 160.45.32.86
Conectando con dl.ivtvdriver.org[160.
Whee! I've found the source of the problem, just
trying to see the format of probe or ignore while
searching through the code to find out why the cx25840
driver isn't verifying that it's attaching to an
actual cx25840. I found a big FIXME in cx25840-driver
that had something to that affect.
It tur
Hi,
a datasheet that is rather focused on driver relevant parts can be
found under http://dl.ivtvdriver.org/datasheets/cx2584x/
Even though there are "confidential" tags, it is considered public and
crafted on Hauppauge's request to release to the Linux community.
--
Axel.Thimm at ATrpms.net
p
Hi,
you can find the tuners' specs under
http://dl.ivtvdriver.org/datasheets/tuners/
Check the *-Amity2 subdirs.
I'm trying to get the tuner specs for the PVR 500 as well.
Is there any PVR 150 user that has a different tuner than the above?
--
Axel.Thimm at ATrpms.net
pgpQkS7EBy6na.pgp
I see that there's some additional IRQ/vsync things removed in that
patch. I thought 0.3.2e had that stuff removed already? I'm assuming
this is additional stuff that's been removed? Reason I'm asking is I'm
trying to get some IRQ problems resolved with my PVR-350 tuner 47...
I'll give this patch
Hi all,
I had a problem back a while ago when I initially
posted my tuner data to the forum, but no one got
round to it and here it is cropping up again. I had a
Compaq test machine that I put the PVR-500 in and it
worked rather well (except it was too damn slow to be
of any good).
I originally h
Hi Jarod,
Do you think you could create the same patch etc for the Philips FQ1216AME
MK4? Tuner 91 and is PAL.
There are a few of us here in PAL land that I am sure would greatly
appreciate the effort.
Model 23559 Rev D291
Serial No: 7725589
Tuner[1]: Model 91 (Philips FQ1216AME_MK4)
Decoder: 30
41 matches
Mail list logo
