Eric- Thanks for the info, I will give it a try tonight. As for V4L as a whole, how stable is it? I had it crash my machine last night... it was my first lockup in about 15 months. Also, since I have a Hauppauge, do I have to worry about backing up the eeprom? If it does get nuked, and I don't have a backup... can I get it from somewhere? Thank you so much for your time! Ryan -----Original Message----- From: Eric Jorgensen [mailto:alhaz@xxxxxxxxxxxx] Sent: Tuesday, August 15, 2000 10:39 AM To: video4linux-list@xxxxxxxxxx Subject: Re: [V4L] Trouble Getting WinTV Go! to work. > to grab i2c-2.5.2. When I try and "make" bttv, it bombs out with errors > like this: > > [snip] > msp3400.c: At top level: > msp3400.c:1256: warning: `struct i2c_adapter' declared inside parameter list > msp3400.c:1257: conflicting types for `msp_probe' > msp3400.c:1095: previous declaration of `msp_probe' > msp3400.c: In function `msp_probe': > msp3400.c:1258: dereferencing pointer to incomplete type > msp3400.c:1258: `I2C_ALGO_BIT' undeclared (first use in this function) > msp3400.c:1258: `I2C_HW_B_BT848' undeclared (first use in this function) > msp3400.c:1259: warning: implicit declaration of function `i2c_probe' You have to patch your kernel with the i2c code, compile all the new i2c stuff as modules, recompile your kernel as well, and then compile bttv. Good luck. - Eric _______________________________________________ Video4linux-list mailing list Video4linux-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/video4linux-list
