On Thu, 27 Jan 2005 21:53:27 -0500, Zed Shaw <[EMAIL PROTECTED]> wrote: > 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.
The modules actually are named "msp3400.ko" and "tveeprom.ko". When they are packaged the filenames are changed so that it's possible to distinguish between the modified ivtv ones and the ones already a part of your system. When v4l contains all the extra definitions that the ivtv modules contain- this temporary solution will no doubt go away. -- Tyler Trafford ------------------------------------------------------- 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
