Greetings, Hans. I initially tried to use Fedora 8 and a 2.6.23 kernel, but could not get it to run as I've previously reported.
I've switched to trying Mythdora 4, with the kernel upgraded to 2.6.22.14-72.fc6, as the basis for trying to get the beta driver(s) to work for me. I'm getting the same sort of results that others have reported with the previous driver. This morning, I've tried the driver cx18-1a65fdfd182d.tar.bz2 with near identical results. I got this driver by going to http://www.linuxtv.org/hg/~hverkuil/cx18/ and clicking the link bz2. The dmesg data is: cx18: Start initialization, version 0.1.0 cx18-0: Initializing card #0 cx18-0: Autodetected Hauppauge card ACPI: PCI Interrupt 0000:01:07.0[A] -> GSI 16 (level, low) -> IRQ 17 cx18-0: cx23418 revision 01010000 (B) tveeprom 1-0050: Hauppauge model 74041, rev C5B2, serial# 2728115 tveeprom 1-0050: MAC address is 00-0D-FE-29-A0-B3 tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 50) tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08) tveeprom 1-0050: audio processor is CX23418 (idx 38) tveeprom 1-0050: decoder processor is CX23418 (idx 31) tveeprom 1-0050: has no radio, has IR receiver, has IR transmitter cx18-0: Autodetected Hauppauge HVR-1600 tuner 2-0061: chip found @ 0xc2 (cx18 i2c driver #0-1) cs5345 1-004c: chip found @ 0x98 (cx18 i2c driver #0-0) cx18-0: Disabled encoder IDX device cx18-0: Registered device video0 for encoder MPEG (2 MB) cx18-0: Registered device video16 for TS (2 MB) cx18-0: Registered device video32 for encoder YUV (2 MB) cx18-0: Registered device vbi0 for encoder VBI (1 MB) cx18-0: Registered device video24 for encoder PCM audio (1 MB) tuner-simple 2-0061: type set to 50 (TCL 2002N) cx18-0: Initialized card #0: Hauppauge HVR-1600 cx18: End initialization At the point where I try the "cat /dev/video0 > test.mpg", I see: cx18-0: Mismatch at offset 3010 cx18-0: Retry loading firmware cx18-0: Mismatch at offset 21574 cx18-0: Failed to initialize on minor 0 from dmesg. The ESMT IC has this information on it: ESMT M13S128324A- 5B AZR1P62U001 704 Regards, Robert On 12/30/2007 9:18 AM, Hans Verkuil wrote: > On Saturday 29 December 2007 01:21, Andrew Steets wrote: > >> Hello, >> >> I am playing with the cx18 driver with a WinTV-HVR 1600. >> >> I can't seem to get past the cpu firmware load. I added some debug >> statements to the driver to see where it was getting stuck. >> >> Occasionally I get errors loading the apu firmware. That looks like >> this: >> >> [ 1749.500856] cx18-0 info: Begin cx18_firmware_init >> [ 1749.504247] cx18-0 info: Begin load_apu_fw_direct >> [ 1749.513396] cx18-0 info: load segment a00000-a07fff >> [ 1749.523014] cx18-0 info: load segment ae0000-ae00ff >> [ 1749.523259] cx18-0 info: load segment b00000-b1a65f >> [ 1749.549837] cx18-0: Mismatch at offset 18134 >> >> But usually it succeeds after retrying. That looks like this: >> >> [ 1751.045638] cx18-0 info: Begin cx18_firmware_init >> [ 1751.050283] cx18-0 info: Begin load_apu_fw_direct >> [ 1751.054884] cx18-0 info: load segment a00000-a07fff >> [ 1751.064483] cx18-0 info: load segment ae0000-ae00ff >> [ 1751.064564] cx18-0 info: load segment b00000-b1a65f >> [ 1751.099571] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000 >> (141200 bytes) >> >> But then the cpu firmware load always fails with this message: >> >> [ 1752.595009] cx18-0 info: Begin load_fw_direct: v4l-cx23418-cpu.fw >> [ 1752.603761] cx18-0: Mismatch at offset 0 >> >> (I added all the "Begin " messages) >> >> I believe I have the ESMT memory on the card and I am using the >> firmware link from the cx18 announce message. >> >> I tried with and with "#if 1" and "#if 0" at line 350 in >> cx-firmware.c and I get the same results either way. I also tried >> increasing the sleep from 500ms to 1500ms and still the same result. >> It always fails at offset 0 when validating the cpu firmware load. >> > > Please update to the latest cx18 driver and try again. I received some > new timings for the memory, so perhaps this one works better. If not, > then please mail me the exact ESMT memory type used as printed on the > memory chips. > > Regards, > > Hans > _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
