Hi Kevin, On Thu, 2005-01-27 at 09:24 -0800, kevin thayer wrote: > The reason for the -ivtv versions is that the ivtv > modules are branches from the mainline kernel > versions, and other (non-ivtv) hardware uses them. It > wouldn't be playing nice to simply remove or overwrite > the kernel versions of things with our own. >
That makes some sense, but then, why is the main ivtv kernel module not named differently? Also, why is the ivtv module that should use the tveeprom-ivtv module loading the tveeprom one instead? Wouldn't it make more sense that, if you're going to install parallel modules that you: a) name them all consistently, b) have the new modules load their appropriate dependencies directly. > audio for the [23]50 series cards is handled by the > msp3400 driver. make sure you use the ivtv version. > Yep, got that working this morning. The 250 and the 350 seem to not mix well together in the same machine, but that doesn't matter since we're not going to use the 250 in the end anyway. > it comes up a lot to do > > alias msp3400 msp3400-ivtv > and > alias tveeprom tveeprom-ivtv > > in modules.conf > Again, I really feel this should not be necessary. If I load the ivtv module, and that module decides to load dependencies for me, and those dependencies require the -ivtv versions, then it should load those versions. Otherwise, it should simply just not load the dependencies. I find the above "fix" more of a "hack" to work around an inconsistent naming and dependency conflict. > I for one am astounded at the number of people who > read the wiki and can't find their solution, but then > find it on the mailing-list and do not update the wiki > to help others. > > The whole point of the wiki system is distributed > document management and it lets anyone update it. Own > your solutions, people :) > Actually, a Wiki is the worst thing in the world for finding stuff. You may know where it is since you wrote it originally, but I swear I looked through that thing and can't find anything related to this particular problem. Also, once I look through the FAQ and still see references to "test_ioctl" rather than ivtvctl, I think it's out of date and decide that maybe this is a recent event. The biggest reason why I and other users are reluctant to edit a project's wiki is that we go to the wiki to find expert information. This means I'm not an expert, so I'm not going to edit it yet. Once I find the full answer, and once I've exhausted getting the root problem solved, then I'll probably post something for you. But, expecting a user to update your wiki for you, when you don't even update it (why is test_ioctl still mentioned) is a little presumptuous don't you think? Lead by example I say. Your thoughts? -- Zed A. Shaw http://www.zedshaw.com/ ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
