IF YOU ARE LOOKING FOR ANSWERS TO THE 'tveeprom_hauppauge_analog' problem, go to the bottom of this message.
[EMAIL PROTECTED] wrote: > Date: Sat, 14 Jan 2006 19:57:50 -0500 > From: "R. G. Newbury" <[EMAIL PROTECTED]> > > This piece of advice in the wiki is (now) backwards: > > "There is work at the moment to merge these conflicting versions, but in > the meantime the kernel version has to go:" > >Can you double-check (from archives, Hans, or some other source) that >this is true, and then update the wiki so people don't get confused? >(Or, if you'd rather not update the wiki, I will, but I'd rather get a >second opinion on this, since I don't have direct experience with >either 500's or pc3000's. And is this something that's changed >between 0.4.0 and later versions? If so, updating the wiki will have >to account for that and speak the truth in all cases. I've been >tweaking the ivtvdriver wiki a little bit, but the last thing I'd >want to do is update it incorrectly.) > >(I'm a big believer in shoving as much information and operational >experience into the ivtvdriver and mythtv wikis as possible, since it >should decrease traffic and frustration a lot if all this stuff can >stay centralized instead of requiring lots of list searching---with >its uncertain keywords, outdated and incomplete information, and all >the rest... :) > > Well there was a thread on the ivtv list (IIRC) starting in August or so, and ending iearly in October where using the kernel module was discussed and Keith noted that he had taken the code for the dvb tveeprom and the ivtv tveeprom and shoehorned them together. Shortly thereafter, the 2.612 (?) kernel came out, with the dvb modules included. And some messages turned up on (again IIRC) both the ivtv and mythtv lists recommending using the kernel module ONLY IF YOU WERE USING BOTH TYPES OF CARDS. And there was a strong implication that the ivtv driver code had been rewritten to make use of either tveeprom.ko module. The person who would know for sure would be Hans. This is the thread: http://www.gossamer-threads.com/lists/ivtv/devel/24235?search_string=tveeprom%20kernel;#24235 The end of the thread is this message from 'Hans' (and I think this is the 'right' Hans). *************************************************** On Tuesday 04 October 2005 23:45, Keith C wrote: > On Oct 4, 2005, at 4:10 PM, Mercury Morris wrote: > > On 9/23/05, Adam Forsyth <agforsyth[at]gmail.com> wrote: > > Well, I just gave up and am now using the *tveeprom* that came with my > > *kernel*. But I'd still love to know what the cx88xx / cx8800 module is > > for. > > > > Hello, > > > > *kernel*: cx88xx: disagrees about version of symbol > > tveeprom_hauppauge_analog > > Yep, thats the one I was getting. > > > So, Googled for some help and found this thread. That's why I'm > > posting this > > reply. The previous posts (above) gave me the idea to swap > > "*tveeprom*" modules, which is exactly what I did. I re-renamed the > > ".orig" back to normal, > > renamed the ivtv version to have the suffix ".ivtv", issued a > > "depmod -ae" command, and checked the results with a "modinfo > > *tveeprom*" command. > > > > Then I rebooted. This time no errors, no errors of any kind. The > > PVR-350 card > > works, the HD-3000 card works, and the remote (ATI Remote Wonder) > > works, too! > > You're lucky. Glad the *kernel* *tveeprom* works for you. I never could > get it to work with my card, so I had to make my own *tveeprom* module > that is a hybrid between the *kernel* and ivtv version. And is slowly > getting out of sync with both. Keith, Can you mail me the *kernel* *tveeprom*.c? And also which *kernel* version it is exactly (version and from which distro, usually uname -a gives this info). Hans ************************************************* NOTE: IN LOOKING FOR THAT THREAD I CAME ACROSS THIS MESSAGE WHICH WAS PART OF THE ANNOUNCEMENT OF THE .5.1 VERSION.!!! Just for the records: One importtant thing I have noticed with 0.5.0 / 0.5.1 / SVN HEAD is that you need to (cd v4l-*kernel*; make distclean) before compiling ivtv for a updated *kernel*. Otherwise v4l ist built/installed for the old *kernel* and ivtv complains about missing symbols tveeprom_read and tveeprom_hauppauge_analog. Geoff _______________________________________________ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
