Hans, Andy Walls wrote: > Here are hashes for the firmwares I have in use on my system: > > $ md5sum /lib/firmware/v4l-cx25840.fw /lib/firmware/v4l-cx23418-dig.fw > 99836e41ccb28c7b373e87686f93712a /lib/firmware/v4l-cx25840.fw > b3704908fd058485f3ef136941b2e513 /lib/firmware/v4l-cx23418-dig.fw > > Regards, > Andy
On Thu, 2009-09-10 at 21:09 -0500, Chris Kennedy wrote: > My checksums are a little odd, because the one of yours for the cx23418 > is the same as my 25840... > > b3704908fd058485f3ef136941b2e513 /lib/firmware/v4l-cx25840.fw > 9b39b3d3bba1ce2da40f82ef0c50ef48 /lib/firmware/v4l-cx2341x-enc.fw > > These are the same from the bundle on ivtvdriver.org. Andy Walls wrote: >Chris kennedy wrote: >> cx25840 3-0044: Audio status: nber nll ifl fdl afc amc ac97 > ^^^^^^^^ ^^^ > The NICAM (French?) audio status flags seem just plain wrong. 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. Regards, Andy _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
