Hm, Kudzu shouldn't care, you just should not be able to load the
usb-ohci module on startup. At least that's what happens to me on my
boxes.
Anyway, here's the documentation that you need:
The module usb-ohci is now gone. Use ohci-hcd instead.
The people with UHCI controllers have a big more documentation to read:
The module uhci is now gone. If you used this module, use
uhci-hcd instead. The module usb-uhci is now gone. If you used
this module, use usb-uhci-hcd instead. If you have a preference
over which UHCI module works better for you, please email
greg@kroah.com your comments, as one of these modules will be
going away in the near future.
> Most likely this would be of course module aliasing entires
> which could be used in /etc/modules.conf to cheat around
> kudzu - this way it would be for example possible
> to have a nice dual boot configuration.
Heh, I don't mess around with module aliasing, so I don't know the first
thing of what to do in this situation. Someone reading the above
documentation should be able to figure it all out.
> (I can adjust my boot scripts to set up an apriopriate symlink
> from /etc/modules.conf to modules-2.5.18.confg and
> modules-2.4.18.conf debpending what I'm booting anyway...)
>
> In short - if you change something about the configuration
> and usage - just document it please.
We really don't use CHANGES anymore. Where do you propose things like
the above few sentences go to where everyone will know to look?
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/