Zed Shaw <[EMAIL PROTECTED]> writes: > > alias msp3400 msp3400-ivtv > > alias tveeprom tveeprom-ivtv > > > > in modules.conf > > Again, I really feel this should not be necessary.
Yes. > 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. No. Two different versions of the msp3400 (and the other) modules isn't going to fly, especially in mixed-card setups (one ivtv card, one bttv card for example). We'll need *one* module which works with *all* cards. > I find the above "fix" more of a "hack" to work around an > inconsistent naming and dependency conflict. It's a workaround for the cases where the kernel's version doesn't work correctly with ivtv (patches to fix that are welcome btw, hint, hint ...). In the long run the ivtv versions of these modules should become obsolete and this mess should go away. Extra bonus is that merging ivtv into the mainline kernel will be alot easier then ;) Gerd -- #define printk(args...) fprintf(stderr, ## args) ------------------------------------------------------- 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
