* [linux-dvb] [Fwd: Re: Try to Make DVB-T part of Compro VideoMate T750 Work]
@ 2008-05-07 22:34 Rod
0 siblings, 0 replies; 4+ messages in thread
From: Rod @ 2008-05-07 22:34 UTC (permalink / raw)
To: linux-dvb
[-- Attachment #1: Type: text/plain, Size: 46 bytes --]
Repost as I think I fell off the list ;o(
[-- Attachment #2: Re: Try to Make DVB-T part of Compro VideoMate T750 Work.eml --]
[-- Type: message/rfc822, Size: 10011 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 226 bytes --]
You are not allowed to post to this mailing list, and your message has
been automatically rejected. If you think that your messages are
being rejected in error, contact the mailing list owner at
linux-dvb-owner@linuxtv.org.
[-- Attachment #2.1.2: Type: message/rfc822, Size: 7555 bytes --]
From: Rod <Rod@Rods.id.au>
To: lin <b87605214@ntu.edu.tw>
Cc: linux-dvb@linuxtv.org
Subject: Re: Try to Make DVB-T part of Compro VideoMate T750 Work
Date: Wed, 07 May 2008 22:23:37 +1000
Message-ID: <48219F49.9090709@Rods.id.au>
Hi, what I2C addresses are you using for each device?
lin wrote:
> Hi:
>
> At preseant, I'm trying to make DVB-T work on Compro T750 (an digital/analog
> hybrid TV capture card) while analog part has already been implemented by
> Newbigin. Since I can only recieve DVB-T signal, I'll mainly focus on DVB-T
> part implementation.
>
> First of all, I need to make sure the chips used on this card. They are...
> Philips ""saa7135"" as main video audio decoder
> Quantek ""qt1010"" as digital TV silicon tuner
> Intel ""ce6353"" or Zarlink ""zl10353""??? as demodulator behind qt1010
> ( I'm not sure which one is the real demodulator adopted on this card. Does
> anybody have further information?)
> Xceive ""xc2028"" as analog TV silicon tuner
>
> My current v4l-dvb version is checked out from linuxtv Mercurial server
> http://linuxtv.org/hg/v4l-dvb
> (v4l-dvb-4c4fd6b8755c)
> , and I manunally patch Newbigin's code on it
> http://www.chrysocome.net/downloads/v4l-dvb-experimental-t750-0.2.diff
> The firmware used by xc2028 driver are generated by extract_xc3028.pl pearl
> scripts. After get all of this done, I can view several DVB-T TV channels
> through Kaffeine, but the quality is unacceptable. The situation seems only
> key frames are decode properly, and the other frames are simply
> blocked "like" the antenna signal weak. So does the sound.
>
> The following is the dmesg related to v4l-dvb modules:
>
> [ 43.971924] Linux video capture interface: v2.00
> [ 44.042551] saa7130/34: v4l2 driver version 0.2.14 loaded
> [ 44.042642] ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC4] -> GSI 19
> (level, high) -> IRQ 20
> [ 44.042652] saa7133[0]: found at 0000:01:07.0, rev: 209, irq: 20, latency:
> 32, mmio: 0xdf001000
> [ 44.042660] saa7133[0]: subsystem: 185b:c900, board: Compro VideoMate T750
> [card=139,autodetected]
> [ 44.042670] saa7133[0]: board init: gpio is 849300
> [ 44.042767] input: saa7134 IR (Compro VideoMate T7 as /class/input/input4
> [ 44.204856] saa7133[0]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c
> 55 d2 b2 92
> [ 44.204866] saa7133[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff
> ff ff ff ff
> [ 44.204874] saa7133[0]: i2c eeprom 20: 01 40 01 02 02 01 03 01 08 ff 00 87
> ff ff ff ff
> [ 44.204881] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 44.204888] saa7133[0]: i2c eeprom 40: ff d7 00 c4 86 1e 05 ff 02 c2 ff 01
> ff ff ff ff
> [ 44.204895] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff cb
> [ 44.204902] saa7133[0]: i2c eeprom 60: 35 ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 44.204914] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 44.204921] saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 44.204928] saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 44.204935] saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 44.204942] saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 44.204949] saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 44.204956] saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 44.204963] saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 44.204970] saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 44.340757] tuner' 2-0061: chip found @ 0xc2 (saa7133[0])
> [ 44.348645] tuner' 2-0062: chip found @ 0xc4 (saa7133[0])
> [ 44.356706] tuner' 2-0063: chip found @ 0xc6 (saa7133[0])
> [ 44.369421] tuner' 2-0068: chip found @ 0xd0 (saa7133[0])
> [ 44.379813] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 20
> [ 44.379820] ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI 20
> (level, high) -> IRQ 18
> [ 44.379850] PCI: Setting latency timer of device 0000:00:06.0 to 64
> [ 44.419310] xc2028 2-0061: type set to XCeive xc2028/xc3028 tuner
> [ 44.524079] xc2028 2-0061: Loading 80 firmware images from xc3028-v27.fw,
> type: xc2028 firmware, ver 2.7
> [ 45.268105] xc2028 2-0061: Loading firmware for type=BASE F8MHZ MTS (7), id
> 0000000000000000.
> [ 46.024569] xc2028 2-0061: i2c output error: rc = -5 (should be 64)
> [ 46.024573] xc2028 2-0061: -5 returned from send
> [ 46.024577] xc2028 2-0061: Error -22 while loading base firmware
> [ 46.082924] intel8x0_measure_ac97_clock: measured 59209 usecs
> [ 46.082929] intel8x0: clocking to 47499
> [ 46.829573] xc2028 2-0061: Loading firmware for type=BASE F8MHZ MTS (7), id
> 0000000000000000.
> [ 47.573565] input: ImPS/2 Logitech Wheel Mouse as /class/input/input5
> [ 47.581186] xc2028 2-0061: i2c output error: rc = -5 (should be 64)
> [ 47.581191] xc2028 2-0061: -5 returned from send
> [ 47.581195] xc2028 2-0061: Error -22 while loading base firmware
> [ 48.325117] xc2028 2-0061: Loading firmware for type=BASE F8MHZ MTS (7), id
> 0000000000000000.
> [ 49.112002] xc2028 2-0061: i2c output error: rc = -5 (should be 64)
> [ 49.112007] xc2028 2-0061: -5 returned from send
> [ 49.112012] xc2028 2-0061: Error -22 while loading base firmware
> [ 49.911789] xc2028 2-0061: Loading firmware for type=BASE F8MHZ MTS (7), id
> 0000000000000000.
> [ 50.665031] xc2028 2-0061: i2c output error: rc = -5 (should be 64)
> [ 50.665036] xc2028 2-0061: -5 returned from send
> [ 50.665040] xc2028 2-0061: Error -22 while loading base firmware
> [ 50.677464] saa7133[0]: registered device video0 [v4l2]
> [ 50.679443] saa7133[0]: registered device vbi0
> [ 50.681560] saa7133[0]: registered device radio0
> [ 50.707733] Compro VideoMate T750 DVB setup
> [ 50.740839] saa7134 ALSA driver for DMA sound loaded
> [ 50.740875] saa7133[0]/alsa: saa7133[0] at 0xdf001000 irq 20 registered as
> card -2
> [ 50.766307] Attaching pll
> [ 50.802239] Quantek QT1010 successfully identified.
> [ 50.802246] DVB: registering new adapter (saa7133[0])
> [ 50.802255] DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)...
>
>
>
>
> Do you have any suggestion about this?
>
> Thanks
>
>
> linleno
>
>
>
[-- Attachment #3: Type: text/plain, Size: 150 bytes --]
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 4+ messages in thread
* [linux-dvb] [Fwd: Re: Try to Make DVB-T part of Compro VideoMate T750 Work]
@ 2008-05-09 23:57 Rod
0 siblings, 0 replies; 4+ messages in thread
From: Rod @ 2008-05-09 23:57 UTC (permalink / raw)
To: linux-dvb
[-- Attachment #1: Type: text/plain, Size: 26 bytes --]
Forgot to cc the list ;o(
[-- Attachment #2: Re: Try to Make DVB-T part of Compro VideoMate T750 Work.eml --]
[-- Type: message/rfc822, Size: 10087 bytes --]
From: "Rod Smart" <Rod@Rods.id.au>
To: "lin" <b87605214@ntu.edu.tw>
Subject: Re: Try to Make DVB-T part of Compro VideoMate T750 Work
Date: Fri, 9 May 2008 13:11:31 +1000 (EST)
Message-ID: <2027.58.105.235.135.1210302691.squirrel@www.rods.id.au>
> On 2008 May 7 Wednesday 20:23:37 you wrote:
>> Hi, what I2C addresses are you using for each device?
>
> Hi, Rod:
>
> Sorry for late replying...
>
> Following is my patch to v4l-dvb (v4l-dvb-4c4fd6b8755c)
> The patch is mainly adapted from Newbigin's patch, but the case in
> saa7134_board_init2 is talltolly a nonsense guessing... lol
>
> Ask a newbie question... lol
> What's the role of I2C plays in between these chips?
>
> linleno
> ---
>
> diff -ru
> v4l-dvb-4c4fd6b8755c-ori/linux/drivers/media/video/saa7134/saa7134-cards.c
> v4l-dvb-4c4fd6b8755c/linux/drivers/media/video/saa7134/saa7134-cards.c
> ---
> v4l-dvb-4c4fd6b8755c-ori/linux/drivers/media/video/saa7134/saa7134-cards.c
> 2008-05-02 18:51:27.000000000 +0800
> +++ v4l-dvb-4c4fd6b8755c/linux/drivers/media/video/saa7134/saa7134-cards.c
> 2008-05-08 22:42:06.000000000 +0800
> @@ -5936,6 +5936,7 @@
> case SAA7134_BOARD_AVERMEDIA_SUPER_007:
> case SAA7134_BOARD_TWINHAN_DTV_DVB_3056:
> case SAA7134_BOARD_CREATIX_CTX953:
> + case SAA7134_BOARD_VIDEOMATE_T750:
> {
> /* this is a hybrid board, initialize to analog mode
> * and configure firmware eeprom address
> diff -ru
> v4l-dvb-4c4fd6b8755c-ori/linux/drivers/media/video/saa7134/saa7134-dvb.c
> v4l-dvb-4c4fd6b8755c/linux/drivers/media/video/saa7134/saa7134-dvb.c
> ---
> v4l-dvb-4c4fd6b8755c-ori/linux/drivers/media/video/saa7134/saa7134-dvb.c
> 2008-05-02 18:51:27.000000000 +0800
> +++ v4l-dvb-4c4fd6b8755c/linux/drivers/media/video/saa7134/saa7134-dvb.c
> 2008-05-08 22:42:54.000000000 +0800
> @@ -40,6 +40,8 @@
> #include "tda1004x.h"
> #include "nxt200x.h"
> #include "tuner-xc2028.h"
> +#include "zl10353.h"
> +#include "qt1010.h"
>
> #include "tda10086.h"
> #include "tda826x.h"
> @@ -937,6 +939,17 @@
> .demod_address = 0x0a,
> };
>
> +static struct zl10353_config videomate_t750_zl10353_config = {
> + .demod_address = 0x0f,
> + .no_tuner = 0,
> + .parallel_ts = 1,
> +};
> +
> +static struct qt1010_config videomate_t750_qt1010_config = {
> + .i2c_address = 0x62
> +};
> +
> +
> /* ==================================================================
> * Core code
> */
> @@ -1263,15 +1276,33 @@
> goto dettach_frontend;
> break;
> case SAA7134_BOARD_AVERMEDIA_CARDBUS_506:
> -#if 0
> - /*FIXME: What frontend does Videomate T750 use? */
> - case SAA7134_BOARD_VIDEOMATE_T750:
> -#endif
> dev->dvb.frontend = dvb_attach(mt352_attach,
> &avermedia_e506r_mt352_dev,
> &dev->i2c_adap);
> attach_xc3028 = 1;
> break;
> +#if 1
> + /*FIXME: What frontend does Videomate T750 use? */
> + case SAA7134_BOARD_VIDEOMATE_T750:
> + printk("Compro VideoMate T750 DVB setup\n");
> + dev->dvb.frontend = dvb_attach(zl10353_attach,
> +
> &videomate_t750_zl10353_config,
> + &dev->i2c_adap);
> + if (dev->dvb.frontend != NULL) {
> + printk("Attaching pll\n");
> + // if there is a gate function then the i2c bus
> breaks.....!
> + dev->dvb.frontend->ops.i2c_gate_ctrl = 0;
> +
> + if (dvb_attach(qt1010_attach,
> + dev->dvb.frontend,
> + &dev->i2c_adap,
> + &videomate_t750_qt1010_config) ==
> NULL)
> + {
> + wprintk("error attaching QT1010\n");
> + }
> + }
> + break;
> +#endif
> case SAA7134_BOARD_MD7134_BRIDGE_2:
> dev->dvb.frontend = dvb_attach(tda10086_attach,
> &sd1878_4m,
> &dev->i2c_adap);
>
Ok, here is the physical electrical connections I had posted elsewhere...
The RTC is connected to the I2C buss from the SAA7135, the INT
output is connected thru a custom driver chip (seems like just a custom
driver similar to a ULN2004 driver chip, I doubt its I2C, it wouldn't
buzz out to that chip, the following addresses are the hard wired
addresses on the PCB
I2C addresses
QT1010 = 0xA0 DVB Front End (#)
DS1337 = 0xD0 RTC, the Alarm out restarts the computer
HT24LC02 = 0xA0 CMOS 2K 2-wire serial EEPROM (#)
XC2028 = 0x Analog/Radio front End (Difficult to get
address info, as its a BGA)
CE6353 = 0x1E Nordig Unified DVB-T CDFDM Terrestrial
Demodulator
(#) Now, as you notice, the I2C address for the QT1010 and the EEPROM
have the same address (0xA0) I feel (assume, could be wrong) that the
I2C for the QT device is wired to the 2nd port of the CE6353 device
QT1010 (module)
DS1337 (module)
XC2028 (CX8800 = module) or CX88... series modules
CE6353 not sure of the module for this yet... not sure how
programmable it is
Have a PDF of the QT1010, cannot find the linky again
DS1337 http://datasheets.maxim-ic.com/en/ds/DS1337-DS1337C.pdf
CE6353 http://download.intel.com/design/celect/datashts/D55752.pdf
CE6353 looks pin-for-pin compatable for the following (Zarlink Devices)
http://www.pctuner.ru/files/pdf/zarlink_mt352.pdf
http://www.pctuner.ru/files/pdf/zarlink_zl10353.pdf
There is a linky on the Intel web site for cross referencing the CE
with Zarlink
Also the I2C address on the chip Doc refers to SADD0:4, in the doc,
it said that "In the current TNIM evaluation application, the 2-wire bus
address is 0001 111 R/ W with the pins connected as
follows:"
I actually found this rather difficult to understand, but I guess I
sussed it... SADD0:4 is 5 pins that are tied to Vdd or Vss, but the pin
outs state they are N.C. (Non Connected) strange..
For the T-750 the configuration is 0001 111r/w Strange how they
didn't change it, but thats what happens when you follow App notes,...
So, I hope this helps someone getting these little beasties going, I
would love to utilise them ;o)
Ok, that little bit above was posted on the MythTV-users listserv,
no one replied to it ;o(
Ok, now for more information, I havn't found this posted on the
Internet anywhere, so I did some probing myself, if I had the computer I
used to have at work, I could post almost the complete circuit diagram
gained from the PCB, and possibly got myself into some real trouble :P
I don't know what the PRO1A does, but I feel its a port driver, or a
masked ROM, or a Fuse link device...
Someone did mention that the tops of the IC's were damaged, and
difficult to read, if you live in Australia, go out and buy yourself a
bottle of "Eucalyptus Oil" it'll clean those chips up really well for
you, the device is something like a 74ALC74 (or is it ALC174, no matter,
its just a simple chip, driving the switch gear to control the outputs,
nothing really special, I think its driven a bit by the PRO1A device, if
I had that computer (mentioned above) I'd have that figgured out
I2C comms are as above, no more clarity needed I think..
I think the bit that people are having a problem with is the GPIO
connections... I'm not sure how accurate the Windoze scanner is, but
here is what I probed...
Format, is SAA7134 (SAA) -> CE6353 (CE)
SAA Pin:Desig -> CE Pin:Desig
86:GPIO0 -> 49:MDO0
85:GPIO1 -> 50:MDO1
84:GPIO2 -> 51:MDO2
83:GPIO3 -> 52:MDO3
82:GPIO4 -> 53:MDO4
81:GPIO5 -> 56:MDO5
80:GPIO6 -> 57:MDO6
79:GPIO7 -> 58:MDO7
68:GPIO16 -> 48:MOVAL
60:GPIO19 -> 47:MOSTRT
59:GPIO20 -> 61:MOCLK
Next is the GPIO to the PRO1A Device from the SAA
SAA 78:GPIO8 -> PRO1A U5:6 (U5 is the PRO1A Desig)
77:GPIO9 -> U5:7
76:GPIO10 -> U5:8
77:GPIO11 -> U5:9
61:GPIO18 -> U5:12
56:GPIO23 -> U5:13 (or 14) strange, same resistance to either pin from
GPIO23 200-500R (Ohms)
Next, not 100% sure of these being No-Connect... further
investigation (another lunch break)
72:GPIO12
71:GPIO13
70:GPIO14
69:GPIO15
58:GPIO21
57:GPIO22
89:GPIO25
88:GPIO26
87:GPIO27
Ok, I hope this helps get this little cart moving...
Well, had lunch today, and probed deeper into the card, probing with
some nice sharp test probes (POGO series from ECT)
SAA:70:GPIO14 -> RT104 -> CE:9:RESET
RT104 is missing, Reset connected to a RC circuit.
SAA:71:GPIO13 -> U5:11
SAA:72:GPIO12 -> U5:10
There are a number of Test Points (TPx) on the back, near the Analog
can,
TP9 -> Vdd
TP8 -> SAA:69:GPIO15 (with pull-up resistor)
TP6 -> SDA (I2C on SAA)
TP5 -> SCL (I2D on SAA)
TP3 -> C93 -> SAA:106:SIF
Guessing,
TP8 = Active Low signal to the XC device
TP5/6 = I2C comms (Given)
TP3 = IF signal Capactively coupled to the IF input of the SAA device
I think thats about all..
--
Qn. Whats the differance between a Snake and a Onion?
Ans. No one cries when you chop up a Snake
(SOLS - Snake Tales)
[-- Attachment #3: Type: text/plain, Size: 150 bytes --]
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 4+ messages in thread
* [linux-dvb] [Fwd: Re: Try to Make DVB-T part of Compro VideoMate T750 Work]
@ 2008-05-09 23:58 Rod
0 siblings, 0 replies; 4+ messages in thread
From: Rod @ 2008-05-09 23:58 UTC (permalink / raw)
To: linux-dvb
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: Re: [linux-dvb] Try to Make DVB-T part of Compro VideoMate T750 Work.eml --]
[-- Type: message/rfc822, Size: 4035 bytes --]
From: "Rod Smart" <Rod@Rods.id.au>
To: "lin" <b87605214@ntu.edu.tw>
Subject: Re: [linux-dvb] Try to Make DVB-T part of Compro VideoMate T750 Work
Date: Fri, 9 May 2008 12:26:08 +1000 (EST)
Message-ID: <1040.58.105.235.135.1210299968.squirrel@www.rods.id.au>
> On 2008 May 9 Friday 07:31:15 you wrote:
>> > On 2008 May 8 Thursday 22:46:09 Rod wrote:
>> >> Hi, is there anyone actually working on this?
>> >>
>> >> I cannot program for the life of me (for now) si, I'd like some
>> >> assistance?
>> >>
>> >> I can get the SAA to be seen on the I2C bus, and a scan doesn't
>> >> reveal the true addresses of the chips behind it (along with the
>> >> previously seen reports of the addresses of the devices.
>> >>
>> >> I have manually probed and have obtained the actual I2C
>> addressing
>> >> of most of the chips (except for the XC device, BGA's are difficult,
>> and
>> >> the PRO1A, well I havn't gone to the length of X-ray'ing it yet, but
>> >> maybe I'll have to give that a go (X-ray to get the die information,
>> >> then try and resolve its function from that info) or I'll just power
>> the
>> >> device and see what it does.. wish i still had the "Pinpoint" system
>> at
>> >> my disposal.
>> >>
>> >> So, I'm looking for help, or a group to chat with to try and help
>> >> this little device along ;o)
>> >> _______________________________________________
>> >> linux-dvb mailing list
>> >> linux-dvb@linuxtv.org
>> >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>> >
>> > Hi, Rod:
>> >
>> > I'm just a little owner of T750, and not a electrical circuit expert.
>> I
>> > just
>> > can read some code of kernel drivers. I do definitly want to give you
>> a
>> > hand
>> > and make this cards work over v4l, but what can I do for you? I live
>> in
>> > Taiwan, if it necessary and Compro wants to tell me, I can give Compro
>> a
>> > call
>> > and ask some questions which may keep this branch forward.
>> >
>> > 2008/05/08
>> > linleno
>>
>> Hi Linleno
>>
>> I have the I2C ports that each device sits on (except the XC device)
>> that
>> i probed from the board, I have the interconnections between the SAA and
>> the 6353 device, and I think (couldn't find/forgot) the QT1010 is
>> connected to the 6353 Secondary I2C port for tuning control.
>>
>> The Reset line on the '6353 is tied to a RC network, with an option to
>> be
>> controlled from the SAA device, this link can be added at another time.
>>
>> I'd also like to be able to control the RTC on the board so I can
>> restart
>> the computer at a certain time, the Linux drivers for controlling my
>> mobo
>> don't work, and screw the BIOS ;o(
> HI, Rod:
>
> So, you can determinate the demodulator on this card is CE6353 but not
> zl10353
> as Newbigin proposed?
>
> Lin
>
>
Hi Lin,
So, you mean as te connection as SAA -> CE6353 -> QT1010?
I'll pull the card again, desolder the can and try to see where those
SDA/SCL tracks run, I have some fine test probes that I can use to probe
those points, the company I work for sells the Ingin & ECT board test
probes for testing of bare and loaded PCB's, so probing won't be a
problem.
I also found that Eucalyptus oil is great for removing the paint on the
tops of some IC chips ;o)
--
Qn. Whats the differance between a Snake and a Onion?
Ans. No one cries when you chop up a Snake
(SOLS - Snake Tales)
[-- Attachment #3: Type: text/plain, Size: 150 bytes --]
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 4+ messages in thread
* [linux-dvb] [Fwd: Re: Try to Make DVB-T part of Compro VideoMate T750 Work]
@ 2008-05-09 23:58 Rod
0 siblings, 0 replies; 4+ messages in thread
From: Rod @ 2008-05-09 23:58 UTC (permalink / raw)
To: linux-dvb
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: Re: [linux-dvb] Try to Make DVB-T part of Compro VideoMate T750 Work.eml --]
[-- Type: message/rfc822, Size: 3130 bytes --]
From: "Rod Smart" <Rod@Rods.id.au>
To: "lin" <b87605214@ntu.edu.tw>
Subject: Re: [linux-dvb] Try to Make DVB-T part of Compro VideoMate T750 Work
Date: Fri, 9 May 2008 09:31:16 +1000 (EST)
Message-ID: <3720.58.105.235.135.1210289476.squirrel@www.rods.id.au>
> On 2008 May 8 Thursday 22:46:09 Rod wrote:
>> Hi, is there anyone actually working on this?
>>
>> I cannot program for the life of me (for now) si, I'd like some
>> assistance?
>>
>> I can get the SAA to be seen on the I2C bus, and a scan doesn't
>> reveal the true addresses of the chips behind it (along with the
>> previously seen reports of the addresses of the devices.
>>
>> I have manually probed and have obtained the actual I2C addressing
>> of most of the chips (except for the XC device, BGA's are difficult, and
>> the PRO1A, well I havn't gone to the length of X-ray'ing it yet, but
>> maybe I'll have to give that a go (X-ray to get the die information,
>> then try and resolve its function from that info) or I'll just power the
>> device and see what it does.. wish i still had the "Pinpoint" system at
>> my disposal.
>>
>> So, I'm looking for help, or a group to chat with to try and help
>> this little device along ;o)
>> _______________________________________________
>> linux-dvb mailing list
>> linux-dvb@linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
> Hi, Rod:
>
> I'm just a little owner of T750, and not a electrical circuit expert. I
> just
> can read some code of kernel drivers. I do definitly want to give you a
> hand
> and make this cards work over v4l, but what can I do for you? I live in
> Taiwan, if it necessary and Compro wants to tell me, I can give Compro a
> call
> and ask some questions which may keep this branch forward.
>
> 2008/05/08
> linleno
>
Hi Linleno
I have the I2C ports that each device sits on (except the XC device) that
i probed from the board, I have the interconnections between the SAA and
the 6353 device, and I think (couldn't find/forgot) the QT1010 is
connected to the 6353 Secondary I2C port for tuning control.
The Reset line on the '6353 is tied to a RC network, with an option to be
controlled from the SAA device, this link can be added at another time.
I'd also like to be able to control the RTC on the board so I can restart
the computer at a certain time, the Linux drivers for controlling my mobo
don't work, and screw the BIOS ;o(
--
Qn. Whats the differance between a Snake and a Onion?
Ans. No one cries when you chop up a Snake
(SOLS - Snake Tales)
[-- Attachment #3: Type: text/plain, Size: 150 bytes --]
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-05-10 3:02 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-05-09 23:57 [linux-dvb] [Fwd: Re: Try to Make DVB-T part of Compro VideoMate T750 Work] Rod
-- strict thread matches above, loose matches on Subject: below --
2008-05-09 23:58 Rod
2008-05-09 23:58 Rod
2008-05-07 22:34 Rod
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox