On Tue, 2009-09-15 at 14:27 +1200, Robin Gilks wrote: > > Andy Walls wrote: > > > Given the testing Chris has done with my patches, it looks like using > > CX23418 A/V core firmware with a CX25843 is returning non-sensical > > cominations of interrupt status flags in the audio interrupt status > > register (0x819 IIRC) of the CX25843. > > > > In the above the NICAM related flags don't make sense and neither does > > the AC97 status. The (S)IF L(ost) flag makes no sense with the format > > detection flags and ormat detetction loop complete flags, etc. Rarely > > do I get more than 1 flag other than RDS (which is always set for me). > > When I do get multple flags at once, its FDL and AFC (IIRC). > > > > Could you revert the firmware archive to use a known CX2584x specific > > firmware for the cx25840 firmware file in the archive at > > dl.ivtvdriver.org? > > > > I suspect the CX23418 firmware image being distributed as CX2584x > > firmware is causing problems for CX2584x chips. > > I'm seeing more and more of this bad audio problem with a PAL PVR150 using > the line input audio and more recent kernel versions (currently Linux > jupiter 2.6.30-gentoo-r4 #2 SMP Thu Aug 13 23:54:02 NZST 2009 x86_64 AMD > Athlon(tm) Dual Core Processor 5050e AuthenticAMD GNU/Linux) and newer > (faster) hardware. > > Is there an md5sum that would identify a known good firmware? The files in > the archive are not very well described (dates don't mean much to me). I'm > also a bit confused by the device numbers as my dsmeg quotes both cx23416 > and cx25840
I use this (possibly ancient) firmware with my PVR-150MCE: $ md5sum /lib/firmware/v4l-cx25840.fw 99836e41ccb28c7b373e87686f93712a /lib/firmware/v4l-cx25840.fw it works wellfor me, but I barely use analog anymore. IIRC, I pulled the file from the Windows driver CD for my Hauppauge card. MakoC.rom or something like that. The CX23416 is the MPEG encoder, the CX2584[0123] is a broadcast TV Video and Audio signal decoder and digitizer that feeds digitized video and audio data to the CX23416 encoder for MPEG encoding. Regards, Andy > This is what I get at startup - very standard Gentoo fare... > > Sep 13 12:14:39 jupiter ivtv: Start initialization, version 1.4.1 > Sep 13 12:14:39 jupiter ivtv0: Initializing card 0 > Sep 13 12:14:39 jupiter ivtv0: Autodetected Hauppauge card (cx23416 based) > Sep 13 12:14:39 jupiter ivtv 0000:01:09.0: PCI INT A -> Link[APC2] -> GSI > 17 (level, low) -> IRQ 17 > Sep 13 12:14:39 jupiter ivtv0: Unreasonably low latency timer, setting to > 64 (was 32) > Sep 13 12:14:39 jupiter ivtv0: Autodetected Hauppauge WinTV PVR-150 > Sep 13 12:14:39 jupiter cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c > driver #0) > Sep 13 12:14:39 jupiter tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #0) > Sep 13 12:14:39 jupiter tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0) > Sep 13 12:14:39 jupiter wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0) > Sep 13 12:14:39 jupiter IRQ 17/ivtv0: IRQF_DISABLED is not guaranteed on > shared IRQs > Sep 13 12:14:39 jupiter ivtv0: Registered device video0 for encoder MPG > (4096 kB) > Sep 13 12:14:39 jupiter ivtv0: Registered device video32 for encoder YUV > (2048 kB) > Sep 13 12:14:39 jupiter ivtv0: Registered device vbi0 for encoder VBI > (1024 kB) > Sep 13 12:14:39 jupiter ivtv0: Registered device video24 for encoder PCM > (320 kB) > Sep 13 12:14:39 jupiter ivtv0: Registered device radio0 for encoder radio > Sep 13 12:14:39 jupiter ivtv0: Initialized card: Hauppauge WinTV PVR-150 > Sep 13 12:14:39 jupiter ivtv: End initialization > Sep 13 12:14:42 jupiter ivtv 0000:01:09.0: firmware: requesting > v4l-cx2341x-enc.fw > Sep 13 12:14:43 jupiter ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 > bytes) > Sep 13 12:14:43 jupiter ivtv0: Encoder revision: 0x02060039 > Cheers > _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
