I've tested your patch on the 2.6.16-1.2122_FC5 as below.... -rmmod all the related modules -patch -p0 on the 0.6.2 source (which succeeded) -make && make install -modprovbe ivtv
(Got the same result with a 'reboot'. I did not do a 30-second cord-out power cycle though) ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.6.2 (tagged release) loading ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS gcc-4.1 ivtv: In case of problems please include the debug info between ivtv: the START INIT IVTV and END INIT IVTV lines, along with ivtv: any module options, when mailing the ivtv-users mailinglist. ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based) ivtv0: Unreasonably low latency timer, setting to 64 (was 32) tveeprom 1-0050: Huh, no eeprom present (err=-121)? tveeprom 1-0050: Encountered bad packet header [00]. Corrupt or not a Hauppauge eeprom. ivtv0: No tuner detected, default to NTSC ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0: Encoder revision: 0x02050032 ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c! ivtv0: i2c addr 0x44 not found for command 0x40045613! ivtv0: i2c addr 0x44 not found for command 0xc0045627! ivtv0: i2c hardware 0x00000020 not found for command 0x40345622! ivtv0: i2c addr 0x44 not found for command 0x40345622! ivtv0: i2c addr 0x44 not found for command 0x40045612! ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c! ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c! ivtv0: i2c addr 0x44 not found for command 0x40045613! ivtv0: i2c addr 0x44 not found for command 0x40045612! ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c! ivtv0: Initialized Hauppauge WinTV PVR-150, card #0 ivtv: ==================== END INIT IVTV ==================== ----- Original Message ----- From: "Simon Baxter" <[EMAIL PROTECTED]> To: "Discussion list for development of the IVTV driver" <[email protected]> Sent: Thursday, June 01, 2006 1:51 PM Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0 > I'm running the version currently on svn (0.8.0), but have a > kernel/modules installed with the 0.6.2. Which would you like me to test > this on? > > > ----- Original Message ----- > From: "Hans Verkuil" <[EMAIL PROTECTED]> > To: "Discussion list for development of the IVTV driver" > <[email protected]> > Sent: Thursday, June 01, 2006 1:27 PM > Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0 > > >> Can you (and anyone else with tveeprom problems) try the following: >> >> Tf you are running ivtv-0.6, then you need to apply the attached patch >> to ivtv and recompile/install. It's not needed for ivtv-0.4.5. >> >> Next add the newi2c=0 ivtv module option. Now load ivtv and see if this >> makes any difference. >> >> Please let me know what the result is. >> >> Thanks, >> >> Hans >> >> On Thursday 01 June 2006 21:28, Simon Baxter wrote: >>> I'm now running kernel 2.6.17-rc5, which included a bunch of patches >>> relating to v4l and i2c, and have upgraded to GCC 4.1.1. Then >>> recompiled the ivtv and v4l-dvb sources from svn. I'm tempting fate >>> saying this, but seem to be experiencing a period of stability - >>> except for a couple of errors around: >>> tveeprom 0-0050: Encountered bad packet header [ff]. Corrupt or not a >>> Hauppauge eeprom. >>> >>> >>> >>> Biggest difference I've noticed with this combination is the order >>> the i2c devices appear on the bus. In 2.6.16.XXX and GCC 4.1.0, they >>> were: Installed I2C busses: >>> i2c-1 unknown ivtv i2c driver #0 >>> Algorithm unavailable >>> i2c-0 unknown SMBus Via Pro adapter at 5000 >>> Algorithm unavailable >>> >>> >>> >>> with 2.6.17-rc5 and GCC 4.1.1 they're: >>> Installed I2C busses: >>> i2c-1 unknown SMBus Via Pro adapter at 5000 >>> Algorithm unavailable >>> i2c-0 unknown ivtv i2c driver #0 >>> Algorithm unavailable >>> >>> >>> >>> _______________________________________________ >>> ivtv-devel mailing list >>> [email protected] >>> http://ivtvdriver.org/mailman/listinfo/ivtv-devel >> > > > -------------------------------------------------------------------------------- > > >> _______________________________________________ >> ivtv-devel mailing list >> [email protected] >> http://ivtvdriver.org/mailman/listinfo/ivtv-devel > > > > _______________________________________________ > ivtv-devel mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-devel _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
