On Tue, 2009-04-07 at 03:36 +0000, Jeffrey Baker wrote:
> Building these modules into the kernel, at this extremely late stage in
> the Jaunty development cycle, doesn't seem like a particularly good
> idea. Among other things, it has implications for laptop users who are
> trying to minimize power consumption, and it makes life unnecessarily
> difficult for users of VMWare Workstation which has numerous unusual use
> cases of USB peripherals.
>
Why?
Whether or not they're built in or modules, they still have to be loaded
for your USB hardware to work.
Whether or not they're built in or modules, you can still disable
individual host control interfaces - the method is just slightly
different (though since the one that works for built-ins ALSO works for
modules, we should arguably be documenting that one instead of the
blacklist trick).
This has solved the bug where ehci was loaded second, therefore the host
controller placed in the wrong mode.
Scott
--
Scott James Remnant
<email address hidden>
On Tue, 2009-04-07 at 03:36 +0000, Jeffrey Baker wrote:
> Building these modules into the kernel, at this extremely late stage in
> the Jaunty development cycle, doesn't seem like a particularly good
> idea. Among other things, it has implications for laptop users who are
> trying to minimize power consumption, and it makes life unnecessarily
> difficult for users of VMWare Workstation which has numerous unusual use
> cases of USB peripherals.
>
Why?
Whether or not they're built in or modules, they still have to be loaded
for your USB hardware to work.
Whether or not they're built in or modules, you can still disable
individual host control interfaces - the method is just slightly
different (though since the one that works for built-ins ALSO works for
modules, we should arguably be documenting that one instead of the
blacklist trick).
This has solved the bug where ehci was loaded second, therefore the host
controller placed in the wrong mode.
Scott
--
Scott James Remnant
<email address hidden>