Hi Martin The output looks a lot nicer, with it listing your cards model number etc. Are you planning on releasing your new/modified software under the GPL if you are I would be grateful if you would send me a copy so I can have a play with it as well. If you do so it might be worth emailing it direct to me because I believe the list has a file size limit. I assume from the output that you use the NTSC format. I guess from what you say that my crystal which is marked as d321c4i is 32.1MHz Using the formulas on the SAA7115 data sheet and the numbers I am using they do look a bit odd, so I was thinking I might try to borrow a frequency counter to measure the freqency coming out of the SAA7115 and going into the cs53l32a so we can be certain as to exactly what is connected to where and what my settings are doing to the frequency. Refering to your comment regarding picture/sound locking I did not notice a problem with my card, however I don't know if it is relevant, but I noticed that the settings used by the linux driver for the SAA7115 sets AMCLK to free running and not frame locked which I guess might cause a slight lack of synchronization.... address 3AH set to 08H giving UCGC=0 and APLL=1.
Best Regards Trev On Tuesday 15 Feb 2005 01:41, Martin Vaughan wrote: > Hi Trev, > > I got the master frequency from the value on the xtal that is along side > the SAA7115, it is 32.1 Mhz, which also ties in with the SAA7115 AMCLK > Tables. > > For ACPF set to 03 c0 00 and at 50HZ (PAL Field), AMCLK will be 12.288 > MHZ (256 * 48 Khz) I assume AMCLK drives the CL ADC clock in. > > Also, yes I tried your new values and as you say the sound is very good, > although I noticed that picture/sound locking was poor. > > I started writing a module to program the cs53l23a regs, I can set the > registers, and read back the values, but the settings I make (including > MCLKDIV RATIO 0/1 and VOLUME/GAIN) have no effect. However, if I set > CP_EN (Control Port Enable) then this seems to change the clock ratio > (because mplayer now reports some sort of buffer error), but not to the > desired one. My theory here if that the ADC IC, as per the datasheet, > needs to be initialised properly - the datasheet (sect 6.3) explains > that after RST is brought high, the CP_EN bit must be activated before > the stand alone mode has fully initialised, which must be done within > apprx 1024 LRCK cycles. I removed my card again, and traced the reset > pin of the cl53l23a, it connects to a small 6 pin sot-23 IC which looks > like a reset controller IC, and I'm guessing that there is a manual > input reset on this 6 pin IC that connects to one of the itvc16 GPIO > lines/ports, I tracked one of the 6 pins back to the itvc16. I assume > that a reset in software can be sent to the ADC via a ITVC GPIO > Register , then the CP_EN can be activated within the desired 1024 LRCK. > I picked up a cheap latching logic probe earlier today, and I'm going to > see what happens to the RST pin on the ADC when I load/unload the > windows driver. I still need to know a bit more about the ITVC16 GPIO > setup. > > I read out the contents of the 7 byte size registers as below > > ivtv: Autodetected ADAPTEC VIDEOH! AVC-2010 card > ivtv: Found an iTVC16 based chip > ACPI: PCI interrupt 0000:00:07.0[A] -> GSI 10 (level, low) -> IRQ 10 > ivtv: Unreasonably low latency timer, setting to 64 (was 32) > ivtv: VIA PCI device: 0x3189 vendor: 0x1106 > tuner: Ignoring new-style parameters in presence of obsolete ones > saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005) > saa7115: detecting saa7115 client on address 0x42 > saa7115: writing init values > ivtv: i2c attach [client=saa7115[0],ok] > saa7115: status: (1E) 0x48, (1F) 0xc0 > starting probe for adapter ivtv i2c driver #0 (0x10005) > detecting cs53l32a client on address 0x22 > Reg 1 02 > Reg 2 00 > Reg 3 30 > Reg 4 00 > Reg 5 00 > Reg 6 01 > Reg 7 03 > Reg 1 01 > Reg 2 60 > ivtv: i2c attach [client=,ok] > ivtv: Encoder revision: 0x02040024 > ivtv: Encoder Firmware may be buggy, use version 0x02040011 > ivtv: Configuring ADAPTEC VIDEOH! AVC-2010 card with 4 streams > ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes > total > ivtv: Registered v4l2 device, streamtype 0 minor 0 > ivtv: Create DMA stream 1 > ivtv: Registered v4l2 device, streamtype 1 minor 32 > ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total > ivtv: Registered v4l2 device, streamtype 2 minor 224 > ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes > total > ivtv: Registered v4l2 device, streamtype 3 minor 24 > ivtv: Could not detect tuner standard, defaulting to NTSC. > ivtv: i2c client id: 0x02 not found! > saa7115: decoder set input (4) > saa7115: now setting Composite input > ivtv: Switching standard to NTSC. > ivtv: i2c client id: 0x02 not found! > saa7115: decoder set norm NTSC > saa7115: set audio: 0x01 > ivtv: Initialized ADAPTEC VIDEOH! AVC-2010, card #0 > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > ivtv-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ivtv-devel ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
