Conexant updated their datasheet for the cx25840. It's now also available from
dl.ivtvdriver.org/datasheets/video. The old version had several blank pages
where text should be, this is now fixed. I don't know what else they fixed,
but I'll be going through it this weekend.
Hans
On Thursday 29 September 2005 20:11, Christophe Massiot wrote:
On Wed, Sep 28, 2005, Hans Verkuil wrote:
The patch to
ivtv-driver.c is needed because otherwise ivtv-radio -s doesn't return
any station. It doesn't seem to disturb anything else.
The patch to tuner.c is needed because
On Thursday 29 September 2005 20:11, Christophe Massiot wrote:
Attached is my current patch against the svn. Tell me if radio works for
you with it.
Yes, it works and it sound better indeed. I think we're close to cracking it.
When you make a log under Windows, can you also make a separate
It's a known bug that the composite/s-video inputs have no sound. I'm looking
into this.
For the time being you can add 'options tda9887 port1=0,port2=0'
to /etc/modprobe.conf. This will make those options active on load of the
module. Run 'depmod' after changing this file just to be sure.
On Sunday 02 October 2005 23:02, Nick Rosier wrote:
MythTV playback got broken somewhere between r2720 and the latest
current release.
When playing back in MythTV, I get these error messages:
2005-10-02 21:10:44.006 IVTV rawframes decreased! Did the decoder reset?
2005-10-02 21:10:44.023
On Monday 03 October 2005 06:04, Ross wrote:
On 10/3/05, Anduin Withers [EMAIL PROTECTED] wrote:
What is the general opinion on abandoning the 0.2 branch in favor of
0.3?
I use 0.2 because I trust 0.2. That trust isn't because it labeled
stable it comes from running it for a long time
On Monday 03 October 2005 18:52, Julien Pervillé wrote:
Le 3 oct. 05, à 09:41, Hans Verkuil a écrit :
It's now called --log-status.
Hans,
Are you sure that --log-status is a valid argument to ivtv-ctrl?
In the latest svn it is --log-status. I changed this last night. Make sure
you're
On Monday 03 October 2005 18:26, Axel Thimm wrote:
Hi,
On Sun, Oct 02, 2005 at 10:34:24PM +0200, Hans Verkuil wrote:
Should we still continue the 0.2 branch? My personal opinion is that once
0.3.9 is released (I'm tentatively aiming for next weekend) that should
become the new stable
On Tuesday 04 October 2005 05:13, Jesse Guardiani wrote:
Hello,
I bought one of those add-on cards from Hauppauge
that provides an extra set of svid/composite inputs
via the white header on the card.
The video input works, but the audio input doesn't
show up:
# ivtvctl -A
ioctl:
On Tuesday 04 October 2005 07:49, Julien Pervillé wrote:
Test done correctly this time...
Using the exact same firmware as on the windows side.
With the latest ivtvctrl binary so that I get --log-status
With your secam.diff patch on top of the 2737 svn build.
7PM Note: France 3 is back to
On Monday 03 October 2005 18:10, Jesse Guardiani wrote:
Hans Verkuil wrote:
Should we still continue the 0.2 branch? My personal opinion is that once
0.3.9 is released (I'm tentatively aiming for next weekend) that should
become the new stable series. Anything that 0.2 does better than
Hi,
Cory Papenfuss wrote:
Am I missing something on the versioning scheme of ivtv? I
downloaded the 0.3.9 tarball a week or so ago and managed a make a
pvr-500 work with it.
Last night I downloaded 0.3.9 again, and it refused to compile
with errors:
On Tuesday 04 October 2005 23:45, Keith C wrote:
On Oct 4, 2005, at 4:10 PM, Mercury Morris wrote:
On 9/23/05, Adam Forsyth [EMAIL PROTECTED] wrote:
Well, I just gave up and am now using the tveeprom that came with my
kernel. But I'd still love to know what the cx88xx / cx8800 module is
On Wednesday 05 October 2005 18:52, Chris Kennedy wrote:
I am kinda irritated now, why was this done, ivtv.tv requested to be
shutdown???
I have my donations page there, and other information, and I have used
the site for development needs of my own to improve ivtv in the future,
not sure
On Wednesday 05 October 2005 18:51, Jesse Guardiani wrote:
Hans Verkuil wrote:
On Tuesday 04 October 2005 05:13, Jesse Guardiani wrote:
Hello,
I bought one of those add-on cards from Hauppauge
that provides an extra set of svid/composite inputs
via the white header on the card
On Wednesday 05 October 2005 21:43, Tyler Trafford wrote:
A week or so back I moved the contents of the 'patches' directory and a
few things from the 'utils' directory into 'misc'.
It's my feeling that these files probably shouldn't be in the
distribution itself, but instead in a directory on
On Thursday 06 October 2005 02:38, Mark Kundinger wrote:
A 0.2 driver that will compile on kernel 2.6.13? Sweet, that will make
it easy for me to compare 0.2 and 0.3.9 to see if there are any quality
differences. Maybe I can do that over the weekend.
And to make sure if I understand
On Thursday 06 October 2005 03:46, Ross wrote:
On 10/6/05, Hans Verkuil [EMAIL PROTECTED] wrote:
Can someone update the download info page on the ivtv.writeme.ch wiki?
http://ivtv.writeme.ch/tiki-index.php?page=DownloadIvyTv
It still points to ivtv.tv instead of dl.ivtvdriver.org
On Thursday 06 October 2005 21:14, D. Hugh Redelmeier wrote:
Video-Frequencies-0.03.tar.gz seems to live on ivtv.sourceforge.net
http://ivtv.sourceforge.net itself seems to be redirected to
http://ivtvdriver.org/index.php/Main_Page
Is Video-Frequencies-0.03.tar.gz orphaned by the
On Thursday 06 October 2005 18:16, Julien Pervillé wrote:
Le 5 oct. 05, à 14:35, Hans Verkuil a écrit :
Still no luck getting
$ ivtvctl --log-status to work...
ioctl IVTV_IOC_LOG_BOARD_STATUS to work...
Can you trace this? I've no idea why this won't work for you. The ioctl
should
There are two encoder firmware versions in widespread use. Version 0x02040011
and 0x02050032. I haven't been able to tell the difference between the two in
practical use. Given a choice I'd go for the newer one (after all, there must
be a reason they released a new version :-)
Other encoder
On Thursday 06 October 2005 08:57, Martin Dauskardt wrote:
At the same time I'll release svn 0.3.9 as 0.4.0 in the 0.4
branch.
Hans,
could you please have a look to
http://www.gossamer-threads.com/lists/ivtv/devel/24561 ?
Trying a 0.3.9 SVN version about two days ago, I still had to edit
On Friday 07 October 2005 01:16, Leonard Orb wrote:
Hans Verkuil wrote:
This usage is all over the place in the kernel and in fact also in the
video4linux repository. So I am hesitant to add workarounds for what is
by now a really old compiler. It is impossible to upgrade to a newer
On Friday 07 October 2005 05:52, Ross wrote:
On 10/7/05, Edward Martin [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]:~$ /sbin/modinfo tuner
filename: /lib/modules/2.6.13.3/kernel/drivers/media/video/tuner.ko
Yep, there's your problem. Rename that file to tuner.ko.old, then
rerun depmod
Hans Verkuil wrote:
But there's indeed no such problem with the kernel sources although the
kernel people have defines of the same style and use it the same way.
Yes, how is that possible? Can you try to compile 2.6.14-rc3, and
especially the tuner*.c sources in drivers/media/video
I've added the fix and you should now be able to compile ivtv with gcc-2.95.
Please check!
Hans
___
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
This is a final call before closing tickets #20 and #21 (no sound on one or
more tuners). Is there anyone who has no sound whatsoever?
Some people still have the problem that there is no sound on some channels, or
that the sound kicks in after 10-30 seconds. I've created ticket #33 for
that,
On Friday 07 October 2005 21:08, Justin I. Nevill wrote:
Hi folks,
I haven't been keeping up with the mailing list for a while, and I come
back and there's been s much progress! Way to go folks!
I'm using a Yuan MPC622
(http://www.yuan.com.tw/en/products/vdo_mpc622.html) on a 2.4.31
On Friday 07 October 2005 21:31, Christophe Massiot wrote:
On Wed, Sep 28, 2005, Christophe Massiot wrote:
I have a machine where /dev/video0 becomes empty when I start
ivtv-radio. It is clearly machine-specific because the same card with
the same kernel and driver in another machine
On Friday 07 October 2005 22:50, Trev Jackson wrote:
I think we can now say that there is not much more that can be done to make
ivtv compatible with the Adaptec AVC-2410 and the Adaptec AVC-2010.
I now use the following to load the driver:
modprobe tuner ignore=0,0x6b
modprobe ivtv
On Saturday 08 October 2005 00:22, Trev Jackson wrote:
How does this work in Windows? Do they have separate NTSC and PAL
drivers? Do they ask the user whether they are PAL or NTSC? It's not
possible to autodetect the tuner type unfortunately, so they must use
some other mechanism.
I've created a supporting-tools directory on dl.ivtvdriver.org and copied
Video-Frequencies-0.03.tar.gz and Video-ivtv-0.13.tar.gz into it.
Hans
___
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
I've updated the recommended firmware page to point to the latest versions and
I give some extra background information. As far as I know the latest
firmware versions work for all cards supported by ivtv. I've also have one
confirmed case where the latest audio firmware fixes slow or no audio
On Thursday 06 October 2005 18:16, Julien Pervillé wrote:
Le 5 oct. 05, à 14:35, Hans Verkuil a écrit :
Still no luck getting
$ ivtvctl --log-status to work...
ioctl IVTV_IOC_LOG_BOARD_STATUS to work...
Can you trace this? I've no idea why this won't work for you. The ioctl
should
On Sunday 09 October 2005 01:53, lantz moore wrote:
sometimes i get no sound and sometimes i get static out of my single
pvr350. the video in and out both work perfectly. i live in ntsc land
and i'm using the tuner input.
Can you test the card under Windows? I ask this because it sounds like
Available from http://dl.ivtvdriver.org/ivtv/archive/0.2.0/ivtv-0.2.0.tar.gz
And you can expect the 0.4.0 stable release in 1-2 hours :-)
Hans
___
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
On Sunday 09 October 2005 11:07, Paul Koster wrote:
Hans Verkuil wrote:
Tomorrow around noon (i.e. in about 12 hours from now) I'm going to
make and release 0.2.0 and 0.4.0. I think pretty much everything is
done that can be done.
With a large number of new users coming over from 0.2
On Sunday 09 October 2005 00:39, Adam Forsyth wrote:
Noone else responded to this so I guess I'll give it a go, but I don't
know much about it. first of all, for /dev/video48 (and /dev/video16?)
should probably be noted that they are pvr-350 only.
Added this.
/dev/video32
The raw video
On Sunday 09 October 2005 14:13, JP Fournier wrote:
Hmmn. I've got a compile problem.
slackware 10.2
kernel 2.4.31
gcc 3.3.6
gcc -D__KERNEL__ -D__KERNEL_SYSCALLS__ -DMODULE -DMODVERSIONS
-DEXPORT_SYMTAB -I/lib/modules/2.4.31/build/include -O2
-fomit-frame-pointer -march=i586 -mcpu=i586
On Sunday 09 October 2005 21:03, Trev Jackson wrote:
On Sunday 09 Oct 2005 19:06, Hans Verkuil wrote:
I've been thinking on how to handle compatibility with older kernels in
the 0.5 series. The problem is that to stay backwards compatible requires
keeping the supporting drivers (tuner
On Monday 10 October 2005 16:44, Mauro Carvalho Chehab wrote:
Hans,
Em Dom, 2005-10-09 às 17:44 +0200, Hans Verkuil escreveu:
On Sunday 09 October 2005 17:27, Adam Forsyth wrote:
It says right at the top of the the cvs info page that it often only
works on the current -rc, and a patch
On Monday 10 October 2005 22:13, Larry K wrote:
I now have the right version of the ivtv driver loading. To do this I had
to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the
driver properly. I was using 2.6-10.x and there appears to be no
prepackaged ivtv 0.3.x driver for
I'm busy reorganizing ivtv-0.5. I had hoped to finish it today but I don't
have enough time (well, not if I want to stay awake tomorrow :-). However I
expect to complete it tomorrow. BTW, Mauro has already merged msp3400 into
v4l, so that saves a lot of time. Thanks, Mauro!
Hans
On Tuesday 11 October 2005 22:10, Christoph Schulz wrote:
Hello,
with ivtv 0.4.0 I have no radio anymore (noise on all frequencies). With
ivtv 0.3.8 I got radio with the kernel supplied tuner tda9887 module
(kernel 2.6.12-gentoo-r9). With ivtv 0.4.0, I have no radio regardless
whether I use
On Tuesday 11 October 2005 22:10, Christoph Schulz wrote:
Hello,
with ivtv 0.4.0 I have no radio anymore (noise on all frequencies). With
ivtv 0.3.8 I got radio with the kernel supplied tuner tda9887 module
(kernel 2.6.12-gentoo-r9). With ivtv 0.4.0, I have no radio regardless
whether I use
On Thursday 13 Oct 2005 11:53, Trev Jackson wrote:
Hi
I tried SVN-1291, which gives a similar error:
make[2]: Entering directory `/usr/src/linux-2.6.8.1-12mdk'
CC [M] /home/mythtv/ivtv-2791/driver/ivtv-driver.o
/home/mythtv/ivtv-2791/driver/ivtv-driver.c: In function
On Thursday 13 October 2005 17:40, Trev Jackson wrote:
On Thursday 13 Oct 2005 14:22, Trev Jackson wrote:
On Thursday 13 Oct 2005 13:43, Hans Verkuil wrote:
On Thursday 13 Oct 2005 11:53, Trev Jackson wrote:
Hi
I tried SVN-1291, which gives a similar error:
make[2
On Monday 24 October 2005 22:55, Micah F. Galizia wrote:
Hans Verkuil wrote:
On Wednesday 19 October 2005 23:07, Micah F. Galizia wrote:
Hello All,
First and foremost, thanks for all your hard work! These drivers are
excellent, but...
I have a PVR-250, which is being incorrectly
On Wednesday 26 October 2005 01:32, John-Marc Chandonia wrote:
I've encountered a strange bug in that ivtv 0.4.0 doesn't seem to get
along with the ondemand frequency scaling governor on my system
(2.6.13.2 kernel). After less than 24 hours of running, the system
disables the IRQ used by my
On Tuesday 25 October 2005 20:02, Keith C wrote:
I'd like to propose that the debug notice get updated in the ivtv
driver. Right now, it says something like :
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing
On Saturday 29 October 2005 23:27, Allen Rohner wrote:
I seem to be having tuner problems. I have a PVR-350 on an AMD64
machine. I've tried several combinations of ivtv 0.3.8 and 4.0, and
kernel 2.6.12 and 2.6.13 with no result. Regardless of what I do, I
only capture static with cat
On Sunday 30 October 2005 22:41, Christian Iversen wrote:
Hi all.
I have a brand new PVR500 (MCE) card. I have some questions in this
regard. Please, if you can answer even just one question, I would be
very grateful if you would take the time to answer me. If something
isn't completely
On Wednesday 02 November 2005 06:34, Tony Lill wrote:
I compiled 0.4.0 against kernel 2.6.14 and when I boot, I get the
following messages. Don't know if they're important, other problems
prevented me from actually testing the driver. Should I turn off the
video4linux modules that come with
On Monday 31 October 2005 11:05, T.J.H. Kluter wrote:
Hi all,
Just to come back on an already discussed issue. I'm the proud owner
of as well a PVR-500 as well as a PVR-150. Both cards are working
excelent with the current 0.4.0 ivtv driver. But as I'm living in
Switzerland, there are some
On Saturday 05 November 2005 12:58, Daan de Beer wrote:
Hello all,
I am the owner of a PAL PVR 500 dual tuner
When I use either 0.3.7 / 0.3.8 / 0.4.0 with encoder firmware
revision 0x02050032 I get all kinds of artifacts while recording.
This means random blocks in the video and pops in
A lot of work is going into 0.5.0 in order to move the saa7115, saa7127
and cx25840 modules to the v4l repository and then to the 2.6.15
kernel. The wm8775 and cs53l32a are already moved over.
Since there is only a relatively small window of opportunity to get big
new things into the kernel we
On Sunday 06 November 2005 16:35, Daan de Beer wrote:
Hello Hans (and ofcourse the rest of the list),
I tested the 0.4.0 driver today with firmware revision 0x02040011 and
it seemed fine and stable. Using the 0x02050032 version gives
artifacts after a small amount of time (about 2 - 5 min).
On Tuesday 08 November 2005 11:07, Axel Thimm wrote:
On Mon, Nov 07, 2005 at 08:13:51AM +0100, Hans Verkuil wrote:
A lot of work is going into 0.5.0 in order to move the saa7115,
saa7127 and cx25840 modules to the v4l repository and then to the
2.6.15 kernel. The wm8775 and cs53l32a
On Wednesday 09 November 2005 08:04, Daan de Beer wrote:
Hello all,
maybe I was too hasty with my conclusion. Yesterday my recordings
made with 0.4.0 and firmware 0x02040011 had a lot of audio and video
artifacts. I am not sure what causes this, because they now all had
it from the start...
That's correct. It won't be released until either 2.6.15 is released
and/or a stable v4l2 is released. The video4linux project makes regular
releases, so we pick one that works and recommend that one to build
against.
Remember: 0.4.x will remain for quite some time as the branch to use for
://jayslife.com
GPG Fingerprint:
[EMAIL PROTECTED] - A6CC 40B4 99A4 1C08 55A7 BCFC ECDF ED68
On 2-Oct-05, at 12:47 PM, Hans Verkuil wrote:
On Sunday 02 October 2005 18:37, Jason McLeod wrote:
This is supposed to be a Hauppauge PVR 150MCE. But the regular
drivers don't seem to be detecting
Hi Tyapkin,
What card do you have? It's apparently a new board from a new vendor we
haven't seen before. Do you have a link to the vendor's website?
Since it is a new board I'm going to need some more information to see
if we can get it to work. In particular I need a list of the chips that
-enc.bin- v4l-cx2341x-enc.fw
ivtv-fw-dec.bin- v4l-cx2341x-dec.fw
HcwMakoA.ROM - v4l-cx25840.fw
ivtv_init_mpeg.bin - v4l-cx2341x-init-mpeg.bin
Please report any problems on the ivtv-devel list!
Enjoy,
Hans Verkuil
IVTV changes:
- removed tveeprom, tuner
On Sunday 13 November 2005 05:09, Rod wrote:
Greetings,
I didn't get any response from ivtv-users so I'm hoping that there
may be an answer here. I am at the end of my rope having gone over
all the documentation, FAQ's and lists.
I am having trouble configuring sound with a dual input
I recommend trying this card in a Windows machine: I suspect that the
second tuner on the PVR500 is broken. ivtv tries to program it but it
isn't detected at all. Until now every time I see messages like that it
means broken hardware.
Hans
On Sunday 13 November 2005 17:19, Michael
Harvey for his xdriver work, to Tyler
Trafford for his work on the cx25840 and to Axel Thimm for hosting the
web page and Subversion/Trac development services. Not to mention all
those other people who contributed in one way or another.
Thanks!
Hans Verkuil
I am working on backporting the changes made in 0.5.0 to 0.4.1.
Originally I intended to do one big bang update, but it turns out the
bang is a bit too big to do in one go. So I'm going to do it in stages.
As a result of that the 0.4.1 development sources may not compile, or
if they do it may
I've finished backporting the 0.5.0 changes to 0.4.1. The 0.4.1
subversion source repository should compile and work again.
I'd appreciate if people will test this development version. If there
are no snags then I think I'll release it fairly quickly.
One important note: firmware loading now
I think we should put the old method of loading from /lib/modules back
into ivtv-0.4.1. It's not that much code and it's not really in the
way. Opinions? Just for the record: 0.5.x will only support the hotplug
method.
Hans
___
ivtv-devel
On Wednesday 16 November 2005 22:55, Nick Rosier wrote:
On 11/13/05, Hans Verkuil [EMAIL PROTECTED] wrote:
On Sunday 13 November 2005 18:26, Nick Rosier wrote:
On 11/13/05, Sigurd Nes [EMAIL PROTECTED] wrote:
Revision 2948 for the 0.4-branch broke sound for pvr350, the
pvr500mce
On Thursday 17 November 2005 11:51, Sigmund Augdal Helberg wrote:
The following small patch fixes a stack overflow and subsequent
segfault in ivtv-detect.
Signed-off-by: Sigmund Augdal Helberg [EMAIL PROTECTED]
Index: ivtv-detect.c
On Saturday 19 November 2005 18:09, Steve Laurie Sanders wrote:
This is a big clue! I think. I believe it supports my suspicion that
the DMA linked list programming might get occasionally clobbered with
SMP kernels. In your case you have two physically separate processors
so you can remove
On Monday 21 November 2005 02:16, Keith Pyle wrote:
I have a PVR-500 that will function normally for a couple of weeks,
and then fail with messages like this:
Nov 15 09:00:12 myhost kernel: ivtv0 warning: 1000 ms time out
waiting for firmware
Nov 15 09:00:12 myhost kernel: ivtv0 warning:
On Monday 21 November 2005 12:06, Sigmund Augdal Helberg wrote:
Currently the base device numbers for everything except vbi* is at
steps of 8. This means that if you put more than 4 pvr350-cards in
the same box the vbi device numbers become all messed up. With a
recently accepted patch to v4l
On Sunday 20 November 2005 18:52, Sigurd Nes wrote:
Martin Dauskardt wrote:
Yesterday I downloaded a tarball from the 0.4 branch. I managed to
solve the firmware changes, but when I switch to an analog channel
on vdr , a message channel not available appears. But I can
confirm that ivtv
On Tuesday 22 November 2005 04:51, Keith Pyle wrote:
On Monday 21 November 2005 02:16, Keith Pyle wrote:
I have a PVR-500 that will function normally for a couple of weeks,
and then fail with messages like this:
Nov 15 09:00:12 myhost kernel: ivtv0 warning: 1000 ms time out
waiting for
On Mon, 2005-11-21 at 23:00 +0100, Hans Verkuil wrote:
The first drawback can be countered by the fact that ivtv is still an
unofficial driver with a 0.x version number. People using it should
expect some changes every now and then. (So I hope to get this change
accepted before ivtv
On Saturday 26 November 2005 07:30, Geoffrey Kruse wrote:
Hallo Hans!
I've started work on this problem yesterday. I discovered that
the MPEG data is placed at the correct memory location so the
shift happens either in the DMA handling (most likely) or in the
internal buffer
On Friday 25 November 2005 19:35, Christophe Massiot wrote:
I have made some testing again with my PVR-150MCE. It turns out that
the line in ivtv-driver.c:
int cfg = TDA9887_PORT1_ACTIVE|TDA9887_PORT2_ACTIVE;
should be turned into:
int cfg = TDA9887_PORT2_ACTIVE;
at least when listening
Ticket #59 (http://ivtvdriver.org/trac/ticket/59) might be an
interesting project for someone who is interested in adding subtitle
support for ivtv in MythTV, mplayer and xine. It is something I've
always had in mind but I simply don't have the time for it. The impact
on the driver is limited,
before it is released.
The 0.5.2 release will contain the merged Japanese 'paken' branch of
this driver. Before starting the merge I wanted to release 0.5.1 with
all outstanding changes.
Enjoy,
Hans Verkuil
ChangeLog:
0.5.1 release
- fixed memory overwrite in ivtvctl.
- fixed memory
Hi all,
Please test this preliminary 0.4.1 release! Download from:
http://ivtvdriver.org/viewcvs/ivtv/branches/0.4.tar.gz?view=tar
If there are no new major problems then I want to release it next week.
I'd like to hear both successes and failures. Especially if you are
running a 2.4 kernel!
From earlier mails from T. Adachi and from reading the source I believe
that gvmvprx2.c, mpg600gr.c and tg5000tv.c are workarounds for
incomplete tda9887 support (i.e. they all program a tda9887 I2C
device). So tda9887.c must be enhanced to support these changes.
Is this correct?
saa7115gv.c
Are all these new cards encoder only?
#define IVTV_CARD_TG5000TV 9 /* NAGASE TRANSGEAR 5000TV,
encoder only */
#define IVTV_CARD_VA2000MAX_SNT6 10 /* VA2000MAX-STN6 */
#define IVTV_CARD_GV_MVPRX 11 /* I/O Data GV-MVP/RX, RX2, RX2W
*/
#define IVTV_CARD_CX23416GYC 12
IVTV_CARD_GV_MVPRX uses tuner TUNER_PANASONIC_VP27. This tuner is
defined as '46' which corresponds to TUNER_MICROTUNE_4042_FI5 in
tuner.h. Is this correct? Or is this old code? No TUNER_PANASONIC_VP27
exists in tuner.h from the video4linux repository, so I'm wondering
what to do with this.
On Saturday 26 November 2005 19:57, Hans Verkuil wrote:
IVTV_CARD_GV_MVPRX uses tuner TUNER_PANASONIC_VP27. This tuner is
defined as '46' which corresponds to TUNER_MICROTUNE_4042_FI5 in
tuner.h. Is this correct? Or is this old code? No
TUNER_PANASONIC_VP27 exists in tuner.h from
On Saturday 26 November 2005 20:49, Sigurd Nes wrote:
Hans Verkuil wrote:
Hi all,
Please test this preliminary 0.4.1 release! Download from:
http://ivtvdriver.org/viewcvs/ivtv/branches/0.4.tar.gz?view=tar
If there are no new major problems then I want to release it next
week. I'd
On Saturday 26 November 2005 22:38, Brent Kilgore wrote:
I can't get it to compile.
Make gives me the following. Am I missing a new dependency? 4.0
compiled fine
make -C driver all
make[1]: Entering directory `/root/ivtv41/driver'
created ivtv-svnversion.h
make -C
On Sunday 27 November 2005 11:54, Sigurd Nes wrote:
Hans Verkuil wrote:
On Saturday 26 November 2005 20:49, Sigurd Nes wrote:
Hans Verkuil wrote:
Hi all,
Please test this preliminary 0.4.1 release! Download from:
http://ivtvdriver.org/viewcvs/ivtv/branches/0.4.tar.gz?view=tar
On Sunday 27 November 2005 19:23, Sigurd Nes wrote:
Hans Verkuil wrote:
Have you tested r2950 and r2961? Please provide the results for
these specific revisions. My guess is that 2950 works and 2961
doesn't, but I need the test results for these revisions.
If my guess is wrong
On Sunday 27 November 2005 20:24, Sigurd Nes wrote:
Hans Verkuil wrote:
On Sunday 27 November 2005 19:23, Sigurd Nes wrote:
Hans Verkuil wrote:
Have you tested r2950 and r2961? Please provide the results for
these specific revisions. My guess is that 2950 works and 2961
doesn't, but I need
On Sunday 27 November 2005 22:52, Tyler Trafford wrote:
Sigurd Nes wrote:
Tyler Trafford wrote:
Oh, I bet I know what this is. The input numbering changed for the
150/500 cards. Tuner 0 = 0 instead of 6, for instance. So that
will need to be reconfigured in MythTV. I had completely
saa717x.c and wm8739.c contain quite a lot of code that is commented out
through '#if 0 ... #endif'. If it is obsolete, then please remove it.
If it is for future enhancements, please add a comment what it is
supposed to do.
If you have already svn access then you can do it yourself, otherwise
On Tuesday 29 November 2005 15:18, Bryan Mayland wrote:
Bryan Mayland wrote:
I upgraded from tags/0.4.0 to branches/0.4 and the recording
volume on my 2 cards (PVR-150, PVR-250 both ntsc) is definitely
lower at the same -y volume= setting as before. I haven't tracked
the problem down
On Monday 28 November 2005 04:45, [EMAIL PROTECTED] wrote:
In [EMAIL PROTECTED] message,
[EMAIL PROTECTED] wrote:
From earlier mails from T. Adachi and from reading the source I
believe that gvmvprx2.c, mpg600gr.c and tg5000tv.c are workarounds
for incomplete tda9887 support (i.e. they
On Wednesday 30 November 2005 07:55, Christoph Schulz wrote:
Hello Hans!
Hans Verkuil wrote:
Can you do the following for me: edit ivtv-irq.c, go to the
function dma_from_device(), go to the end of the function and add a
IVTV_INFO line just before the 'goto redo_dma;' line
On Wednesday 30 November 2005 00:21, Bryan Mayland wrote:
Hans Verkuil wrote:
This is due to r2954 changing the volume scaling in the
msp3400. I don't think this change is a good thing. Sure, you can
crank up the volume to the point it becomes clipped and overblown,
but the driver
On Friday 02 December 2005 20:00, Brendan Hoar wrote:
Using KnoppMyth R5A26, upgrading to 0.4.1 svn as of today (see
below), ivtv could not find the firmware. I added the following
module options, which appeared to be recognized correctly in the
example output below:
options ivtv
I've noticed that the saa717x uses the same I2C address as the
saa7114/5. Do you know of a way to uniquely identify the saa717x?
One option is to check what happens when you write to I2C address 0. The
saa7114 and saa7115 return an ID 'string' by alternately writing and
reading I2C address 0:
On Saturday 03 December 2005 16:12, Brent Kilgore wrote:
Thanks that's fixed, 4.0 still will not build tuner.o or tda9887.o.
I found this behavior on the trac page and made a note verifying it.
http://ivtvdriver.org/trac/ticket/50
Are there any workarounds? If this is fixed in the 4.1 svn,
1 - 100 of 860 matches
Mail list logo
