HI!
Additonal info:
I downgraded to rc3g and am seeing the same thing as with rc3i. This is
/proc/interrupts right after booting:
10: 21761 XT-PIC ivtv0
11: 1 XT-PIC ivtv1
12: 66 XT-PIC i8042
14: 8163 XT-PIC ide0
15:
Hi,
I had to do the same thing... try this patch of mine...
The firmware name is as follow:
/lib/module/ivtv-fw-dec.bin0
/lib/module/ivtv-fw-enc.bin0
/lib/module/ivtv-fw-dec.bin1
/lib/module/ivtv-fw-enc.bin1
Note the extra number at the end. They represent the assigned card
number.
-Loc
mu
HI!
Harry Orenstein wrote:
Now the question: I just upgraded to 0.2.0-rc3i from 0.2.0-rc3g and now I get
interrupt errors (much more than in rc3g) and /proc/interrupts shows that the
ivtv driver generates interrupts even when I am not capturing (which it
didn't do in rc3g).
There seems to be no
First, thanks for all the recent hard work. Seems like work always proceeds
in bursts - with someone always stepping up when necessary. Thanks to all
the developers for the constant progress.
Now the question: I just upgraded to 0.2.0-rc3i from 0.2.0-rc3g and now I get
interrupt errors (much
On Sunday 27 March 2005 5:35 pm, John Andersen wrote:
> On Sunday 27 March 2005 4:39 pm, William Powers wrote:
> > However, in about 6 hours of testing,
> > 0.3.2p has been 100% flawless.
>
> Ok you convinced me, I'm downloading now for
> testing. I've wanted to get off of 0.2 for some time
> bu
On Sunday 27 March 2005 4:39 pm, William Powers wrote:
> However, in about 6 hours of testing,
> 0.3.2p has been 100% flawless.
Ok you convinced me, I'm downloading now for
testing. I've wanted to get off of 0.2 for some time
but none of them would compile cleanly.
Going to try this one.
--
__
FWIW, of the 8 to 10 versions I've tried over the past six months or so,
the is the first one (since ck100zz) that records/encodes perfectly with
my two 250's. Of course, my experience has been that the non-standard
capture settings I like to use will cause trouble with versions that
work fine
Hi,
Could some one help me how to enable FM radio support on PVR150. I
have tested for this feature on ivtv-0.3.2p based on the documents
provided with the driver. But the FM radio does not seems to be
working.
Shiju
---
SF email is sponsored
--- Nick Rosier <[EMAIL PROTECTED]> wrote:
> So looks like it's set to PAL-BG now for me as well (what I need); I
> thought I'd set this in my modprobe.conf (options tuner pal=G) but
> that doesn't seem to have any effect. Need to have a further look into
> this.
I think with a 2.6 kernel you nee
Hi,
When using the ioctl VIDIOC_G_TUNER to get the signal strength it
always returns 0x. I tested the latest version ivtv-0.3.2p. It
too gives the signal strenght as 0x when tuned to any TV channels.
Could someone help me to get the right signal strength using the ivtv
driver.
Shiju
---
Marcel,
browsed a bit through the source code and found a parameter for tuner called pal
I did a insmod tuner.ko pal=G before loading ivtv and got this in dmesg:
ivtv: Setting Tuner 58
tuner: type set to 58 (LG PAL TAPE-S001D) by ivtv i2c driver #1
ivtv: Switching standard to PAL.
insmod fixup: P
Chris, Developers,
the PVR250/350 uses a firmware extracted from the windows drivers
which is 262144 bytes in size. The PVR150/500 seem to be having a
newer firmware caled HcwFalcn.rom which is 376836 byes in size.
I'm running a mixed configuration with a PVR350 and a PVR150MCE.
Currently I've bee
Hi,
I recored a part from /dev/video0 and looked at the width of recording.
I saw that the image is much more wider than it apperas on the TV. This
is happened for both, the OSD and the decoder output.
How can I figure out, if the cropping of the image output is done by the
television or by the
I'm only getting static while watching live tv. It appears my encoder is
not initializing cleanly. Originally I thought the encoder card was
failing but I confirmed it's working o.k. by trying it in a windows box.
Live tv worked after putting it back in my myth box for a short time but
failed after
The D1 video standard (for NTSC anyway) is 720x486, and DV uses, I believe,
720x480. MPEG for DVD is also produced at 720-wide and all are
non-square-pixel formats. I'd imagine that many output cards use 720-wide
because they're piggybacking on chips or engineering done for DVD, DV, or
D1 standard
masterbackend:~/ivtv-0.3.2l/driver# make
make CONFIG_VIDEO_IVTV=m -C /lib/modules/2.6.10-1-686-smp/build
M=/root/ivtv-0.3.2l/driver modules
make[1]: Entering directory `/usr/src/kernel-headers-2.6.10-1-686-smp'
CC [M] /root/ivtv-0.3.2l/driver/msp3400.o
CC [M] /root/ivtv-0.3.2l/driver/saa7115
The 720x480 for ntsc has never made sense to me. Ntsc is 4:3 aspect
ratio which for square pixels matches with 640x480, not 720x480.
Vertically I get a little overscan which seems typical with tv but what
I get horizontally I don't think can be dismissed as overscan.
My decoder output is fine, i
Hi Paul,
the same values of pixels are cropped at my TV.
It seems that the cropping only appears to the OCD not to the decoder
output.
Could that be possible?
Best Regards
TheNop
Paul Curtis schrieb:
TheNop wrote:
Hi,
I'm using the ivtvdev driver for X. I noticed that the fullscreen
output ist
TheNop wrote:
Hi,
I'm using the ivtvdev driver for X. I noticed that the fullscreen output
ist cropped.
It seems that not the full 720x576 (pal) or 720x480 (ntsc) output is
shown on the TV.
That would be normal. Most TVs (especially CRT based TVs) have an
'overscan" area both horizontally and ve
Hi,
I'm using the ivtvdev driver for X. I noticed that the fullscreen output
ist cropped.
It seems that not the full 720x576 (pal) or 720x480 (ntsc) output is
shown on the TV.
I have no idea what is the reason for that.
It would be great if anyone can give me a hint to solve the problem.
Best re
It's not a critical problem as it won't happen often.
I filled up my hard disk while watching Live TV. After I made some
space again, I had to restart the backend and reload the driver
otherwise a black screen was displayed. Restarting the front end
didn't help.
Not sure if the problem lies in iv
Am Freitag, 25. März 2005 01.14 schrieb Marcel Meier:
> Hello,
> I think, my PVR 150 has yet another Tuner which is not in the tuner.h/c - It
> is recognized by the
> tveeprom module as LG S001D MK3. Everything loads clean but Channels below
> 126MHz I can't tune to.
> Switching Channels in myth
Figured out the kernel oops, didn't realize something was sleeping still
in the mailbox code, fixed that and made it more safe to have commands in
interrupts there. Also contains the recent sound fixes for the pvr150/500.
http://ivtv.no-ip.info/ivtv-0.3/ivtv-0.3.2p.tgz
Thanks,
Chris
--
---
Chr
23 matches
Mail list logo
