Re: [ivtv-devel] VBI (again)
Hi, Tyler Trafford wrote: Bryan Mayland wrote: Morten Rnseth wrote: Hah! I found "/lib/modules/2.6.8.1-12mdk/kernel/drivers/media/video/tda9887.ko.gz" - and I thought I'd gotten rid of all doubles... Would this one interfer? I'll take a closer look tomorrow, too late now...going to bed, I'm afraid. It certainly could. Can't wait to see what happens tomorrow, I think we're close too. Good night! I'm guessing that the I2C defined parameters are done in the 'obsolete style' in Morten's kernel version, causing it to ignore all non-obsoletely-defined ones. OK - so I cannot chuck out the black magic code and use the tda9887 with proper settings. Yet. So, either he upgrades to a new kernel, or someone adds the old style paramter definitions, also it seems the other modules (since they all use i2c headers) should have their ifdefs changed to use the obsolete style if they are on kernel = 2.6.8. Actually, there's probably no reason why he can't use the tda9887 that came with his kernel... But, unfortunately I removed it :-) Still, I can use the ivtv provided tda9887 module, can I not? Besides, teher are probably more people out there using old kernels with obsolete parameter definitions, so maybe they should be added after all? What do you think? Cheers, -Morten -- --- WEB-fx Morten Lerskau Rnseth http://www.webfx.no Odinsvei 15c mailto:[EMAIL PROTECTED] 1413 TrnsenTlf.: (47) 6680 9191 Norway Mob : (47) 9343 4357
Re: [ivtv-devel] VBI (again)
Hi, I'm guessing that the I2C defined parameters are done in the 'obsolete style' in Morten's kernel version, causing it to ignore all non-obsoletely-defined ones. BTW, what exactly is the difference between new-style parameters and obsolete ones? Cheers, -Morten -- --- WEB-fx Morten Lerskau Rønseth http://www.webfx.no Odinsvei 15c mailto:[EMAIL PROTECTED] 1413 TårnåsenTlf.: (47) 6680 9191 Norway Mob : (47) 9343 4357 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Morten Rønseth wrote: Hi, I'm guessing that the I2C defined parameters are done in the 'obsolete style' in Morten's kernel version, causing it to ignore all non-obsoletely-defined ones. BTW, what exactly is the difference between new-style parameters and obsolete ones? Theyare defined differently, take a look at the module_param/MODULE_PARM setup at the top of cx25840-driver for an example. -- Tyler Trafford --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Tyler Trafford wrote:
I'm guessing that the I2C defined parameters are done in the 'obsolete
style' in Morten's kernel version, causing it to ignore all
non-obsoletely-defined ones.
Ah yes, I didn't even think about that (even though he clearly
posted it in his log).
Actually, there's probably no reason why he can't use the tda9887 that
came with his kernel..
This is true. However, not being one to not submit like a patch a
day... this adds those params as well as syncs with the latest v4l
version, which has a parameter fix and support for mono radio (woohoo!).
Why don't you give this a try Morten? (against the 0.3.6s release)
You'll need the options:
options ivtv tda9887=0
options tda9887 port1=0 port2=0
Index: driver/tda9887.c
===
--- driver/tda9887.c(revision 325)
+++ driver/tda9887.c(working copy)
@@ -9,9 +9,17 @@
#include linux/slab.h
#include linux/delay.h
+#if LINUX_VERSION_CODE KERNEL_VERSION(2,5,0)
+#include audiochip.h
+#include tuner.h
+#include id.h
+#include i2c-compat.h
+#else
#include media/audiochip.h
-#include tuner.h
+#include media/tuner.h
#include media/id.h
+#endif
+#include compat.h
/* Chips:
TDA9885 (PAL, NTSC)
@@ -33,17 +41,43 @@
0x96 1,
I2C_CLIENT_END,
};
-static unsigned short normal_i2c_range[] = {I2C_CLIENT_END,I2C_CLIENT_END};
+#if LINUX_VERSION_CODE KERNEL_VERSION(2,6,13)
+static unsigned short normal_i2c_range[] = { I2C_CLIENT_END };
+#endif
I2C_CLIENT_INSMOD;
/* insmod options */
+#define UNSET (-1U)
static unsigned int debug = 0;
+static unsigned int port1 = UNSET;
+static unsigned int port2 = UNSET;
+static unsigned int qss= UNSET;
+static unsigned int adjust = 0x10;
+static char pal[] = -;
+static char secam[] = -;
+
+#if LINUX_VERSION_CODE KERNEL_VERSION(2,6,9)
module_param(debug, int, 0644);
+module_param(port1, int, 0644);
+module_param(port2, int, 0644);
+module_param(qss, int, 0644);
+module_param(adjust, int, 0644);
+module_param_string(pal, pal, sizeof(pal), 0644);
+module_param_string(secam, secam, sizeof(secam), 0644);
+#else
+MODULE_PARM(debug, i);
+MODULE_PARM(port1, i);
+MODULE_PARM(port2, i);
+MODULE_PARM(qss, i );
+MODULE_PARM(adjust, i);
+MODULE_PARM(pal, s);
+MODULE_PARM(secam, s);
+#endif
+
MODULE_LICENSE(GPL);
/* -- */
-#define UNSET (-1U)
#define PREFIX tda9885/6/7:
#define dprintk if (debug) printk
@@ -54,6 +88,7 @@
unsigned int config;
unsigned int pinnacle_id;
unsigned int using_v4l2;
+ unsigned int radio_mode;
};
struct tvnorm {
@@ -213,20 +248,26 @@
}
};
-static struct tvnorm radio = {
- .name = radio,
+static struct tvnorm radio_stereo = {
+ .name = Radio Stereo,
.b= ( cFmRadio |
- cQSS |
- cAutoMuteFmActive |
- cOutputPort1Inactive ),
- .c= ( cAudioGain6 |
- 0x10 ),
- .e= ( cAudioIF_6_5 |
- cRadioIF_38_90 |
- cGating_36 |
- cTunerGainLow ),
+ cQSS ),
+ .c= ( cDeemphasisOFF |
+ cAudioGain6 ),
+ .e= ( cAudioIF_5_5 |
+ cRadioIF_38_90 ),
};
+static struct tvnorm radio_mono = {
+ .name = Radio Mono,
+ .b= ( cFmRadio |
+ cQSS ),
+ .c= ( cDeemphasisON |
+ cDeemphasis50),
+ .e= ( cAudioIF_5_5 |
+ cRadioIF_38_90 ),
+};
+
/* -- */
static void dump_read_message(unsigned char *buf)
@@ -359,7 +400,10 @@
int i;
if (t-radio) {
- norm = radio;
+ if (t-radio_mode == V4L2_TUNER_MODE_MONO)
+ norm = radio_mono;
+ else
+ norm = radio_stereo;
} else {
for (i = 0; i ARRAY_SIZE(tvnorms); i++) {
if (tvnorms[i].std t-std) {
@@ -380,15 +424,6 @@
return 0;
}
-static unsigned int port1 = UNSET;
-static unsigned int port2 = UNSET;
-static unsigned int qss= UNSET;
-static unsigned int adjust = 0x10;
-module_param(port1, int, 0644);
-module_param(port2, int, 0644);
-module_param(qss, int, 0644);
-module_param(adjust, int, 0644);
-
static int tda9887_set_insmod(struct tda9887 *t, char *buf)
{
if (UNSET != port1) {
@@ -418,6 +453,12 @@
static int tda9887_set_config(struct tda9887 *t, char *buf)
{
+#if LINUX_VERSION_CODE KERNEL_VERSION(2,6,11)
+ if (t-config TDA9887_PORT1)
+ buf[1] |= cOutputPort1Inactive;
+ if (t-config TDA9887_PORT2)
+ buf[1] |= cOutputPort2Inactive;
+#else
if (t-config TDA9887_PORT1_ACTIVE)
Re: [ivtv-devel] VBI (again)
Bryan Mayland wrote:
Proving once again that I can't produce a working patch before noon. I
got the #if backward so it defined new-style params on old systems and
old-style params on new systems. This patch has it the right way.
Index: driver/tda9887.c
===
--- driver/tda9887.c(revision 325)
+++ driver/tda9887.c(working copy)
@@ -9,9 +9,17 @@
#include linux/slab.h
#include linux/delay.h
+#if LINUX_VERSION_CODE KERNEL_VERSION(2,5,0)
+#include audiochip.h
+#include tuner.h
+#include id.h
+#include i2c-compat.h
+#else
#include media/audiochip.h
-#include tuner.h
+#include media/tuner.h
#include media/id.h
+#endif
+#include compat.h
/* Chips:
TDA9885 (PAL, NTSC)
@@ -33,17 +41,43 @@
0x96 1,
I2C_CLIENT_END,
};
-static unsigned short normal_i2c_range[] = {I2C_CLIENT_END,I2C_CLIENT_END};
+#if LINUX_VERSION_CODE KERNEL_VERSION(2,6,13)
+static unsigned short normal_i2c_range[] = { I2C_CLIENT_END };
+#endif
I2C_CLIENT_INSMOD;
/* insmod options */
+#define UNSET (-1U)
static unsigned int debug = 0;
+static unsigned int port1 = UNSET;
+static unsigned int port2 = UNSET;
+static unsigned int qss= UNSET;
+static unsigned int adjust = 0x10;
+static char pal[] = -;
+static char secam[] = -;
+
+#if LINUX_VERSION_CODE KERNEL_VERSION(2,6,9)
+MODULE_PARM(debug, i);
+MODULE_PARM(port1, i);
+MODULE_PARM(port2, i);
+MODULE_PARM(qss, i );
+MODULE_PARM(adjust, i);
+MODULE_PARM(pal, s);
+MODULE_PARM(secam, s);
+#else
module_param(debug, int, 0644);
+module_param(port1, int, 0644);
+module_param(port2, int, 0644);
+module_param(qss, int, 0644);
+module_param(adjust, int, 0644);
+module_param_string(pal, pal, sizeof(pal), 0644);
+module_param_string(secam, secam, sizeof(secam), 0644);
+#endif
+
MODULE_LICENSE(GPL);
/* -- */
-#define UNSET (-1U)
#define PREFIX tda9885/6/7:
#define dprintk if (debug) printk
@@ -54,6 +88,7 @@
unsigned int config;
unsigned int pinnacle_id;
unsigned int using_v4l2;
+ unsigned int radio_mode;
};
struct tvnorm {
@@ -213,20 +248,26 @@
}
};
-static struct tvnorm radio = {
- .name = radio,
+static struct tvnorm radio_stereo = {
+ .name = Radio Stereo,
.b= ( cFmRadio |
- cQSS |
- cAutoMuteFmActive |
- cOutputPort1Inactive ),
- .c= ( cAudioGain6 |
- 0x10 ),
- .e= ( cAudioIF_6_5 |
- cRadioIF_38_90 |
- cGating_36 |
- cTunerGainLow ),
+ cQSS ),
+ .c= ( cDeemphasisOFF |
+ cAudioGain6 ),
+ .e= ( cAudioIF_5_5 |
+ cRadioIF_38_90 ),
};
+static struct tvnorm radio_mono = {
+ .name = Radio Mono,
+ .b= ( cFmRadio |
+ cQSS ),
+ .c= ( cDeemphasisON |
+ cDeemphasis50),
+ .e= ( cAudioIF_5_5 |
+ cRadioIF_38_90 ),
+};
+
/* -- */
static void dump_read_message(unsigned char *buf)
@@ -359,7 +400,10 @@
int i;
if (t-radio) {
- norm = radio;
+ if (t-radio_mode == V4L2_TUNER_MODE_MONO)
+ norm = radio_mono;
+ else
+ norm = radio_stereo;
} else {
for (i = 0; i ARRAY_SIZE(tvnorms); i++) {
if (tvnorms[i].std t-std) {
@@ -380,15 +424,6 @@
return 0;
}
-static unsigned int port1 = UNSET;
-static unsigned int port2 = UNSET;
-static unsigned int qss= UNSET;
-static unsigned int adjust = 0x10;
-module_param(port1, int, 0644);
-module_param(port2, int, 0644);
-module_param(qss, int, 0644);
-module_param(adjust, int, 0644);
-
static int tda9887_set_insmod(struct tda9887 *t, char *buf)
{
if (UNSET != port1) {
@@ -418,6 +453,12 @@
static int tda9887_set_config(struct tda9887 *t, char *buf)
{
+#if LINUX_VERSION_CODE KERNEL_VERSION(2,6,11)
+ if (t-config TDA9887_PORT1)
+ buf[1] |= cOutputPort1Inactive;
+ if (t-config TDA9887_PORT2)
+ buf[1] |= cOutputPort2Inactive;
+#else
if (t-config TDA9887_PORT1_ACTIVE)
buf[1] = ~cOutputPort1Inactive;
if (t-config TDA9887_PORT1_INACTIVE)
@@ -426,6 +467,7 @@
buf[1] = ~cOutputPort2Inactive;
if (t-config TDA9887_PORT2_INACTIVE)
buf[1] |= cOutputPort2Inactive;
+#endif
if (t-config TDA9887_QSS)
buf[1] |= cQSS;
@@ -448,8 +490,6 @@
break;
}
}
- if(t-config TDA9887_LOW_GAIN)
- buf[2] |= cTunerGainLow;
return 0;
}
Re: [ivtv-devel] VBI (again)
Hi Bryan, Bryan Mayland wrote: Bryan Mayland wrote: Proving once again that I can't produce a working patch before noon. I got the #if backward so it defined new-style params on old systems and old-style params on new systems. This patch has it the right way. Hmmm - seems my system doesn't like the patch: CC [M] /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.o /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c: In function `tda9887_set_config': /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c:457: error: `TDA9887_PORT1' undeclared (first use in this function) /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c:457: error: (Each undeclared identifier is reported only once /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c:457: error: for each function it appears in.) /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c:459: error: `TDA9887_PORT2' undeclared (first use in this function) /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c:472: error: `TDA9887_QSS' undeclared (first use in this function) /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c:474: error: `TDA9887_INTERCARRIER' undeclared (first use in this function) /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c:477: error: `TDA9887_AUTOMUTE' undeclared (first use in this function) /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c:479: error: `TDA9887_DEEMPHASIS_MASK' undeclared (first use in this function) /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c:482: error: `TDA9887_DEEMPHASIS_NONE' undeclared (first use in this function) /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c:485: error: `TDA9887_DEEMPHASIS_50' undeclared (first use in this function) /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c:488: error: `TDA9887_DEEMPHASIS_75' undeclared (first use in this function) /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c: In function `tda9887_command': /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c:719: error: `TDA9887_SET_CONFIG' undeclared (first use in this function) /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c: At top level: /usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.c:573: warning: 'tda9887_status' defined but not used make[3]: *** [/usr/local/src/IVTV/ivtv-0.3.6s/driver/tda9887.o] Error 1 make[2]: *** [_module_/usr/local/src/IVTV/ivtv-0.3.6s/driver] Error 2 make[2]: Leaving directory `/usr/src/linux-2.6.8.1-12mdk' make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/local/src/IVTV/ivtv-0.3.6s/driver' make: *** [driver] Error 2 Am I missing a headerfile, maybe? Cheers, -Morten -- --- WEB-fx http://www.webfx.no Morten Lerskau Rønseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Tårnåsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Morten Rønseth wrote:
Hmmm - seems my system doesn't like the patch:
Gah! I thought these were defined in 2.6 series' tuner.h.
Apparently they didn't make it in until recently. Try patch #3!
Index: driver/tda9887.c
===
--- driver/tda9887.c(revision 325)
+++ driver/tda9887.c(working copy)
@@ -9,9 +9,17 @@
#include linux/slab.h
#include linux/delay.h
+#include tuner.h
+
+#if LINUX_VERSION_CODE KERNEL_VERSION(2,5,0)
+#include audiochip.h
+#include id.h
+#include i2c-compat.h
+#else
#include media/audiochip.h
-#include tuner.h
#include media/id.h
+#endif
+#include compat.h
/* Chips:
TDA9885 (PAL, NTSC)
@@ -33,17 +41,43 @@
0x96 1,
I2C_CLIENT_END,
};
-static unsigned short normal_i2c_range[] = {I2C_CLIENT_END,I2C_CLIENT_END};
+#if LINUX_VERSION_CODE KERNEL_VERSION(2,6,13)
+static unsigned short normal_i2c_range[] = { I2C_CLIENT_END };
+#endif
I2C_CLIENT_INSMOD;
/* insmod options */
+#define UNSET (-1U)
static unsigned int debug = 0;
+static unsigned int port1 = UNSET;
+static unsigned int port2 = UNSET;
+static unsigned int qss= UNSET;
+static unsigned int adjust = 0x10;
+static char pal[] = -;
+static char secam[] = -;
+
+#if LINUX_VERSION_CODE KERNEL_VERSION(2,6,9)
+MODULE_PARM(debug, i);
+MODULE_PARM(port1, i);
+MODULE_PARM(port2, i);
+MODULE_PARM(qss, i );
+MODULE_PARM(adjust, i);
+MODULE_PARM(pal, s);
+MODULE_PARM(secam, s);
+#else
module_param(debug, int, 0644);
+module_param(port1, int, 0644);
+module_param(port2, int, 0644);
+module_param(qss, int, 0644);
+module_param(adjust, int, 0644);
+module_param_string(pal, pal, sizeof(pal), 0644);
+module_param_string(secam, secam, sizeof(secam), 0644);
+#endif
+
MODULE_LICENSE(GPL);
/* -- */
-#define UNSET (-1U)
#define PREFIX tda9885/6/7:
#define dprintk if (debug) printk
@@ -54,6 +88,7 @@
unsigned int config;
unsigned int pinnacle_id;
unsigned int using_v4l2;
+ unsigned int radio_mode;
};
struct tvnorm {
@@ -213,20 +248,26 @@
}
};
-static struct tvnorm radio = {
- .name = radio,
+static struct tvnorm radio_stereo = {
+ .name = Radio Stereo,
.b= ( cFmRadio |
- cQSS |
- cAutoMuteFmActive |
- cOutputPort1Inactive ),
- .c= ( cAudioGain6 |
- 0x10 ),
- .e= ( cAudioIF_6_5 |
- cRadioIF_38_90 |
- cGating_36 |
- cTunerGainLow ),
+ cQSS ),
+ .c= ( cDeemphasisOFF |
+ cAudioGain6 ),
+ .e= ( cAudioIF_5_5 |
+ cRadioIF_38_90 ),
};
+static struct tvnorm radio_mono = {
+ .name = Radio Mono,
+ .b= ( cFmRadio |
+ cQSS ),
+ .c= ( cDeemphasisON |
+ cDeemphasis50),
+ .e= ( cAudioIF_5_5 |
+ cRadioIF_38_90 ),
+};
+
/* -- */
static void dump_read_message(unsigned char *buf)
@@ -359,7 +400,10 @@
int i;
if (t-radio) {
- norm = radio;
+ if (t-radio_mode == V4L2_TUNER_MODE_MONO)
+ norm = radio_mono;
+ else
+ norm = radio_stereo;
} else {
for (i = 0; i ARRAY_SIZE(tvnorms); i++) {
if (tvnorms[i].std t-std) {
@@ -380,15 +424,6 @@
return 0;
}
-static unsigned int port1 = UNSET;
-static unsigned int port2 = UNSET;
-static unsigned int qss= UNSET;
-static unsigned int adjust = 0x10;
-module_param(port1, int, 0644);
-module_param(port2, int, 0644);
-module_param(qss, int, 0644);
-module_param(adjust, int, 0644);
-
static int tda9887_set_insmod(struct tda9887 *t, char *buf)
{
if (UNSET != port1) {
@@ -448,8 +483,6 @@
break;
}
}
- if(t-config TDA9887_LOW_GAIN)
- buf[2] |= cTunerGainLow;
return 0;
}
@@ -483,10 +516,6 @@
/* -- */
-static char pal[] = -;
-module_param_string(pal, pal, 0644, sizeof(pal));
-static char secam[] = -;
-module_param_string(secam, secam, 0644, sizeof(secam));
static int tda9887_fixup_std(struct tda9887 *t)
{
@@ -545,19 +574,6 @@
return 0;
}
-#if LINUX_VERSION_CODE = KERNEL_VERSION(2, 6, 8)
-static unsigned int msleep_interruptible(unsigned int msecs)
-{
- unsigned long timeout = msecs_to_jiffies(msecs);
-
- while (timeout !signal_pending(current)) {
- set_current_state(TASK_INTERRUPTIBLE);
- timeout = schedule_timeout(timeout);
- }
- return
Re: [ivtv-devel] VBI (again)
Hi :-) Bryan Mayland wrote: Morten Rønseth wrote: Hmmm - seems my system doesn't like the patch: Gah! I thought these were defined in 2.6 series' tuner.h. Apparently they didn't make it in until recently. Try patch #3! Uhm - sorry to be the bearer of bad omens, but I don't have i2c-compat.h either. Seriously. I'm searching the net for it right now... Cheers, -Morten -- --- WEB-fx http://www.webfx.no Morten Lerskau Rønseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Tårnåsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
OK, never mind the bollocks, I'm a babbling fool. This did the trick, Bryan, just what the doctor ordered. First impressions are great, later tonight I'll give it the wife's stress testing :-) Thanks! Cheers, -Morten Bryan Mayland wrote: Morten Rnseth wrote: Hmmm - seems my system doesn't like the patch: Gah! I thought these were defined in 2.6 series' tuner.h. Apparently they didn't make it in until recently. Try patch #3! -- --- WEB-fx http://www.webfx.no Morten Lerskau Rnseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Trnsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477_id=16492=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Hi Bryan,
Bryan Mayland wrote:
Morten
Rnseth wrote:
I've just tried that - seems like it's
the cx25840 module that makes anything above 0.3.5 fail. After I load
0.3.5, I unload everything except the cx25840 module (ivtv, wm8775,
tveeprom tuner, in that order - anything else I should know of?),
then load 0.3.6q. It works.
Ok, so 0.3.5a fails too? If that's the case we can definitely
narrow down the problem. Try this patch against the current version to
see if you can use the current cx25840.
This worked - almost :-) I get picture, but I seem to get vertical
ghosting - there seem to be slight ghosting "shadows" over under
any given point on the screen (almost like antialiasing), it is very
obvious when looking at letters.
Cheers,
-Morten
Index: cx25840-driver.c
===
--- cx25840-driver.c (revision 323)
+++ cx25840-driver.c (working copy)
@@ -427,6 +427,16 @@
CX25840_SET_PWR_DN_TUNING(pwr_dn);
}
#endif
+static int execute_wi2c(struct i2c_client *client, int addr, u8 * b,
+int len)
+{
+ int save_addr = client-addr;
+ int retval;
+ client-addr = addr;
+ retval = i2c_master_send(client, b, len);
+ client-addr = save_addr;
+ return retval;
+}
static int cx25840_command(struct i2c_client *client, unsigned int cmd, void *arg)
{
@@ -717,6 +727,10 @@
CX25840_SET_VID_OUT_EN(enable);
CX25840_SET_PLL_CLK_OUT_EN(enable);
+{
+u8 bytes[] = { 0x00, 0x16, 0x70, 0x4a };
+execute_wi2c(client, 0x43, bytes, 4);
+}
state-enable = enable;
break;
--
---
WEB-fx http://www.webfx.no
Morten Lerskau Rnseth mailto:[EMAIL PROTECTED]
Odinsvei 15c +47 6680 9191
1413 Trnsen+47 9343 4357
Norway
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477_id=16492=click
___
ivtv-devel mailing list
ivtv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Morten Rønseth wrote: This worked - almost :-) I get picture, but I seem to get vertical ghosting - there seem to be slight ghosting shadows over under any given point on the screen (almost like antialiasing), it is very obvious when looking at letters. Now we're getting somewhere! Wow, so black_magic did more than just set up audio. Vey interesting. Ok now let's see about those ghosts. First try removing line 221 from cx25840-driver.c (just comment it out): CX25840_SET_ACFG_DIS(0x01); --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Tyler Trafford wrote: It turns out that kernels = 2.6.8 don't honor the INSTALL_MOD_DIR parameter. Hey, you learn something every day. Growing up on old linux kernel building (2.0-2.4), the 2.6 build process confuses and scares me. Damn progresss! --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Hi Bryan, Bryan Mayland wrote: Morten Rønseth wrote: This worked - almost :-) I get picture, but I seem to get vertical ghosting - there seem to be slight ghosting shadows over under any given point on the screen (almost like antialiasing), it is very obvious when looking at letters. Now we're getting somewhere! Wow, so black_magic did more than just set up audio. Vey interesting. Ok now let's see about those ghosts. First try removing line 221 from cx25840-driver.c (just comment it out): CX25840_SET_ACFG_DIS(0x01); Bullseye...! 10 out of 10 for style and precision :-) Works great. I'm with my (rather active) 20 month old son right now, so I'll test it some more later tonight. So far so good, love it! BTW, will this fix find it's way into the official branch of ivtv? Cheers, -Morten --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel -- --- WEB-fx http://www.webfx.no Morten Lerskau Rønseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Tårnåsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Morten Rønseth wrote: Bullseye...! 10 out of 10 for style and precision :-) Works great. I'm with my (rather active) 20 month old son right now, so I'll test it some more later tonight. So far so good, love it! Awesome news. When you get time: Do you have any module options set in modprobe.conf / modprobe.d / modules.conf? BTW, will this fix find it's way into the official branch of ivtv? The line you had to remove to get rid of the doublevision problems should be in soon. Did I already send the message about that? The black_magic patch is a hack so we'll have to find out why it works before it can go in. I'll probably need more information from you. Add this line to your modprobe.conf and post your `dmesg | grep tda9885/6/7` output please: options tda9887 debug=1 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Bryan Mayland wrote: Morten Rønseth wrote: Bullseye...! 10 out of 10 for style and precision :-) Works great. I'm with my (rather active) 20 month old son right now, so I'll test it some more later tonight. So far so good, love it! Awesome news. When you get time: Do you have any module options set in modprobe.conf / modprobe.d / modules.conf? No, nothing. I keep everything in an /etc/init.d file and all I do for startup is basically load the ivtv module... BTW, will this fix find it's way into the official branch of ivtv? The line you had to remove to get rid of the doublevision problems should be in soon. Did I already send the message about that? The black_magic patch is a hack so we'll have to find out why it works before it can go in. I'll probably need more information from you. Add this line to your modprobe.conf and post your `dmesg | grep tda9885/6/7` output please: options tda9887 debug=1 Will do, later tonight. Thanks again, Bryan. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel Cheers, -Morten -- --- WEB-fx http://www.webfx.no Morten Lerskau Rønseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Tårnåsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Morten Rønseth wrote: As it turns out, I'm not using tda9887 - I have an udefined symbol msleep_interruptible when compiling/loading and ivtv doesn't seem to need it either. Anything else I could do? hehe, you're blowing my mind! I'm hoping that this is because your tda9887 is the 0.3.5 version. 0.3.6a and above have a ifdef which /should/ define msleep_interruptible for kernels which don't have it (2.6.7 and below?). Which kernel version are you on (I can't seem to find it in your messages although I know you've said it before)? Can you also make sure the tda9887 module is from the current ivtv? You'll also have to make sure the module loads, because it seems you do need it (the magic patch sends a command to the tda9887, which must be there). You can either insmod it before ivtv, or use the ivtv module options: options ivtv tda9887=0 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Bryan Mayland wrote: Morten Rønseth wrote: As it turns out, I'm not using tda9887 - I have an udefined symbol msleep_interruptible when compiling/loading and ivtv doesn't seem to need it either. Anything else I could do? hehe, you're blowing my mind! I'm hoping that this is because your tda9887 is the 0.3.5 version. 0.3.6a and above have a ifdef which /should/ define msleep_interruptible for kernels which don't have it (2.6.7 and below?). Which kernel version are you on (I can't seem to find it in your messages although I know you've said it before)? Can you also make sure the tda9887 module is from the current ivtv? You'll also have to make sure the module loads, because it seems you do need it (the magic patch sends a command to the tda9887, which must be there). You can either insmod it before ivtv, or use the ivtv module options: options ivtv tda9887=0 I just sussed it. My kernel version is 2.6.8.1-12mdk - tda9887.c, line 548 defines msleep_iterruptible iff version is 2.6.7 or older. Don't know why, but I seem to need it, version 2.6.8 ( can't believe I haven't seen this before...). I changed the 7 to an 8 and voila! it compiles, installs and loads...:-) Below is my dmesg ivtv. Does it make any more sense? Cheers, -Morten tda9887: Unknown parameter `debug' tda9887: Ignoring new-style parameters in presence of obsolete ones Linux video capture interface: v1.00 ivtv: START INIT IVTV ivtv: version 0.3.6 (r) loading ivtv: Linux version: 2.6.8.1-12mdk 686 gcc-3.4 ivtv: In case of problems please include the debug info ivtv: between the START INIT IVTV and END INIT IVTV lines when ivtv: mailing the ivtv-devel mailinglist. ivtv: Autodetected WinTV PVR 150 card ivtv: Found an iTVC16 based chip ivtv: VIA PCI device: 0x3205 vendor: 0x1106 tda9885/6/7: chip found @ 0x86 ivtv: i2c attach [client=tda9887,ok] tveeprom: Ignoring new-style parameters in presence of obsolete ones tveeprom: Hauppauge: model = 26559, rev = C257, serial# = 7607292 tveeprom: tuner = Philips FM1216 ME MK3 (idx = 57, type = 38) tveeprom: tuner fmt = PAL(B/G) PAL(I) SECAM(L/L) PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) tveeprom: audio_processor = MSP3410D (type = 5) ivtv: i2c attach [client=tveeprom[50],ok] ivtv: Tuner Type 38, Tuner formats 0x00400e17, Radio: yes, Model 0x008d2557, Revision 0x0001 ivtv: PAL tuner detected ivtv: Radio detected tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 ivtv: i2c attach [client=(tuner unset),ok] cx25840: Ignoring new-style parameters in presence of obsolete ones cx25840: starting probe for adapter ivtv i2c driver #0 (0x10005) cx25840: detecting cx25840 client on address 0x88 cx25840: cx25843-23 found. Initializing... cx25840: requesting /lib/modules/HcwMakoA.ROM cx25840: firmware loaded ivtv: i2c attach [client=cx25840[50],ok] wm8775: Ignoring new-style parameters in presence of obsolete ones ivtv: i2c attach [client=wm8775[50],ok] ivtv: Encoder revision: 0x02050032 ivtv: Encoder Firmware may be buggy, use version 0x02040011 ivtv: Configuring WinTV PVR 150 card with 5 streams ivtv: Registered v4l2 device for encoder MPEG minor 0 ivtv: Create DMA encoder MPEG stream: 0 x 32768 buffers (0KB total) ivtv: Registered v4l2 device for encoder YUV minor 32 ivtv: Create DMA encoder YUV stream: 0 x 12960 buffers (0KB total) ivtv: Registered v4l2 device for encoder VBI minor 224 ivtv: Create DMA encoder VBI stream: 0 x 12740 buffers (0KB total) ivtv: Registered v4l2 device for encoder PCM audio minor 24 ivtv: Create DMA encoder PCM audio stream: 0 x 4608 buffers (0KB total) ivtv: Registered v4l2 device for encoder radio minor 64 ivtv: Create encoder radio stream ivtv: Setting Tuner 38 tuner: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3)) by ivtv i2c driver #0 cx25840: decoder set norm PAL cx25840: decoder set input (6) cx25840: now setting Tuner input cx25840: set audio input (0) ivtv: Switching standard to PAL. cx25840: decoder set norm PAL ivtv: Initialized WinTV PVR 150, card #0 ivtv: END INIT IVTV ivtv: ivtv_enc_thread: pid = 12543, itv = 0xe0e8e880 ivtv: ivtv_enc_vbi_thread: pid = 12544, itv = 0xe0e8e880 cx25840: decoder set size: ignoring bad config request Hsrc=720 Vsrc=576 width=720 height=576 cx25840: decoder set picture bright=128 contrast=63 saturation=64 hue=0 cx25840: decoder set picture bright=128 contrast=63 saturation=63 hue=0 cx25840: decoder set picture bright=127 contrast=63 saturation=63 hue=0 cx25840: decoder set picture bright=127 contrast=63 saturation=63 hue=0 cx25840: decoder disable output cx25840: decoder enable output cx25840: decoder set norm PAL cx25840: decoder set input (6) cx25840: now setting Tuner input cx25840: set audio input (0) ivtv: Sliced VBI not supported for cx25840 so no vbi re-insertion possible yet -- --- WEB-fx
Re: [ivtv-devel] VBI (again)
Morten Rønseth wrote: I just sussed it. My kernel version is 2.6.8.1-12mdk - tda9887.c, line 548 defines msleep_iterruptible iff version is 2.6.7 or older. Don't know why, but I seem to need it, version 2.6.8 ( can't believe I haven't seen this before...). I changed the 7 to an 8 and voila! it compiles, installs and loads...:-) Good work! Now comes the real test. Back out the magic patch I posted for you, unload all the relevant modules and see if it goes from scratch. Differences from the current ivtv release should be: -- cx25840 line 221 should be commented out. (ACFG_DIS(0x01)) -- tda9887 should have msleep_interuptible defined for = 2.6.8 -- your modprobe.d should have `options ivtv tda9887=0` The first two things I will roll up with my volume control patch, so you won't have to worry about patching every version, but it would be cool to know if they're going to work. If you get scratchy sound or a lot of ticking, add options: options tda9887 port1=0 port2=0 I'd also like to thank you for sticking with this while we work out the problems. You've helped tremendously. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Bryan Mayland wrote: Morten Rønseth wrote: I just sussed it. My kernel version is 2.6.8.1-12mdk - tda9887.c, line 548 defines msleep_iterruptible iff version is 2.6.7 or older. Don't know why, but I seem to need it, version 2.6.8 ( can't believe I haven't seen this before...). I changed the 7 to an 8 and voila! it compiles, installs and loads...:-) Good work! Now comes the real test. Back out the magic patch I posted for you, unload all the relevant modules and see if it goes from scratch. Differences from the current ivtv release should be: -- cx25840 line 221 should be commented out. (ACFG_DIS(0x01)) -- tda9887 should have msleep_interuptible defined for = 2.6.8 -- your modprobe.d should have `options ivtv tda9887=0` The first two things I will roll up with my volume control patch, so you won't have to worry about patching every version, but it would be cool to know if they're going to work. OK, done that - even did cold boot :-) Only thing that worries me now is that the system is completely silent for the first 30 secs or so of watching TV. After that sound returns and all seems OK. Wouldn't it be easier/better to decide whether msleep_interruptible should be defined based upon what is in linux/delay.h? I might be wrong but I believe that's where it should be found if present in system headers. Also, I now start my system like this: /sbin/modprobe tda9887 debug=1 /sbin/modprobe -v ivtv ivtv_std=2 tda9887=0 the I do: /usr/local/bin/ivtvctl -d /dev/video0 -u 1 -f width=720,height=576 -p 6/usr/local/bin/ivtvctl -d /dev/video0 -c dnr_mode=0 /usr/local/bin/ivtvctl -d /dev/video0 -c dnr_temporal=4 /usr/local/bin/ivtvctl -d /dev/video0 -c dnr_spatial=4 If you get scratchy sound or a lot of ticking, add options: options tda9887 port1=0 port2=0 No anomalities apart from the tardy sound. I'd also like to thank you for sticking with this while we work out the problems. You've helped tremendously. Well, let ME thank YOU. I now have a much more robust system and I can (once again) take part in any new fixes and implemantations in the driver as a whole. Here's what my dmesg now shows (why are some cx25840 operations repeated...?): tda9887: Unknown parameter `debug' tda9887: Ignoring new-style parameters in presence of obsolete ones Linux video capture interface: v1.00 ivtv: START INIT IVTV ivtv: version 0.3.6 (r) loading ivtv: Linux version: 2.6.8.1-12mdk 686 gcc-3.4 ivtv: In case of problems please include the debug info ivtv: between the START INIT IVTV and END INIT IVTV lines when ivtv: mailing the ivtv-devel mailinglist. ivtv: Autodetected WinTV PVR 150 card ivtv: Found an iTVC16 based chip ivtv: Unreasonably low latency timer, setting to 64 (was 32) ivtv: VIA PCI device: 0x3205 vendor: 0x1106 tda9885/6/7: chip found @ 0x86 ivtv: i2c attach [client=tda9887,ok] tveeprom: Ignoring new-style parameters in presence of obsolete ones tveeprom: Hauppauge: model = 26559, rev = C257, serial# = 7607292 tveeprom: tuner = Philips FM1216 ME MK3 (idx = 57, type = 38) tveeprom: tuner fmt = PAL(B/G) PAL(I) SECAM(L/L) PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) tveeprom: audio_processor = MSP3410D (type = 5) ivtv: i2c attach [client=tveeprom[50],ok] ivtv: Tuner Type 38, Tuner formats 0x00400e17, Radio: yes, Model 0x008d2557, Revision 0x0001 ivtv: Radio detected tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 ivtv: i2c attach [client=(tuner unset),ok] cx25840: Ignoring new-style parameters in presence of obsolete ones cx25840: starting probe for adapter ivtv i2c driver #0 (0x10005) cx25840: detecting cx25840 client on address 0x88 cx25840: cx25843-23 found. Initializing... cx25840: requesting /lib/modules/HcwMakoA.ROM cx25840: firmware loaded ivtv: i2c attach [client=cx25840[50],ok] wm8775: Ignoring new-style parameters in presence of obsolete ones ivtv: i2c attach [client=wm8775[50],ok] ivtv: Encoder revision: 0x02050032 ivtv: Encoder Firmware may be buggy, use version 0x02040011 ivtv: Configuring WinTV PVR 150 card with 5 streams ivtv: Registered v4l2 device for encoder MPEG minor 0 ivtv: Create DMA encoder MPEG stream: 0 x 32768 buffers (0KB total) ivtv: Registered v4l2 device for encoder YUV minor 32 ivtv: Create DMA encoder YUV stream: 0 x 12960 buffers (0KB total) ivtv: Registered v4l2 device for encoder VBI minor 224 ivtv: Create DMA encoder VBI stream: 0 x 12740 buffers (0KB total) ivtv: Registered v4l2 device for encoder PCM audio minor 24 ivtv: Create DMA encoder PCM audio stream: 0 x 4608 buffers (0KB total) ivtv: Registered v4l2 device for encoder radio minor 64 ivtv: Create encoder radio stream ivtv: Setting Tuner 38 tuner: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3)) by ivtv i2c driver #0 cx25840: decoder set norm PAL cx25840: decoder set input (6) cx25840: now setting Tuner input cx25840: set audio input (0) ivtv:
Re: [ivtv-devel] VBI (again)
Hi Bryan, Good work! Now comes the real test. Back out the magic patch I posted for you, unload all the relevant modules and see if it goes from scratch. Differences from the current ivtv release should be: -- cx25840 line 221 should be commented out. (ACFG_DIS(0x01)) done -- tda9887 should have msleep_interuptible defined for = 2.6.8 done -- your modprobe.d should have `options ivtv tda9887=0` I don't use modprobe.d :-) But I give the option to ivtv when it loads. The first two things I will roll up with my volume control patch, so you won't have to worry about patching every version, but it would be cool to know if they're going to work. OK, done that - even did cold boot :-) Only thing that worries me now is that the system is completely silent for the first 30 secs or so of watching TV. After that sound returns and all seems OK. Seems I was wrong. Without the black magic hack, every other channel is mute, whilst others are audible as they should be. No pattern I could find, but I'm sure there is a one. WITH the hack, all is OK. Cheers, -Morten -- --- WEB-fx http://www.webfx.no Morten Lerskau Rønseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Tårnåsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Morten Rønseth wrote: Seems I was wrong. Without the black magic hack, every other channel is mute, whilst others are audible as they should be. No pattern I could find, but I'm sure there is a one. WITH the hack, all is OK. Can you try it without the hack and: options tda9887 port1=0 port2=0 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Hi Bryan, Bryan Mayland wrote: Morten Rønseth wrote: Seems I was wrong. Without the black magic hack, every other channel is mute, whilst others are audible as they should be. No pattern I could find, but I'm sure there is a one. WITH the hack, all is OK. Can you try it without the hack and: options tda9887 port1=0 port2=0 I get tda9887: Unknown parameter `port1' tda9887: Ignoring new-style parameters in presence of obsolete ones --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel Cheers, -Morten -- --- WEB-fx http://www.webfx.no Morten Lerskau Rønseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Tårnåsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Morten Rønseth wrote: Can you try it without the hack and: options tda9887 port1=0 port2=0 I get tda9887: Unknown parameter `port1' tda9887: Ignoring new-style parameters in presence of obsolete ones Ack, you're kidding me. Well now I'm just confused (as if this whole thing wasn't confusing enough already). Anyone have an idea where my port parameters went? You don't have multiple copies of this somewhere do you? (try find /lib/modules/`uname -r` -name tda9887*) --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Hi Bryan, Bryan Mayland wrote: Morten Rønseth wrote: Can you try it without the hack and: options tda9887 port1=0 port2=0 I get tda9887: Unknown parameter `port1' tda9887: Ignoring new-style parameters in presence of obsolete ones Ack, you're kidding me. Well now I'm just confused (as if this whole thing wasn't confusing enough already). Anyone have an idea where my port parameters went? You don't have multiple copies of this somewhere do you? (try find /lib/modules/`uname -r` -name tda9887*) Hah! I found /lib/modules/2.6.8.1-12mdk/kernel/drivers/media/video/tda9887.ko.gz - and I thought I'd gotten rid of all doubles... Would this one interfer? I'll take a closer look tomorrow, too late now...going to bed, I'm afraid. But we're close! :-) Cheers, -Morten --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel -- --- WEB-fx http://www.webfx.no Morten Lerskau Rønseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Tårnåsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Morten Rønseth wrote: Hah! I found /lib/modules/2.6.8.1-12mdk/kernel/drivers/media/video/tda9887.ko.gz - and I thought I'd gotten rid of all doubles... Would this one interfer? I'll take a closer look tomorrow, too late now...going to bed, I'm afraid. It certainly could. Can't wait to see what happens tomorrow, I think we're close too. Good night! --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Hi, Just couldn't stay away... Bryan Mayland wrote: Morten Rønseth wrote: Hah! I found /lib/modules/2.6.8.1-12mdk/kernel/drivers/media/video/tda9887.ko.gz - and I thought I'd gotten rid of all doubles... Would this one interfer? I'll take a closer look tomorrow, too late now...going to bed, I'm afraid. It certainly could. Can't wait to see what happens tomorrow, I think we're close too. Good night! Removed rouge module, but still get same message after warm boot: tda9887: Unknown parameter `port1' tda9887: Ignoring new-style parameters in presence of obsolete ones .. I'll try cold boot tomorrow. Cheers, -Morten --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel -- --- WEB-fx http://www.webfx.no Morten Lerskau Rønseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Tårnåsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Bryan Mayland wrote: Morten Rønseth wrote: Hah! I found /lib/modules/2.6.8.1-12mdk/kernel/drivers/media/video/tda9887.ko.gz - and I thought I'd gotten rid of all doubles... Would this one interfer? I'll take a closer look tomorrow, too late now...going to bed, I'm afraid. It certainly could. Can't wait to see what happens tomorrow, I think we're close too. Good night! I'm guessing that the I2C defined parameters are done in the 'obsolete style' in Morten's kernel version, causing it to ignore all non-obsoletely-defined ones. So, either he upgrades to a new kernel, or someone adds the old style paramter definitions, also it seems the other modules (since they all use i2c headers) should have their ifdefs changed to use the obsolete style if they are on kernel = 2.6.8. Actually, there's probably no reason why he can't use the tda9887 that came with his kernel... -- Tyler Trafford --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Hi, Bryan Mayland wrote: Tyler Trafford wrote: If 0.3.5 is the last, then this must be more 'black magic' (tda9887) fallout. I would think that too, but that only messed with the audio. His picture is wonky too. This could be unrelated to your problem, but these are not messages from the cx25840.ko included with 0.3.6q. This is true though. Might want to do a find /lib/modules/`uname -r` -name cx25840* And see if you've got more than one version. Here is the output: [EMAIL PROTECTED] IVTV]$ sudo find /lib/modules/`uname -r` -name cx25840* /lib/modules/2.6.8.1-12mdk/extra/cx25840.ko There is only one. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel -- --- WEB-fx http://www.webfx.no Morten Lerskau Rønseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Tårnåsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Tyler Trafford wrote: Bryan Mayland wrote: Tyler Trafford wrote: If 0.3.5 is the last, then this must be more 'black magic' (tda9887) fallout. I would think that too, but that only messed with the audio. His picture is wonky too. If he loads 0.3.5, unloads, and then loads 0.3.5a - it works, but 0.3.5a after a cold boot does not... The tda987 must be doing more there then we think. Morten: what parameters are you passing to the modules? I let ivtv decide what to load. This is how it's all started: /sbin/modprobe -v ivtv #ivtv_std=6 tda9887=0 #tuner=38 radio=1 If I remove the first hash, nothing much changes... If you want, I could send you the complete startup-script (~8k). Cheers, -Morten -- --- WEB-fx http://www.webfx.no Morten Lerskau Rnseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Trnsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477_id=16492=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Morten Rønseth wrote: This is true though. Might want to do a find /lib/modules/`uname -r` -name cx25840* And see if you've got more than one version. Here is the output: [EMAIL PROTECTED] IVTV]$ sudo find /lib/modules/`uname -r` -name cx25840* /lib/modules/2.6.8.1-12mdk/extra/cx25840.ko Well that's not good. We put our stuff in an ivtv directory, not the extra directory. When you do `make install`, do you see a line that says: make INSTALL_MOD_PATH= INSTALL_MOD_DIR=ivtv \ or does it say extra at the end of that? --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Hi, Bryan Mayland wrote: Morten Rønseth wrote: This is true though. Might want to do a find /lib/modules/`uname -r` -name cx25840* And see if you've got more than one version. Here is the output: [EMAIL PROTECTED] IVTV]$ sudo find /lib/modules/`uname -r` -name cx25840* /lib/modules/2.6.8.1-12mdk/extra/cx25840.ko Well that's not good. We put our stuff in an ivtv directory, not the extra directory. When you do `make install`, do you see a line that says: make INSTALL_MOD_PATH= INSTALL_MOD_DIR=ivtv \ or does it say extra at the end of that? It says ivtv: make INSTALL_MOD_PATH= INSTALL_MOD_DIR=ivtv \ CONFIG_VIDEO_IVTV=m -C /lib/modules/2.6.8.1-12mdk/build M=/usr/local/src/IVTV/ivtv-0.3.6p/driver modules_install I don't know where extra comes from...does it matter? Timestamp on /lib/modules/2.6.8.1-12mdk/extra/cx25840.ko is correct, it's from when I last installed the driver (friday). Cheers, -Morten --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel -- --- WEB-fx http://www.webfx.no Morten Lerskau Rønseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Tårnåsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Hi, Tyler Trafford wrote: Morten Rnseth wrote: Output from /var/log/messages: ivtv: START INIT IVTV ivtv: version 0.3.6 (q) loading ivtv: Linux version: 2.6.8.1-12mdk 686 gcc-3.4 cx25840: FW image '/lib/modules/HcwMakoA.ROM' of size 13883 loaded. cx25840: FW image md5 digest: a6f6a90a3be338cdb89d59e835798408 cx25840: FW image sha1 digest: ad2872fb98ad43b6c4afa45d239a57010edebe84 This could be unrelated to your problem, but these are not messages from the cx25840.ko included with 0.3.6q. Could it be becuase after loading 0.3.5 I only unload the ivtv module before loading 0.3.6q ? Cheers, -Morten -- --- WEB-fx http://www.webfx.no Morten Lerskau Rnseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Trnsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477_id=16492=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Morten Rønseth wrote: Could it be becuase after loading 0.3.5 I only unload the ivtv module before loading 0.3.6q ? Ah! Yes. When you rmmod only ivtv, it leaves everything else behind, so the cx25840 from 0.3.5 stays resident. Try removing that one too when you switch versions. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Hi, Bryan Mayland wrote: Morten Rønseth wrote: Could it be becuase after loading 0.3.5 I only unload the ivtv module before loading 0.3.6q ? Ah! Yes. When you rmmod only ivtv, it leaves everything else behind, so the cx25840 from 0.3.5 stays resident. Try removing that one too when you switch versions. I've just tried that - seems like it's the cx25840 module that makes anything above 0.3.5 fail. After I load 0.3.5, I unload everything except the cx25840 module (ivtv, wm8775, tveeprom tuner, in that order - anything else I should know of?), then load 0.3.6q. It works. Cheers, -Morten --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel -- --- WEB-fx http://www.webfx.no Morten Lerskau Rønseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Tårnåsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Morten Rønseth wrote:
I've just tried that - seems like it's the cx25840 module that makes
anything above 0.3.5 fail. After I load 0.3.5, I unload everything
except the cx25840 module (ivtv, wm8775, tveeprom tuner, in that
order - anything else I should know of?), then load 0.3.6q. It works.
Ok, so 0.3.5a fails too? If that's the case we can definitely
narrow down the problem. Try this patch against the current version to
see if you can use the current cx25840.
Index: cx25840-driver.c
===
--- cx25840-driver.c(revision 323)
+++ cx25840-driver.c(working copy)
@@ -427,6 +427,16 @@
CX25840_SET_PWR_DN_TUNING(pwr_dn);
}
#endif
+static int execute_wi2c(struct i2c_client *client, int addr, u8 * b,
+int len)
+{
+ int save_addr = client-addr;
+ int retval;
+ client-addr = addr;
+ retval = i2c_master_send(client, b, len);
+ client-addr = save_addr;
+ return retval;
+}
static int cx25840_command(struct i2c_client *client, unsigned int cmd, void
*arg)
{
@@ -717,6 +727,10 @@
CX25840_SET_VID_OUT_EN(enable);
CX25840_SET_PLL_CLK_OUT_EN(enable);
+{
+u8 bytes[] = { 0x00, 0x16, 0x70, 0x4a };
+execute_wi2c(client, 0x43, bytes, 4);
+}
state-enable = enable;
break;
Re: [ivtv-devel] VBI (again)
Hi, Chris Kennedy wrote: To get VBI working do this... run... ivtvctl -w cc,wss; ivtvctl -b cc,wss; ivtvctl -x 1 then turn on CC support in your TV set, so CC is displayed on output, check normal TV to confirm this is on. Then cat /dev/video0 /dev/video16 or any other form of encoding from the card and decoding that video with the card should produce CC. Thanks, Chris I just installed 0.3.6q and ran ivtvctl -w cc,wss; ivtvctl -b cc,wss; ivtvctl -x 1. here is the output: ioctl IVTV_IOC_S_VBI_PASSTHROUGH ok VBI passthrough mode set to 000c ioctl IVTV_IOC_S_VBI_MODE ok vbi service_set set to 000c ioctl IVTV_IOC_S_VBI_EMBED failed: Invalid argument Output from /var/løog/messages: ivtv: START INIT IVTV ivtv: version 0.3.6 (q) loading ivtv: Linux version: 2.6.8.1-12mdk 686 gcc-3.4 ivtv: In case of problems please include the debug info ivtv: between the START INIT IVTV and END INIT IVTV lines when ivtv: mailing the ivtv-devel mailinglist. ivtv: Autodetected WinTV PVR 150 card ivtv: Found an iTVC16 based chip ivtv: VIA PCI device: 0x3205 vendor: 0x1106 tveeprom: Hauppauge: model = 26559, rev = C257, serial# = 7607292 tveeprom: tuner = Philips FM1216 ME MK3 (idx = 57, type = 38) tveeprom: tuner fmt = PAL(B/G) PAL(I) SECAM(L/L) PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) tveeprom: audio_processor = MSP3410D (type = 5) ivtv: i2c attach [client=tveeprom[50],ok] tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 ivtv: i2c attach [client=(tuner unset),ok] cx25840: starting probe for adapter ivtv i2c driver #0 (0x10005) cx25840: detecting client on address 0x88 cx25840: writing init values cx25840: FW image '/lib/modules/HcwMakoA.ROM' of size 13883 loaded. cx25840: FW image md5 digest: a6f6a90a3be338cdb89d59e835798408 cx25840: FW image sha1 digest: ad2872fb98ad43b6c4afa45d239a57010edebe84 cx25840: Status: cx258433 (DEVICE_ID) ivtv: i2c attach [client=cx25840[50],ok] ivtv: i2c attach [client=wm8775[50],ok] ivtv: Tuner Type 38, Tuner formats 0x00400e17, Radio: yes, Model 0x008d2557, Revision 0x0001 ivtv: PAL tuner detected ivtv: Radio detected ivtv: Encoder revision: 0x02050032 ivtv: Encoder Firmware may be buggy, use version 0x02040011 ivtv: Configuring WinTV PVR 150 card with 5 streams ivtv: Registered v4l2 device for encoder MPEG minor 0 ivtv: Create DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv: Registered v4l2 device for encoder YUV minor 32 ivtv: Create DMA encoder YUV stream: 161 x 12960 buffers (2048KB total) ivtv: Registered v4l2 device for encoder VBI minor 224 ivtv: Create DMA encoder VBI stream: 164 x 12740 buffers (2048KB total) ivtv: Registered v4l2 device for encoder PCM audio minor 24 ivtv: Create DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) ivtv: Registered v4l2 device for encoder radio minor 64 ivtv: Create encoder radio stream ivtv: Setting Tuner 38 tuner: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3)) by ivtv i2c driver #0 cx25840: decoder set norm PAL cx25840: decoder set input (6) cx25840: Tuner Input ivtv: Switching standard to PAL. cx25840: decoder set norm PAL ivtv: Initialized WinTV PVR 150, card #0 ivtv: END INIT IVTV BTW, I'd love for the 0.3.6 series to be able to start my pvr150 correctly after a cold boot - the last version that does is 0.3.5. (re pvr150 only capturing noise). :-) Cheers, -Morten -- --- WEB-fx Morten Lerskau Rønseth http://www.webfx.no Odinsvei 15c mailto:[EMAIL PROTECTED] 1413 TårnåsenTlf.: (47) 6680 9191 Norway Mob : (47) 9343 4357 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Morten Rønseth wrote: ioctl IVTV_IOC_S_VBI_EMBED failed: Invalid argument This is because the cx25840-based cards (150 and 500) don't have sliced VBI support in the driver (or at least so says the error message in the code): ivtv: Sliced VBI not supported for cx25840 so no vbi re-insertion possible yet BTW, I'd love for the 0.3.6 series to be able to start my pvr150 correctly after a cold boot - the last version that does is 0.3.5. (re pvr150 only capturing noise). :-) What kind of noise are you seeing? A screen full of static or is it more like the doublevision problem described in the thread ivtv-0.3.6m: PAL doublevision problems --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Hi Bryan, Bryan Mayland wrote: Morten Rønseth wrote: ioctl IVTV_IOC_S_VBI_EMBED failed: Invalid argument This is because the cx25840-based cards (150 and 500) don't have sliced VBI support in the driver (or at least so says the error message in the code): ivtv: Sliced VBI not supported for cx25840 so no vbi re-insertion possible yet Ah - I see. BTW, I'd love for the 0.3.6 series to be able to start my pvr150 correctly after a cold boot - the last version that does is 0.3.5. (re pvr150 only capturing noise). :-) What kind of noise are you seeing? A screen full of static or is it more like the doublevision problem described in the thread ivtv-0.3.6m: PAL doublevision problems It's an almost black screen, with noisy patterns on the bottom 20% or so - no image, no sound. First loading 0.3.5 upon startup then unloading it and then loading 0.3.6 (any will do) works. Cheers, -Morten -- --- WEB-fx http://www.webfx.no Morten Lerskau Rønseth mailto:[EMAIL PROTECTED] Odinsvei 15c +47 6680 9191 1413 Tårnåsen+47 9343 4357 Norway --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Bryan Mayland wrote: Morten Rønseth wrote: BTW, I'd love for the 0.3.6 series to be able to start my pvr150 correctly after a cold boot - the last version that does is 0.3.5. (re pvr150 only capturing noise). :-) What kind of noise are you seeing? A screen full of static or is it more like the doublevision problem described in the thread ivtv-0.3.6m: PAL doublevision problems If 0.3.5 is the last, then this must be more 'black magic' (tda9887) fallout. -- Tyler Trafford --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Tyler Trafford wrote: If 0.3.5 is the last, then this must be more 'black magic' (tda9887) fallout. I would think that too, but that only messed with the audio. His picture is wonky too. This could be unrelated to your problem, but these are not messages from the cx25840.ko included with 0.3.6q. This is true though. Might want to do a find /lib/modules/`uname -r` -name cx25840* And see if you've got more than one version. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
Bryan Mayland wrote: Tyler Trafford wrote: If 0.3.5 is the last, then this must be more 'black magic' (tda9887) fallout. I would think that too, but that only messed with the audio. His picture is wonky too. If he loads 0.3.5, unloads, and then loads 0.3.5a - it works, but 0.3.5a after a cold boot does not... The tda987 must be doing more there then we think. Morten: what parameters are you passing to the modules? -- Tyler Trafford --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
To get VBI working do this... run... ivtvctl -w cc,wss; ivtvctl -b cc,wss; ivtvctl -x 1 then turn on CC support in your TV set, so CC is displayed on output, check normal TV to confirm this is on. Then cat /dev/video0 /dev/video16 or any other form of encoding from the card and decoding that video with the card should produce CC. Thanks, Chris Daniel Segel wrote: I have no answers, but I wanted to chime in and let the developers know that I am yet another user who is very interested in Closed Caption support via the PVR-350 as well. I'm willing to wait if it's coming, but if there's no indication that it's at least being worked on then I'll have to either switch video cards (capture cards? Where exactly is the problem?) or give up on MythTV altogether (which is what I bought the PVR-350 for.) Daniel GREG AMY LINDLEY wrote: Hi, I have looked at the README.vbi and installed the latest ivtv drivers. I have the following line in my /etc/rc.local: /usr/bin/ivtvctl -w wss,cc,vps I believe from reading this that the CC data should be going to the TV out on my PVR350 at this point. Unfortunately, I don't seem to see anything. I am not sure what else I may be missing. I have tried using mplayer and xine, but neither seems to help. I tried different DVDs/VOBs so I don't believe that to be the issue. I see that the VBI threads do get initialized in the /var/log/messages file. Not sure what I am missing. I am certainly willing to run tests or help out however I can to get this working. Is there anyone willing to help me out? Thanks, Greg --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel -- === Chris Kennedy [EMAIL PROTECTED] --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
I don't need to leave the passthrough option on for normal operation (i.e. watching pre-recorded shows via MythTV), do I? I do get some kind of CC signal coming through using the options you listed, but it's really garbled and only about 5% of it is understandable. Also, my TV is 4:3 - do I still need the wss flag as well? My video source is a DISH Network satellite receiver. Daniel Chris Kennedy wrote: To get VBI working do this... run... ivtvctl -w cc,wss; ivtvctl -b cc,wss; ivtvctl -x 1 then turn on CC support in your TV set, so CC is displayed on output, check normal TV to confirm this is on. Then cat /dev/video0 /dev/video16 or any other form of encoding from the card and decoding that video with the card should produce CC. Thanks, Chris Daniel Segel wrote: I have no answers, but I wanted to chime in and let the developers know that I am yet another user who is very interested in Closed Caption support via the PVR-350 as well. I'm willing to wait if it's coming, but if there's no indication that it's at least being worked on then I'll have to either switch video cards (capture cards? Where exactly is the problem?) or give up on MythTV altogether (which is what I bought the PVR-350 for.) Daniel GREG AMY LINDLEY wrote: Hi, I have looked at the README.vbi and installed the latest ivtv drivers. I have the following line in my /etc/rc.local: /usr/bin/ivtvctl -w wss,cc,vps I believe from reading this that the CC data should be going to the TV out on my PVR350 at this point. Unfortunately, I don't seem to see anything. I am not sure what else I may be missing. I have tried using mplayer and xine, but neither seems to help. I tried different DVDs/VOBs so I don't believe that to be the issue. I see that the VBI threads do get initialized in the /var/log/messages file. Not sure what I am missing. I am certainly willing to run tests or help out however I can to get this working. Is there anyone willing to help me out? Thanks, Greg --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] VBI (again)
I have no answers, but I wanted to chime in and let the developers know that I am yet another user who is very interested in Closed Caption support via the PVR-350 as well. I'm willing to wait if it's coming, but if there's no indication that it's at least being worked on then I'll have to either switch video cards (capture cards? Where exactly is the problem?) or give up on MythTV altogether (which is what I bought the PVR-350 for.) Daniel GREG AMY LINDLEY wrote: Hi, I have looked at the README.vbi and installed the latest ivtv drivers. I have the following line in my /etc/rc.local: /usr/bin/ivtvctl -w wss,cc,vps I believe from reading this that the CC data should be going to the TV out on my PVR350 at this point. Unfortunately, I don't seem to see anything. I am not sure what else I may be missing. I have tried using mplayer and xine, but neither seems to help. I tried different DVDs/VOBs so I don't believe that to be the issue. I see that the VBI threads do get initialized in the /var/log/messages file. Not sure what I am missing. I am certainly willing to run tests or help out however I can to get this working. Is there anyone willing to help me out? Thanks, Greg --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
