Quoting Axel Thimm <[EMAIL PROTECTED]>: >> This isn't true if you need Samsung tuner support - the kernel >> modules do not >> have support for the Samsung TCPN tuner on new PVR-500s, and so in >> the case of >> PVR-500 boards with the new Samsung tuner, you have to go back to the >> "old way" >> of doing things. Of course, if they're using RPMs that didn't have >> the Kbuild >> files modified to build those modules in the first place, things won't work >> anyway. > > The rpms package up what the ivtv buildsystem decides to build for > that kernel. E.g. there is no control mechsnism in the rpm layer, you > get what you'd get if you would build it yourself. This is what I guessed. The end result is that the RPMs will *not* work for anyone who has a Samsung tuner - they will have to manually build ivtv themselves.
> Hans turned off the build of certain kernel modules for 2.6.15 because > the support is now in the kernel. Did you try the Samsung tuner > support with 2.6.15? If ivtv 0.4.2 had better tuner kernel modules > than 2.6.15, Hans wouldn't had turned it off. No, it makes sense to turn building of ivtv's own tveeprom/tuner modules off by default, since they are of no benefit to 95%+ of ivtv users - only those who have Samsung tuners on a recent PVR-500 (not supported by the 2.6.15 kernel modules, as Samsung support was added in early-to-mid January, which is after 2.6.15's release) have a need for the ivtv tuner modules, which is why getting them to build requires modifying one of the Kbuild files in the ivtv distribution. (There's a README file somewhere in the distribution that covers the exact details of how, I don't have access to it at the moment as I'm not at home. To those users with a PVR-500 and a Samsung tuner that haven't gotten it up and running yet, I strongly suggest reading that README, and also reading anything PVR-500 related in the past 2-3 weeks of the mailing list archives, since proper Samsung tuner support requires an additional patch against the 0.4.2 release.) Note that in this situation, some form of conflict resolution between the ivtv modules and the kernel-provided modules will have to be performed. One method is to use modules.conf (or the equivalent file) and rename the ivtv-based modules to modulename-ivtv.ko and force those to load. The other (which is how I do it) is to rename the kernel modules to tveeprom.ko.bak and tuner.ko.bak, and leave the ivtv-based ones as tveeprom.ko and tuner.ko. Fortunately most of these problems except for the issue of bad lowband performance on tuner 0 will go away with 2.6.16, which according to Hans has the patches for Samsung TCPN tuner support integrated. Solving the bad lowband performance issue will most likely require a lot of trial and error or someone obtaining complete i2c logs from a recent PVR-500 on a Windows box (which does not exhibit bad lowband performance on tuner 0.) The end conclusion is: Do not try to use precompiled RPMs for a PVR-500 with the new Samsung tuner, at least not with kernel 2.6.15 + ivtv 0.4.2. _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
