I have 3 firmware versions here, here are the md5's c34803bc1ca86567076ac7dc0df91076 /usr/portage/distfiles/pvr250_17_21288.exe 173c5ce2c0f16da42a5316ef7cee6834 /usr/portage/distfiles/pvr250_18a_inf.zip dff9c5cd9b50140c6bc3180f264557c7 /usr/portage/distfiles/pvr48wdm_1.8.22037.exe
I'm using the last one which has md5's # md5sum /lib/modules/ivtv-fw-* 305dba74bbe5905447add8883f3ecb68 /lib/modules/ivtv-fw-dec.bin ab75947ef1b086e26f9b08e628baa02e /lib/modules/ivtv-fw-enc.bin this gives in dmesg: ivtv: Encoder revision: 0x02040011 ivtv: Decoder revision: 0x02020023 On Friday 03 December 2004 16:21, Greg Estabrooks wrote: > >ftp://ftp.shspvr.com/download/wintv-pvr_250-350/win9x-2k-xp_mpeg_wdm_drv/p > >vr48w dm_1.8.22037.exe > > when you use it, dmesg will say: > > ivtv: Encoder revision: 0x02040011 > > ivtv: Decoder revision: 0x02020023 > > Now I just grab the firmware from that exact file and it's showing the > buggy Encoder version, are you sure that you used that file ? > > ivtv: Encoder revision: 0x02040024 > ivtv: Decoder revision: 0x02020023 > > > > ------------------------------------------------------- > 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://productguide.itmanagersjournal.com/ > _______________________________________________ > 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://productguide.itmanagersjournal.com/ _______________________________________________ ivtv-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
