Re: [linux-dvb] HDTV performance issues.
I use mplayer playing my HDTV program these days. >> And It give me a good effect. It's very intersting ! Could you give more detail information about your system - which CPU, video card, dvb-s2 card, software and channels do you use ?could you show MPlayer logs. Igor ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Asys P7131 Hybrid: DVB out of range
Am Mittwoch, den 05.09.2007, 16:36 -0700 schrieb Trent Piepho: > On Thu, 6 Sep 2007, hermann pitton wrote: > > Am Mittwoch, den 05.09.2007, 13:29 +0200 schrieb Paolo Dell'Aquila: > > > Than I've done some test with Mythtv and auto-scanning > > > for channels... and now... > > > > > > ...now I'm having the following (BIG) problem: > > > dvb-t doesn't work anymore (also in kaffeiene or tzap). > > > > > > dmesg has the following error: > > > DVB: frontend 0 frequency 2147483647 out of range (5100..85800) > > > > That sounds really mad, especially as you are in freq. limits of the > > tda8275 and not of the tda8275a, which for sure you have. > > The limits are comming from the tda10046 info. I think the correct thing > to do here is to not have the tda1004x driver define frequency limits, as > it's the tuner that has the limits. You are totally right. /me and others tried on this over and over again. For some price ..., not worth at all! f* > But, 2147483647 is not a valid DVB-T frequency. It looks like some random > number. Hopefully, that is the little remaining soon gone. Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HDTV performance issues.
kevin liu wrote: > By the way, HDTV don't need your system to have mpeg4 processing > ability, it only need mpeg2 decoder. While this is currently, and will be for some time to come, true for ATSC, it does not equally apply to other standards. Please see the very first message of this thread, as it outlines the source and standard being acquired. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] HDTV performance issues.
Hi, I think your computer can play HDTV program properly. I use mplayer playing my HDTV program these days. And It give me a good effect. By the way, HDTV don't need your system to have mpeg4 processing ability, it only need mpeg2 decoder. And you can give your mplayer a more proper config, you can use the -vo option to change the video out device and -vc option to change the decoder. Please try it and hope it a help. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Asys P7131 Hybrid: DVB out of range
Trent Piepho wrote: > On Thu, 6 Sep 2007, hermann pitton wrote: > > Am Mittwoch, den 05.09.2007, 13:29 +0200 schrieb Paolo Dell'Aquila: > > > Than I've done some test with Mythtv and auto-scanning > > > for channels... and now... > > > > > > ...now I'm having the following (BIG) problem: > > > dvb-t doesn't work anymore (also in kaffeiene or tzap). > > > > > > dmesg has the following error: > > > DVB: frontend 0 frequency 2147483647 out of range (5100..85800) > > > > That sounds really mad, especially as you are in freq. limits of the > > tda8275 and not of the tda8275a, which for sure you have. > > The limits are comming from the tda10046 info. I think the correct thing > to do here is to not have the tda1004x driver define frequency limits, as > it's the tuner that has the limits. Nak. You must not remove these limits unless you make sure that all tuner drivers which might be attached to this demod have non-zero frequency limits. > But, 2147483647 is not a valid DVB-T frequency. It looks like some random > number. Ack, this frequency is bogus. The application must be fixed. CU Oliver -- VDR Remote Plugin 0.3.9: http://www.escape-edv.de/endriss/vdr/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Asys P7131 Hybrid: DVB out of range
Trent Piepho wrote: > On Thu, 6 Sep 2007, hermann pitton wrote: >> Am Mittwoch, den 05.09.2007, 13:29 +0200 schrieb Paolo Dell'Aquila: >>> Than I've done some test with Mythtv and auto-scanning >>> for channels... and now... >>> >>> ...now I'm having the following (BIG) problem: >>> dvb-t doesn't work anymore (also in kaffeiene or tzap). >>> >>> dmesg has the following error: >>> DVB: frontend 0 frequency 2147483647 out of range (5100..85800) >> That sounds really mad, especially as you are in freq. limits of the >> tda8275 and not of the tda8275a, which for sure you have. > > The limits are comming from the tda10046 info. I think the correct thing > to do here is to not have the tda1004x driver define frequency limits, as > it's the tuner that has the limits. > > But, 2147483647 is not a valid DVB-T frequency. It looks like some random > number. It's not that random: 2147483647 equals INT_MAX and also LONG_MAX on 32 bit systems. Quoting from the manpage of strtol(): The strtol() function returns the result of the conversion, unless the value would underflow or overflow. If an underflow occurs, strtol() returns LONG_MIN. If an overflow occurs, strtol() returns LONG_MAX. In both cases, errno is set to ERANGE. Precisely the same holds for strtoll() (with LLONG_MIN and LLONG_MAX instead of LONG_MIN and LONG_MAX). My conclusion: Your channels.conf contains invalid frequency values. Tzap uses strtol() to parse those values and returns LONG_MAX. The error could be reported to the user by applying the attached patch. Regards, Andreas diff -r 1923f74d97ae util/szap/azap.c --- a/util/szap/azap.c Wed Jun 27 19:46:43 2007 +0200 +++ b/util/szap/azap.c Thu Sep 06 02:47:52 2007 +0200 @@ -104,6 +104,8 @@ int parse_int(int fd, int *val) }; *val = strtol(number, NULL, 10); + if (errno == ERANGE) + return -4; return 0; } diff -r 1923f74d97ae util/szap/tzap.c --- a/util/szap/tzap.c Wed Jun 27 19:46:43 2007 +0200 +++ b/util/szap/tzap.c Thu Sep 06 02:47:52 2007 +0200 @@ -180,6 +180,8 @@ int parse_int(int fd, int *val) }; *val = strtol(number, NULL, 10); + if (errno == ERANGE) + return -4; return 0; } ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Asys P7131 Hybrid: DVB out of range
On Thu, 6 Sep 2007, hermann pitton wrote:
> Am Mittwoch, den 05.09.2007, 13:29 +0200 schrieb Paolo Dell'Aquila:
> > Than I've done some test with Mythtv and auto-scanning
> > for channels... and now...
> >
> > ...now I'm having the following (BIG) problem:
> > dvb-t doesn't work anymore (also in kaffeiene or tzap).
> >
> > dmesg has the following error:
> > DVB: frontend 0 frequency 2147483647 out of range (5100..85800)
>
> That sounds really mad, especially as you are in freq. limits of the
> tda8275 and not of the tda8275a, which for sure you have.
The limits are comming from the tda10046 info. I think the correct thing
to do here is to not have the tda1004x driver define frequency limits, as
it's the tuner that has the limits.
But, 2147483647 is not a valid DVB-T frequency. It looks like some random
number.
---
# HG changeset patch
# User Trent Piepho <[EMAIL PROTECTED]>
# Date 1189035269 25200
# Node ID 0f6fa7f9db1241806c7d91ff6a9775f12fe1d6dd
# Parent 1387dc197077ad89fdc4014c927c4d8c9ae56193
tda1004x: Remove frequency limits
From: Trent Piepho <[EMAIL PROTECTED]>
The frequency limits are defined by the tuner. The demodulator's input comes
in at a fixed intermediate frequency, and it doesn't care or know what
frequency it was at originally.
Signed-off-by: Trent Piepho <[EMAIL PROTECTED]>
diff -r 1387dc197077 -r 0f6fa7f9db12
linux/drivers/media/dvb/frontends/tda1004x.c
--- a/linux/drivers/media/dvb/frontends/tda1004x.c Sun Sep 02 07:56:18
2007 +0100
+++ b/linux/drivers/media/dvb/frontends/tda1004x.c Wed Sep 05 16:34:29
2007 -0700
@@ -1216,8 +1216,6 @@ static struct dvb_frontend_ops tda10045_
.info = {
.name = "Philips TDA10045H DVB-T",
.type = FE_OFDM,
- .frequency_min = 5100,
- .frequency_max = 85800,
.frequency_stepsize = 17,
.caps =
FE_CAN_FEC_1_2 | FE_CAN_FEC_2_3 | FE_CAN_FEC_3_4 |
@@ -1275,8 +1273,6 @@ static struct dvb_frontend_ops tda10046_
.info = {
.name = "Philips TDA10046H DVB-T",
.type = FE_OFDM,
- .frequency_min = 5100,
- .frequency_max = 85800,
.frequency_stepsize = 17,
.caps =
FE_CAN_FEC_1_2 | FE_CAN_FEC_2_3 | FE_CAN_FEC_3_4 |
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] New Card: Compro VideoMate S220 DVB-T
Hi Richard, Am Mittwoch, den 05.09.2007, 19:11 +0100 schrieb Richard (MQ): > Richard (MQ) wrote: > > Hi List, > > > > The Compro VideoMate T200,T200a and T300 are listed at > > http://linuxtv.org/hg/v4l-dvb/file/18f323a05fbe/linux/Documentation/video4linux/CARDLIST.saa7134 > > - but no T220 > > > > It's a DVB-T card based on SAA7130 and MT352, incorrectly identified in > > OpenSuSE 10.3 (Beta 2) as "Compro Videomate DVB-T200 [185b:c901]" (which > > confused me immensely, because that was what I thought I'd bought, but > > was wrong!). Needless to say, config as a T200 doesn't work. > > > > Is there any chance of support for this card please? Can I do anything > > to help? > > > > PS - This is a new thread spun off from "New Card: Compro VideoMate > > S300/S350 DVB-S" as I'd rather hijacked it... > > The following transferred from S300/S350 thread as mentioned above: > > > > Am Dienstag, den 04.09.2007, 09:19 +0200 schrieb Jan Louw: > >>> >> > If it's a T220 I think you're out of luck. Check out > >>> >> > > http://linuxtv.org/hg/v4l-dvb/file/18f323a05fbe/linux/Documentation/video4linux/CARDLIST.saa7134 > > >>> >> > for a list of cards (should be somewhere under > >>> >> > /usr/src/linux/Documentation as well). The Compro VideoMate > T200,T200a > >>> >> > and T300 is listed, but no T220. I did see some T220 posts a > while back. > >>> >> > Maybe they will be of some use to you. > >>> >> > > >>> >> > What is strange is that your card is not detected as UNKNOWN. > Maybe it's > >>> >> > because the vendor:product of 185b:c901 is the same as the > T200's or > >>> >> > maybe YaST added an 'options saa7134 card=72' somewhere... > > > > > > If again a card with same PCI subsystem ID appears, like now, it should > > > fall through the eeprom detection Hartmut has added and print a warning > > > about "unknow tuner stuff". You can override it then with the > > > card=number insmod option. > > Without card=n insmod option, the card is wrongly autodetected as > DVB-T200 (hence my confusion in the earlier thread), and as you suggest > an "Unexpected tuner type" message comes up - this with "options saa7134 > i2c_scan=1" in /etc/modprobe.conf.local > > > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130/34: v4l2 driver version > 0.2.14 loaded > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: found at :00:0c.0, > rev: 1, irq: 18, latency: 32, mmio: 0xe200 > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: subsystem: 185b:c901, > board: Compro Videomate DVB-T200 [card=71,autodetected] > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: board init: gpio is 843f00 > Sep 5 19:13:36 103-Beta2-2 kernel: input: saa7134 IR (Compro Videomate > DV as /class/input/input9 > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 00: 5b 18 01 > c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 10: 00 ff 86 > 0f ff 20 ff ff ff ff ff ff ff ff ff ff > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 20: 01 40 01 > 03 03 ff 03 01 08 ff 00 88 ff ff ff ff > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 30: ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 40: ff d5 00 > c4 86 1e ff ff ff ff ff ff ff ff ff ff > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 50: ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff cb > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 60: 30 ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 70: ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c scan: found device @ > 0x1e [???] > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c scan: found device @ > 0xa0 [eeprom] > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c scan: found device @ > 0xc4 [???] > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c scan: found device @ > 0xd0 [???] > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: Unexpected tuner type > info: d5 in eeprom > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: registered device video0 > [v4l2] > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: registered device vbi0 > Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]/dvb: frontend > initialization failed > > "modprobe mt352" does nothing AFAICT, even when "debug=1" is added > > I can readily try the mercurial source build if that might help, I'm > > currently using kernel 2.6.22.3 (OpenSuSE 10.3 beta 2) > > > > Where do I find the list of "saa7134 card=x" - is it in that source > > code somewhere? > > > > > Latest always in mercurial saa7134.h and Documentation/saa7134.CARDLIST, > > > but won't help. Best approach so far was by Murray Graham I guess. > > > http://www.linuxtv.org/pipermail/linux-dvb/2007-July/019030.html > > > > > > At least a read of the qt1010 register 0x29 returned 0x39, if this is > > > safe for the tuner ID. Think 0xd5 for the tuner ID in the eepro
Re: [linux-dvb] Asys P7131 Hybrid: DVB out of range
Hi Paolo, Am Mittwoch, den 05.09.2007, 13:29 +0200 schrieb Paolo Dell'Aquila: > This morning I upgraded the kernel of my linux box. > After that I cloned v4l-dvb and compiled everything. I've done it > because couldn't watch digital tv with mplayer but only with > kaffeine. > Mplayer error was: > vb_streaming_read, attempt N. 6 failed with errno 0 when reading ... no such issues here. > So I tried to update bit I didn't solve the problem. > > > Than I've done some test with Mythtv and auto-scanning > for channels... and now... > > ...now I'm having the following (BIG) problem: > dvb-t doesn't work anymore (also in kaffeiene or tzap). > > dmesg has the following error: > DVB: frontend 0 frequency 2147483647 out of range (5100..85800) That sounds really mad, especially as you are in freq. limits of the tda8275 and not of the tda8275a, which for sure you have. > After this mess up, analogical TV is no more properly working, before > was really perfect. > > Going crazy... > > > thank you for your help. > > > P.S. > I would like to know is some of you could use a patch cable between > P7131 and motherboard for listen TV. I've tried sever time but no sound > at all and I have to use sox or aplay. Yes, I do this without any problems, but on the prior P7131 Dual without LNA. From the bottom, left is left and right is right and the two pins in the middle are ground. > > Some information about my system: > SO: Ubuntu 7.07 - Linux linux 2.6.20-16-generic > > dmesg: > [...] > [ 18.020064] saa7130/34: v4l2 driver version 0.2.14 loaded > [ 18.020132] ACPI: PCI Interrupt :01:09.0[A] -> GSI 17 (level, > low) -> IRQ 17 > [ 18.020144] saa7133[0]: found at :01:09.0, rev: 209, irq: 17, > latency: 64, mmio: 0xcdcff800 > [ 18.020152] saa7133[0]: subsystem: 1043:4876, board: ASUSTeK P7131 > Hybrid [card=112,autodetected] > [ 18.020163] saa7133[0]: board init: gpio is 20 OK, you are using the patch to change the digital antenna input, no analog used after latest module unload and the IR receiver is not plugged. > [ 18.020239] input: saa7134 IR (ASUSTeK P7131 Hybri as /class/input/input4 > [ 18.054492] intel_rng: FWH not detected > [ 18.148302] nvidia: module license 'NVIDIA' taints kernel. > [ 18.14] saa7133[0]: i2c eeprom 00: 43 10 76 48 54 20 1c 00 43 43 > a9 1c 55 d2 b2 92 > [ 18.155568] saa7133[0]: i2c eeprom 10: ff ff ff 0f ff 20 ff ff ff ff > ff ff ff ff ff ff > [ 18.155581] saa7133[0]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff > 00 d5 ff ff ff ff > [ 18.155593] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff > [ 18.155605] saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 03 32 55 50 > ff ff ff ff ff ff > [ 18.155617] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff > [ 18.155630] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff > [ 18.155642] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff > [ 18.562616] tuner 0-004b: chip found @ 0x96 (saa7133[0]) > [ 18.610496] tda8290 0-004b: setting tuner address to 61 > [ 18.611021] NET: Registered protocol family 17 > [ 18.714276] tuner 0-004b: type set to tda8290+75a > [ 18.762213] tda8290 0-004b: setting tuner address to 61 > [ 18.866006] tuner 0-004b: type set to tda8290+75a Analog detects the right tuner type here. > [ 18.873190] saa7133[0]: registered device video0 [v4l2] > [ 18.873229] saa7133[0]: registered device vbi0 > [ 18.873256] saa7133[0]: registered device radio0 > [ 18.873732] ACPI: PCI Interrupt :00:1b.0[A] -> GSI 16 (level, > low) -> IRQ 16 > [ 18.873766] PCI: Setting latency timer of device :00:1b.0 to 64 > [ 18.911272] saa7134 ALSA driver for DMA sound loaded > [ 18.911615] saa7133[0]/alsa: saa7133[0] at 0xcdcff800 irq 17 > registered as card -2 > [ 19.051812] DVB: registering new adapter (saa7133[0]) > [ 19.051821] DVB: registering frontend 0 (Philips TDA10046H DVB-T)... > [ 19.121478] tda1004x: setting up plls for 48MHz sampling clock > [ 19.141824] ACPI: PCI Interrupt :05:00.0[A] -> GSI 16 (level, > low) -> IRQ 16 > [ 19.141839] PCI: Setting latency timer of device :05:00.0 to 64 > [ 19.141970] NVRM: loading NVIDIA UNIX x86 Kernel Module 1.0-9755 > Mon Feb 26 23:21:15 PST 2007 > [ 19.404784] tda1004x: found firmware revision 29 -- ok > [...] > [ 49.092508] tda1004x: setting up plls for 48MHz sampling clock > [ 49.455718] tda1004x: found firmware revision 29 -- ok > [ 49.796042] DVB: frontend 0 frequency 2147483647 out of range > (5100..85800) > [ 49.834811] DVB: frontend 0 frequency 2147483647 out of range > (5100..85800) For Michael, I'm running latest with all his patches from 20070902 on two different machines down to 2.6.20, except other analog stuff, the tda8275a Asus P7131 Dual and a md7134 with FMD1216ME (the triple, but don't get the second PCI bridge in an analog o
[linux-dvb] New scan file se-Karlstad_Sormon 20070903
A new scan file is attached for Sweden, Karlstad (Sörmon). Valid from 3rd of September 2007. The National authority(Teracom) changed the transmission on Monday the 3rd of September removing all but one Analog TV channel and moving the existing DVB-t muxes, including the FEC high and low types. The last remaining analog channel (SVT1) will be turned off on the 19th. It has been verified by me on 2 different DVB setups. Regards, Simon G. se-Karlstad_Sormon Description: Binary data ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Hauppaug Nova T 500
Many thanks to David and Darren for your replies, Yes, the problem was the initial tuning file. It was from the Ubuntu Feisty dvb-utils package. Running w_scan allowed me to get a file that works with MythTV, but tzap was not happy with the "AUTO" parameters it produced. Using David Matthews information, and the frequencies found by w_scan (and verified on www.ukfree.tv) I could make a channels.conf file that kept tzap happy. For the record, here's my initial tuning file for Craigkelly: # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy #MuxA 23 T 49000 8MHz 2/3 NONE QAM64 2k 1/32 NONE #MuxB 26 T 51400 8MHz 2/3 NONE QAM16 2k 1/32 NONE #Mux2 29 T 53800 8MHz 2/3 NONE QAM64 2k 1/32 NONE #Mux1 33 T 57000 8MHz 2/3 NONE QAM16 2k 1/32 NONE #MuxD 39 T 61800 8MHz 2/3 NONE QAM16 2k 1/32 NONE #MuxC 42 T 64200 8MHz 2/3 NONE QAM16 2k 1/32 NONE # The following were added by w_scan, but no channels found by scan #30 #T 54600 8MHz AUTO AUTO AUTO AUTO AUTO AUTO #34 #T 57800 8MHz AUTO AUTO AUTO AUTO AUTO AUTO #47 #T 68200 8MHz AUTO AUTO AUTO AUTO AUTO AUTO #56 #T 75400 8MHz AUTO AUTO AUTO AUTO AUTO AUTO #59 #T 77800 8MHz AUTO AUTO AUTO AUTO AUTO AUTO #62 #T 80200 8MHz AUTO AUTO AUTO AUTO AUTO AUTO I dont know why there are other frequencies present, but no channels were found. The scan program found some duplicate channels on frequencies off those listed above (eg 490166670). I'm not sure why again, but I removed these from the resulting channel list. So, thanks once again. Dave ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] VHF support for MT2266?
Hi, I recently got a Nova-TD USB Stick which is working fine so far except for the missing support for VHF. I'd like to be able to tune to frequency 18450, but in mt2266.c it says: .frequency_min = 47000, I tried to set this to 17400 without changing anything else. That's the minimum frequency mentioned in the product brief. Kaffeine still says "Can't tune dvb" when I select one of the VHF channels, neither does a new channel scan help. Can anyone help with this? BR Matthias ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] cx88-dvb: fix nxt200x rf input switching broke my tuner? :)
-Original Message- From: Michael Krufky [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 05, 2007 2:07 PM To: Nathan Faust Cc: CityK; linux-dvb@linuxtv.org Subject: Re: [linux-dvb] cx88-dvb: fix nxt200x rf input switching broke my tuner? :) > -Original Message- > From: CityK [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 05, 2007 1:33 PM > To: Nathan Faust > Cc: linux-dvb@linuxtv.org > Subject: Re: [linux-dvb] cx88-dvb: fix nxt200x rf input switching broke > my tuner? :) > > Nathan Faust wrote: >> Hi, >> >> I've notice the same thing with my Kworld ATSC-110. >> I'm running Ubuntu 7.10, 2.6.22-10-generic, x86_64. I guess it is a >> change in the 2.6.22 kernel. >> Is there anyway to change this back so that QAM and NTSC inputs are >> the same? >> > > They should be the same now -- that was what the change was all about. > > By default now, the top RF input should be 8VSB and the bottom should be > QAM & analog (both ota and cable). Nathan Faust wrote: > CityK, > > Thanks for your reply, but that is not what I'm seeing in MythTV and > TVTime for /dev/video0. I'm getting signal from /dev/video0 when I use > the upper input, not the lower one. I haven't trying tuning 8VSB, but > as for the QAM input, that seems to be working as expected. > > Maybe I should look at the driver config for input select in SAA7134 or > swap the input selection lines for VSB and QAM in the dvb code? > > After looking at the input selection code in nxt200x.c, QAM and VSB, it > looks like if I switch these lines it will swap the inputs. > //QAM > - state->config->set_pll_input(buf+1, 1); > + state->config->set_pll_input(buf+1, 0); > > //VSB > - state->config->set_pll_input(buf+1, 0); > + state->config->set_pll_input(buf+1, 1); > > Am I correct? > > I am confused as to what these lines do > if (state->config->set_ts_params) > state->config->set_ts_params(fe, 1); <-- what the > front-end parameter 0 or 1 mean. Nathan, Please do not top-quote As per your description above, you are correct... HOWEVER, now I understand your issue -- you are running old code. If you update to the latest v4l/dvb modules via linuxtv.org mercurial, you will find that functionality has been restored as per your desire. Please see http://linuxtv.org/repo ...for instructions to upgrade your v4l/dvb modules. Good Luck, Mike Mike, I've been using the stock Ubuntu 7.10 kernel (2.6.22.4) with just the Kworld ATSC-110 remote additions. I'll give that a try and get back if I continue to have problems. As for top quoting, sorry about that. Thank you, Nathan. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] New Card: Compro VideoMate S220 DVB-T
Richard (MQ) wrote: > Hi List, > > The Compro VideoMate T200,T200a and T300 are listed at > http://linuxtv.org/hg/v4l-dvb/file/18f323a05fbe/linux/Documentation/video4linux/CARDLIST.saa7134 > - but no T220 > > It's a DVB-T card based on SAA7130 and MT352, incorrectly identified in > OpenSuSE 10.3 (Beta 2) as "Compro Videomate DVB-T200 [185b:c901]" (which > confused me immensely, because that was what I thought I'd bought, but > was wrong!). Needless to say, config as a T200 doesn't work. > > Is there any chance of support for this card please? Can I do anything > to help? > > PS - This is a new thread spun off from "New Card: Compro VideoMate > S300/S350 DVB-S" as I'd rather hijacked it... The following transferred from S300/S350 thread as mentioned above: > > Am Dienstag, den 04.09.2007, 09:19 +0200 schrieb Jan Louw: >>> >> > If it's a T220 I think you're out of luck. Check out >>> >> > http://linuxtv.org/hg/v4l-dvb/file/18f323a05fbe/linux/Documentation/video4linux/CARDLIST.saa7134 >>> >> > for a list of cards (should be somewhere under >>> >> > /usr/src/linux/Documentation as well). The Compro VideoMate T200,T200a >>> >> > and T300 is listed, but no T220. I did see some T220 posts a while back. >>> >> > Maybe they will be of some use to you. >>> >> > >>> >> > What is strange is that your card is not detected as UNKNOWN. Maybe it's >>> >> > because the vendor:product of 185b:c901 is the same as the T200's or >>> >> > maybe YaST added an 'options saa7134 card=72' somewhere... > > > > If again a card with same PCI subsystem ID appears, like now, it should > > fall through the eeprom detection Hartmut has added and print a warning > > about "unknow tuner stuff". You can override it then with the > > card=number insmod option. Without card=n insmod option, the card is wrongly autodetected as DVB-T200 (hence my confusion in the earlier thread), and as you suggest an "Unexpected tuner type" message comes up - this with "options saa7134 i2c_scan=1" in /etc/modprobe.conf.local Sep 5 19:13:36 103-Beta2-2 kernel: saa7130/34: v4l2 driver version 0.2.14 loaded Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: found at :00:0c.0, rev: 1, irq: 18, latency: 32, mmio: 0xe200 Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: subsystem: 185b:c901, board: Compro Videomate DVB-T200 [card=71,autodetected] Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: board init: gpio is 843f00 Sep 5 19:13:36 103-Beta2-2 kernel: input: saa7134 IR (Compro Videomate DV as /class/input/input9 Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 00: 5b 18 01 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 88 ff ff ff ff Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 40: ff d5 00 c4 86 1e ff ff ff ff ff ff ff ff ff ff Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 60: 30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c scan: found device @ 0x1e [???] Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c scan: found device @ 0xa0 [eeprom] Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c scan: found device @ 0xc4 [???] Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c scan: found device @ 0xd0 [???] Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: Unexpected tuner type info: d5 in eeprom Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: registered device video0 [v4l2] Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: registered device vbi0 Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]/dvb: frontend initialization failed "modprobe mt352" does nothing AFAICT, even when "debug=1" is added > I can readily try the mercurial source build if that might help, I'm > currently using kernel 2.6.22.3 (OpenSuSE 10.3 beta 2) > > Where do I find the list of "saa7134 card=x" - is it in that source > code somewhere? > > > Latest always in mercurial saa7134.h and Documentation/saa7134.CARDLIST, > > but won't help. Best approach so far was by Murray Graham I guess. > > http://www.linuxtv.org/pipermail/linux-dvb/2007-July/019030.html > > > > At least a read of the qt1010 register 0x29 returned 0x39, if this is > > safe for the tuner ID. Think 0xd5 for the tuner ID in the eeprom is not > > yet sure, might be vendor specific. On the T100 is one, dmesg, eeprom > > dump and i2c_scan not yet available. > > > > Tuner is at 0x62 (7bit notation) and mt352 at 0xf (0x1e >> 1). > > Something claims to be an analog demod at 0x86 (8bit), but hard to > > believe. I
Re: [linux-dvb] New Card: Compro VideoMate S300/S350 DVB-S
Sorry - wrong thread. Please ignore! Richard (MQ) wrote: >> Am Dienstag, den 04.09.2007, 09:19 +0200 schrieb Jan Louw: ... > Thanks for your help so far, I have grabbed the mercurial source and am > now trying to digest it... -- Cheers Richard (MQ) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] cx88-dvb: fix nxt200x rf input switching broke my tuner? :)
> -Original Message- > From: CityK [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 05, 2007 1:33 PM > To: Nathan Faust > Cc: linux-dvb@linuxtv.org > Subject: Re: [linux-dvb] cx88-dvb: fix nxt200x rf input switching broke > my tuner? :) > > Nathan Faust wrote: >> Hi, >> >> I've notice the same thing with my Kworld ATSC-110. >> I'm running Ubuntu 7.10, 2.6.22-10-generic, x86_64. I guess it is a >> change in the 2.6.22 kernel. >> Is there anyway to change this back so that QAM and NTSC inputs are >> the same? >> > > They should be the same now -- that was what the change was all about. > > By default now, the top RF input should be 8VSB and the bottom should be > QAM & analog (both ota and cable). Nathan Faust wrote: > CityK, > > Thanks for your reply, but that is not what I'm seeing in MythTV and > TVTime for /dev/video0. I'm getting signal from /dev/video0 when I use > the upper input, not the lower one. I haven't trying tuning 8VSB, but > as for the QAM input, that seems to be working as expected. > > Maybe I should look at the driver config for input select in SAA7134 or > swap the input selection lines for VSB and QAM in the dvb code? > > After looking at the input selection code in nxt200x.c, QAM and VSB, it > looks like if I switch these lines it will swap the inputs. > //QAM > - state->config->set_pll_input(buf+1, 1); > + state->config->set_pll_input(buf+1, 0); > > //VSB > - state->config->set_pll_input(buf+1, 0); > + state->config->set_pll_input(buf+1, 1); > > Am I correct? > > I am confused as to what these lines do > if (state->config->set_ts_params) > state->config->set_ts_params(fe, 1); <-- what the > front-end parameter 0 or 1 mean. Nathan, Please do not top-quote As per your description above, you are correct... HOWEVER, now I understand your issue -- you are running old code. If you update to the latest v4l/dvb modules via linuxtv.org mercurial, you will find that functionality has been restored as per your desire. Please see http://linuxtv.org/repo ...for instructions to upgrade your v4l/dvb modules. Good Luck, Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] New Card: Compro VideoMate S300/S350 DVB-S
> Am Dienstag, den 04.09.2007, 09:19 +0200 schrieb Jan Louw: >> > If it's a T220 I think you're out of luck. Check out >> > http://linuxtv.org/hg/v4l-dvb/file/18f323a05fbe/linux/Documentation/video4linux/CARDLIST.saa7134 >> > >> > for a list of cards (should be somewhere under >> > /usr/src/linux/Documentation as well). The Compro VideoMate T200,T200a >> > and T300 is listed, but no T220. I did see some T220 posts a while back. >> > Maybe they will be of some use to you. >> > >> > What is strange is that your card is not detected as UNKNOWN. Maybe it's >> > because the vendor:product of 185b:c901 is the same as the T200's or >> > maybe YaST added an 'options saa7134 card=72' somewhere... > > If again a card with same PCI subsystem ID appears, like now, it should > fall through the eeprom detection Hartmut has added and print a warning > about "unknow tuner stuff". You can override it then with the > card=number insmod option. Without card=n insmod option, the card is wrongly autodetected as DVB-T200 (hence my confusion in the earlier thread), and as you suggest an "Unexpected tuner type" message comes up - this with "options saa7134 i2c_scan=1" in /etc/modprobe.conf.local Sep 5 19:13:36 103-Beta2-2 kernel: saa7130/34: v4l2 driver version 0.2.14 loaded Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: found at :00:0c.0, rev: 1, irq: 18, latency: 32, mmio: 0xe200 Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: subsystem: 185b:c901, board: Compro Videomate DVB-T200 [card=71,autodetected] Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: board init: gpio is 843f00 Sep 5 19:13:36 103-Beta2-2 kernel: input: saa7134 IR (Compro Videomate DV as /class/input/input9 Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 00: 5b 18 01 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 88 ff ff ff ff Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 40: ff d5 00 c4 86 1e ff ff ff ff ff ff ff ff ff ff Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 60: 30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c scan: found device @ 0x1e [???] Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c scan: found device @ 0xa0 [eeprom] Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c scan: found device @ 0xc4 [???] Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: i2c scan: found device @ 0xd0 [???] Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: Unexpected tuner type info: d5 in eeprom Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: registered device video0 [v4l2] Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]: registered device vbi0 Sep 5 19:13:36 103-Beta2-2 kernel: saa7130[0]/dvb: frontend initialization failed "modprobe mt352" does nothing AFAICT, even when "debug=1" is added >>> > > I can readily try the mercurial source build if that might help, I'm >>> > > currently using kernel 2.6.22.3 (OpenSuSE 10.3 beta 2) >>> > > >>> > > Where do I find the list of "saa7134 card=x" - is it in that source code >>> > > somewhere? > > Latest always in mercurial saa7134.h and Documentation/saa7134.CARDLIST, > but won't help. Best approach so far was by Murray Graham I guess. > http://www.linuxtv.org/pipermail/linux-dvb/2007-July/019030.html > > At least a read of the qt1010 register 0x29 returned 0x39, if this is > safe for the tuner ID. Think 0xd5 for the tuner ID in the eeprom is not > yet sure, might be vendor specific. On the T100 is one, dmesg, eeprom > dump and i2c_scan not yet available. > > Tuner is at 0x62 (7bit notation) and mt352 at 0xf (0x1e >> 1). > Something claims to be an analog demod at 0x86 (8bit), but hard to > believe. I have emailed Murray Graham directly (address from that archive) but no response as yet. Thanks for your help so far, I have grabbed the mercurial source and am now trying to digest it... -- Cheers Richard (MQ). ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] cx88-dvb: fix nxt200x rf input switching broke my tuner? :)
CityK, Thanks for your reply, but that is not what I'm seeing in MythTV and TVTime for /dev/video0. I'm getting signal from /dev/video0 when I use the upper input, not the lower one. I haven't trying tuning 8VSB, but as for the QAM input, that seems to be working as expected. Maybe I should look at the driver config for input select in SAA7134 or swap the input selection lines for VSB and QAM in the dvb code? After looking at the input selection code in nxt200x.c, QAM and VSB, it looks like if I switch these lines it will swap the inputs. //QAM - state->config->set_pll_input(buf+1, 1); + state->config->set_pll_input(buf+1, 0); //VSB - state->config->set_pll_input(buf+1, 0); + state->config->set_pll_input(buf+1, 1); Am I correct? I am confused as to what these lines do if (state->config->set_ts_params) state->config->set_ts_params(fe, 1); <-- what the front-end parameter 0 or 1 mean. Thank you, Nathan. -Original Message- From: CityK [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 05, 2007 1:33 PM To: Nathan Faust Cc: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] cx88-dvb: fix nxt200x rf input switching broke my tuner? :) Nathan Faust wrote: > Hi, > > I've notice the same thing with my Kworld ATSC-110. > I'm running Ubuntu 7.10, 2.6.22-10-generic, x86_64. I guess it is a > change in the 2.6.22 kernel. > Is there anyway to change this back so that QAM and NTSC inputs are > the same? > They should be the same now -- that was what the change was all about. By default now, the top RF input should be 8VSB and the bottom should be QAM & analog (both ota and cable). ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] cx88-dvb: fix nxt200x rf input switching broke my tuner? :)
Nathan Faust wrote: > Hi, > > I've notice the same thing with my Kworld ATSC-110. > I'm running Ubuntu 7.10, 2.6.22-10-generic, x86_64. I guess it is a > change in the 2.6.22 kernel. > Is there anyway to change this back so that QAM and NTSC inputs are the > same? > They should be the same now -- that was what the change was all about. By default now, the top RF input should be 8VSB and the bottom should be QAM & analog (both ota and cable). ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Dvb card sensitivity to power supply
I have a Hauppauge WinTV Nexus-CA dvb-c card and a WinTV-Nova-C budget card. For some reason lately there has been more and more problems with the picture. Femon shows that the signal is good () and snr is not so bad either (e0e0 or better). I remember reading somewhere that these cards are quite sensitive to how gow good the power supple is. Has anyone noticed any similar behaviour? I mean should I by a new power supply? Would it be worth it? The power supply is some years old though. I would apreciate any hints / advise. \\Kartsa ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] cx88-dvb: fix nxt200x rf input switching broke my tuner? :)
Hi, I've notice the same thing with my Kworld ATSC-110. I'm running Ubuntu 7.10, 2.6.22-10-generic, x86_64. I guess it is a change in the 2.6.22 kernel. Is there anyway to change this back so that QAM and NTSC inputs are the same? Thank you, Nathan. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Sandeen Sent: Saturday, August 25, 2007 7:29 PM To: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] cx88-dvb: fix nxt200x rf input switching broke my tuner? :) Eric Sandeen wrote: > hi, I have a Kworld ATSC 110 PCI DVB card, > > 03:09.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 > Video Broadcast Decoder (rev f0) > Subsystem: KWorld Computer Co. Ltd. ATSC 110 Digital / Analog > HDTV Tuner > Flags: bus master, medium devsel, latency 55, IRQ 23 > Memory at c4001000 (32-bit, non-prefetchable) [size=2K] > Capabilities: [40] Power Management version 2 > > It seems this fairly recent mod broke my ability to tune in QAM HDTV: > > --- > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=com > mitdiff;h=f5ae29e284b328e0976789d5c199bbbe80e4b005 > [PATCH] cx88-dvb: fix nxt200x rf input switching Michael Krufky [Sat, > 24 Mar 2007 17:21:53 + (13:21 -0400)] After dvb tuner refactoring, > the pllbuff has been altered such that the pll address is now stored > in buf[0]. Instead of sending buf to set_pll_input, we should send > buf+1. > > --- Ok, after much patient assistance from mkrufky, we sorted out that a recent change meant that I had to switch physical inputs on my card - that is, plugging the physical cable into the *other* card input (the input closer to the center of pci card bracket) - makes everything happy again... Thanks, -Eric ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Hauppaug Nova T 500
Dave wrote: > > [EMAIL PROTECTED]:/home/dave# scan > /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-Craigkelly > scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-Craigkelly > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > initial transponder 49000 0 2 9 3 0 3 0 > initial transponder 51400 0 2 9 1 0 3 0 > initial transponder 53800 0 2 9 3 0 3 0 > initial transponder 57000 0 2 9 1 0 3 0 > initial transponder 61800 0 2 9 1 0 3 0 > initial transponder 64200 0 2 9 1 0 3 0 > >>> tune to: > 49000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_4:HIERARCHY_NONE > WARNING: >>> tuning failed!!! It seems the guard interval is wrong. It should be 1/32 not 1/4. Try the file below. It worked for me just now. I have a Nova T-500 and get both Craigkelly and Black Hill. I've also adjusted a couple of the frequencies although that doesn't seem essential. David # uk Craigkelly # # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 48983 8MHz 2/3 NONE QAM64 2k 1/32 NONE T 51383 8MHz 2/3 NONE QAM16 2k 1/32 NONE T 53800 8MHz 2/3 NONE QAM64 2k 1/32 NONE T 57000 8MHz 2/3 NONE QAM16 2k 1/32 NONE T 61800 8MHz 2/3 NONE QAM16 2k 1/32 NONE T 64200 8MHz 2/3 NONE QAM16 2k 1/32 NONE ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Patch for all tuners Beholder series 40x, 50x, 60x, M6, Columbus
Igor Kuznetsov wrote: > > > Made support all tuners Beholder. Almost-not yet only support hardware MPEG > decoders in a series of M6. > > > > Patch for all tuners Beholder series 40x, 50x, 60x, M6, and Columbus > > > > http://www.igk.ru/linux/files/v4l/v4l2-beholder-0.1.patch > > -- > > Igor Kuznetsov "IgK" > > Email: [EMAIL PROTECTED] [EMAIL PROTECTED] > > ICQ: 6651879 Igor, First off, it looks like these devices are analog-only, so it would be more appropriate to send this to the video4linux mailing list (cc added) The patch is large, so I chopped it from the email. For those interested, please see the original email: http://linuxtv.org/pipermail/linux-dvb/2007-September/020256.html Secondly, your patch introduces broken whitespace all over. Tabs should be used for leading spacing, not a series of spaces. We prefer for new cards to be added to the end of the card array-- not dispersed randomly throughout. It looks like your large patch includes work from multiple contributors, based on the different names that I see commented within the card array additions. You did not provide a sign-off on your work. You should probably also collect sign-off's from those other developers involved in this work. For more information on sign-off, and patch submissions to the v4l/dvb projects in general, please see: http://linuxtv.org/hg/v4l-dvb/file/tip/README.patches The preferred method would be to clone the latest version of the repository from linuxtv.org, apply your patch to that tree, test it, and then generate a new diff as follows: hg diff > new.patch Then, send in that new patch to the mailing lists. Again, when you send in the new patch with sign-offs , please be sure to include the video4linux mailing list: Linux and Kernel Video <[EMAIL PROTECTED]> Cheers, Mike Krufky ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Patch for all tuners Beholder series 40x, 50x, 60x, M6, Columbus
Made support all tuners Beholder. Almost-not yet only support hardware MPEG
decoders in a series of M6.
Patch for all tuners Beholder series 40x, 50x, 60x, M6, and Columbus
http://www.igk.ru/linux/files/v4l/v4l2-beholder-0.1.patch
--
Igor Kuznetsov "IgK"
Email: [EMAIL PROTECTED] [EMAIL PROTECTED]
ICQ: 6651879diff -urp v4l-dvb/linux/drivers/media/video/ir-kbd-i2c.c v4l-dvb.beholder/linux/drivers/media/video/ir-kbd-i2c.c
--- v4l-dvb/linux/drivers/media/video/ir-kbd-i2c.c 2007-08-23 01:01:28.0 +0400
+++ v4l-dvb.beholder/linux/drivers/media/video/ir-kbd-i2c.c 2007-09-04 15:14:53.0 +0400
@@ -383,6 +383,7 @@ static int ir_attach(struct i2c_adapter
case 0x7a:
case 0x47:
case 0x71:
+ case 0x2d:
if (adap->id == I2C_HW_B_CX2388x) {
/* Handled by cx88-input */
name= "CX2388x remote";
@@ -493,7 +494,7 @@ static int ir_probe(struct i2c_adapter *
*/
static const int probe_bttv[] = { 0x1a, 0x18, 0x4b, 0x64, 0x30, -1};
- static const int probe_saa7134[] = { 0x7a, 0x47, 0x71, -1 };
+ static const int probe_saa7134[] = { 0x7a, 0x47, 0x71, 0x2d, -1 };
static const int probe_em28XX[] = { 0x30, 0x47, -1 };
static const int probe_cx88[] = { 0x18, 0x71, -1 };
const int *probe = NULL;
diff -urp v4l-dvb/linux/drivers/media/video/saa7134/saa7134-cards.c v4l-dvb.beholder/linux/drivers/media/video/saa7134/saa7134-cards.c
--- v4l-dvb/linux/drivers/media/video/saa7134/saa7134-cards.c 2007-08-23 01:01:29.0 +0400
+++ v4l-dvb.beholder/linux/drivers/media/video/saa7134/saa7134-cards.c 2007-09-05 01:21:46.0 +0400
@@ -2177,6 +2177,190 @@ struct saa7134_board saa7134_boards[] =
.gpio = 0x01,
},
},
+ [SAA7134_BOARD_BEHOLD_401] = {
+ .name = "Beholder BeholdTV 401",
+ .audio_clock= 0x00187de7,
+ .tuner_type = TUNER_PHILIPS_FQ1216ME,
+ .radio_type = UNSET,
+ .tuner_addr = ADDR_UNSET,
+ .radio_addr = ADDR_UNSET,
+ .inputs = {{
+ .name = name_svideo,
+ .vmux = 8,
+ .amux = LINE1,
+ },{
+ .name = name_comp1,
+ .vmux = 1,
+ .amux = LINE1,
+ },{
+ .name = name_tv,
+ .vmux = 3,
+ .amux = LINE2,
+ .tv = 1,
+ }},
+ .mute = {
+ .name = name_mute,
+ .amux = LINE1,
+ },
+ },
+ [SAA7134_BOARD_BEHOLD_403] = {
+ .name = "Beholder BeholdTV 403",
+ .audio_clock= 0x00187de7,
+ .tuner_type = TUNER_PHILIPS_FQ1216ME,
+ .radio_type = UNSET,
+ .tuner_addr = ADDR_UNSET,
+ .radio_addr = ADDR_UNSET,
+ .inputs = {{
+ .name = name_svideo,
+ .vmux = 8,
+ .amux = LINE1,
+ },{
+ .name = name_comp1,
+ .vmux = 1,
+ .amux = LINE1,
+ },{
+ .name = name_tv,
+ .vmux = 3,
+ .amux = LINE2,
+ .tv = 1,
+ }},
+ },
+ [SAA7134_BOARD_BEHOLD_403FM] = {
+ .name = "Beholder BeholdTV 403 FM",
+ .audio_clock= 0x00187de7,
+ .tuner_type = TUNER_PHILIPS_FQ1216ME,
+ .radio_type = UNSET,
+ .tuner_addr = ADDR_UNSET,
+ .radio_addr = ADDR_UNSET,
+ .inputs = {{
+ .name = name_svideo,
+ .vmux = 8,
+ .amux = LINE1,
+ },{
+ .name = name_comp1,
+ .vmux = 1,
+ .amux = LINE1,
+ },{
+ .name = name_tv,
+ .vmux = 3,
+ .amux = LINE2,
+ .tv = 1,
+ }},
+ .radio = {
+ .name = name_radio,
+ .amux = LINE2,
+ },
+ },
+ [SAA7134_BOARD_BEHOLD_405] = {
+ /* , Sergey <[EMAIL PROTECTED]> */
+ .name = "Beholder BeholdTV 405",
+ .audio_clock= 0x00187de7,
+ .tuner_type = TUNER_PHILIPS_FM1216ME_MK3,
+ .radio_type = UNSET,
+ .tuner_addr = ADDR_UNSET,
+ .radio_addr = ADDR_UNSET,
+ .tda9887_conf = TDA9887_PRESENT,
+ .inputs = {{
+ .name = name_svideo,
+ .vmux = 8,
+ .amux = LINE1,
+ },{
+ .name = name_comp1,
+ .vmux = 3,
+ .amux = LINE1,
+ },{
+ .name = name_tv,
+ .vmux = 3,
+ .amux = LINE2,
+ .tv = 1,
+ }},
+ },
+ [SAA7134_BOARD_BEHOLD_405FM] = {
+ /* , Sergey <[EMAIL PROTECTED]> */
+ .name = "Beholder BeholdTV 405 FM",
+ .audio_clock= 0x00187de7,
+ .tuner_type = TUNER_PHILIPS_FM1216ME_MK3,
+ .radio_type = UNSET,
+ .tuner_addr = ADDR_UNSET,
+ .radio_addr = ADDR_UNSET,
+ .tda9887_conf = TDA9887_PRESENT,
+ .inputs = {{
+ .name = name_svideo,
+ .vmux = 8,
+ .amux = LINE1,
+ },{
+ .name = name_comp1,
+ .vmux = 3,
+ .amux = LINE1,
+ },{
+ .name = name_tv,
+ .vmux = 3,
+ .amux = LINE2,
+ .tv = 1,
+ }},
+ .radio = {
+ .name = name_radio,
+ .amux = LINE2,
+ },
+ },
+ [SAA7134_BOARD_BEHOLD_407FM] = {
+ /* */
+ /*, Evgeny <[EMAIL PROTECTED]> */
+ .name = "Beholder BeholdTV 407 FM",
+ .audio_clock = 0x00187de7,
+ .tuner_type = TUNER_PHILIPS_FM1216ME_MK3,
+ .radio_type = UNSET,
+ .tuner_addr = ADDR_UNSET,
+ .radio_addr = ADDR_UNSET,
+ .tda9887_conf = TDA9887_PRESENT,
+ .gpiomask = 0xc0c000,
+ .inputs = {{
+ .name = name_svideo,
+ .vmux = 8,
[linux-dvb] Asys P7131 Hybrid: DVB out of range
This morning I upgraded the kernel of my linux box. After that I cloned v4l-dvb and compiled everything. I've done it because couldn't watch digital tv with mplayer but only with kaffeine. Mplayer error was: vb_streaming_read, attempt N. 6 failed with errno 0 when reading ... So I tried to update bit I didn't solve the problem. Than I've done some test with Mythtv and auto-scanning for channels... and now... ...now I'm having the following (BIG) problem: dvb-t doesn't work anymore (also in kaffeiene or tzap). dmesg has the following error: DVB: frontend 0 frequency 2147483647 out of range (5100..85800) After this mess up, analogical TV is no more properly working, before was really perfect. Going crazy... thank you for your help. P.S. I would like to know is some of you could use a patch cable between P7131 and motherboard for listen TV. I've tried sever time but no sound at all and I have to use sox or aplay. Some information about my system: SO: Ubuntu 7.07 - Linux linux 2.6.20-16-generic dmesg: [...] [ 18.020064] saa7130/34: v4l2 driver version 0.2.14 loaded [ 18.020132] ACPI: PCI Interrupt :01:09.0[A] -> GSI 17 (level, low) -> IRQ 17 [ 18.020144] saa7133[0]: found at :01:09.0, rev: 209, irq: 17, latency: 64, mmio: 0xcdcff800 [ 18.020152] saa7133[0]: subsystem: 1043:4876, board: ASUSTeK P7131 Hybrid [card=112,autodetected] [ 18.020163] saa7133[0]: board init: gpio is 20 [ 18.020239] input: saa7134 IR (ASUSTeK P7131 Hybri as /class/input/input4 [ 18.054492] intel_rng: FWH not detected [ 18.148302] nvidia: module license 'NVIDIA' taints kernel. [ 18.14] saa7133[0]: i2c eeprom 00: 43 10 76 48 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 [ 18.155568] saa7133[0]: i2c eeprom 10: ff ff ff 0f ff 20 ff ff ff ff ff ff ff ff ff ff [ 18.155581] saa7133[0]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff 00 d5 ff ff ff ff [ 18.155593] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 18.155605] saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 03 32 55 50 ff ff ff ff ff ff [ 18.155617] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 18.155630] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 18.155642] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 18.562616] tuner 0-004b: chip found @ 0x96 (saa7133[0]) [ 18.610496] tda8290 0-004b: setting tuner address to 61 [ 18.611021] NET: Registered protocol family 17 [ 18.714276] tuner 0-004b: type set to tda8290+75a [ 18.762213] tda8290 0-004b: setting tuner address to 61 [ 18.866006] tuner 0-004b: type set to tda8290+75a [ 18.873190] saa7133[0]: registered device video0 [v4l2] [ 18.873229] saa7133[0]: registered device vbi0 [ 18.873256] saa7133[0]: registered device radio0 [ 18.873732] ACPI: PCI Interrupt :00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16 [ 18.873766] PCI: Setting latency timer of device :00:1b.0 to 64 [ 18.911272] saa7134 ALSA driver for DMA sound loaded [ 18.911615] saa7133[0]/alsa: saa7133[0] at 0xcdcff800 irq 17 registered as card -2 [ 19.051812] DVB: registering new adapter (saa7133[0]) [ 19.051821] DVB: registering frontend 0 (Philips TDA10046H DVB-T)... [ 19.121478] tda1004x: setting up plls for 48MHz sampling clock [ 19.141824] ACPI: PCI Interrupt :05:00.0[A] -> GSI 16 (level, low) -> IRQ 16 [ 19.141839] PCI: Setting latency timer of device :05:00.0 to 64 [ 19.141970] NVRM: loading NVIDIA UNIX x86 Kernel Module 1.0-9755 Mon Feb 26 23:21:15 PST 2007 [ 19.404784] tda1004x: found firmware revision 29 -- ok [...] [ 49.092508] tda1004x: setting up plls for 48MHz sampling clock [ 49.455718] tda1004x: found firmware revision 29 -- ok [ 49.796042] DVB: frontend 0 frequency 2147483647 out of range (5100..85800) [ 49.834811] DVB: frontend 0 frequency 2147483647 out of range (5100..85800) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] linux-dvb Digest, Vol 32, Issue 12
ter:1317: start filter pid 0x0010 table_id 0x40 > update_poll_fds:1297: poll fd 6 > update_poll_fds:1297: poll fd 5 > update_poll_fds:1297: poll fd 4 > WARNING: filter timeout pid 0x0011 > remove_filter:1385: remove filter pid 0x0011 > stop_filter:1363: stop filter pid 0x0011 > update_poll_fds:1297: poll fd 6 > update_poll_fds:1297: poll fd 4 > WARNING: filter timeout pid 0x > remove_filter:1385: remove filter pid 0x > stop_filter:1363: stop filter pid 0x > update_poll_fds:1297: poll fd 6 > WARNING: filter timeout pid 0x0010 > remove_filter:1385: remove filter pid 0x0010 > stop_filter:1363: stop filter pid 0x0010 > dumping lists (0 services) > Done. > > > > > > ./tzap shows: > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > tuning to 60200 Hz > video pid 0x00a1, audio pid 0x0052 > status 1b | signal 5bbb | snr | ber 001f | unc | > FE_HAS_LOCK > status 1b | signal 5657 | snr | ber 001f | unc 0008 | > FE_HAS_LOCK > status 1b | signal 562e | snr | ber 001f | unc | > FE_HAS_LOCK > status 1b | signal 567e | snr | ber 001f | unc | > FE_HAS_LOCK > status 1b | signal 56da | snr | ber 001f | unc | > FE_HAS_LOCK > > > > > > dmesg shows: > ACPI: PCI Interrupt :00:11.5[C] -> GSI 22 (level, low) -> IRQ 19 > PCI: Setting latency timer of device :00:11.5 to 64 > usb 4-1: new high speed USB device using ehci_hcd and address 2 > usb 4-1: configuration #1 chosen from 1 choice > dib0700: loaded with support for 5 different device-types > dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state. > dvb-usb: will pass the complete MPEG2 transport stream to the software > demuxer. > DVB: registering new adapter (Hauppauge Nova-T Stick) > DVB: registering frontend 0 (DiBcom 7000PC)... > MT2060: successfully identified (IF1 = 1220) > input: IR-receiver inside an USB DVB receiver as /class/input/input1 > dvb-usb: schedule remote query interval to 150 msecs. > dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected. > usbcore: registered new interface driver dvb_usb_dib0700 > > > > -- > > Message: 2 > Date: Wed, 05 Sep 2007 08:52:49 +0400 > From: goga777 <[EMAIL PROTECTED]> > Subject: Re: [linux-dvb] HDTV performance issues > To: linux-dvb@linuxtv.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="koi8-r" > > > > >>There is no PureVideo support in the NVidia Linux driver. > > > yes,?the?same?sad?situation?in?Linux?with?the?cards?from?ATI??(AVIVO > technology). > > Also,?there's?not?interlace PAFF?support?in?MPlayer?(ffmpeg). > > But?you?can??have a look on new Extension HD/PCI card from > ReelMultimedia - with h264 hardware decoder from Micronas and with > hdmi output. > > > > http://www.reel-multimedia.com/rmm-english/pdf/produkt-flyer/extension_hd.pdf > > Igor > > ? > -- next part -- > An HTML attachment was scrubbed... > URL: > http://www.linuxtv.org/pipermail/linux-dvb/attachments/20070905/bcac0755/attachment.html > > -- > > Message: 3 > Date: Wed, 05 Sep 2007 07:52:26 +0100 > From: "richard (MQ)" <[EMAIL PROTECTED]> > Subject: Re: [linux-dvb] New Card: Compro VideoMate S300/S350 DVB-S > To: linux-dvb@linuxtv.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > hermann pitton wrote: > > > And please, start a new thread ... ;) > > I already did - "New Card: Compro VideoMate T220 DVB-T" (at about the > same time you sent your message, which I just saw.) > > I will attampt to answer your questions on teh new thread, but it will > have to wait till I get in tonight. > -- > Cheers > Richard (MQ) > > > > -- > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > > End of linux-dvb Digest, Vol 32, Issue 12 > * > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HDTV performance issues
>>There is no PureVideo support in the NVidia Linux driver hot news from today morning AMD: Accelerating Open-Source Drivers http://www.phoronix.com/scan.php?page=article&item=825&num=1 let's hope that with AMD/ATI cards with new Linux-drivers we can see h264 video without any problem Igor ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
