On Tue, Apr 7, 2009 at 10:16 AM, Scott James Remnant
<email address hidden> wrote:
> Whether or not they're built in or modules, they still have to be loaded
> for your USB hardware to work.
True.
> 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).
OK, I should research this. A laptop user can save energy by
unloading the hcd modules, which puts the corresponding PCI functions
into D3. How can you achieve the same thing with the drivers
built-in?
On Tue, Apr 7, 2009 at 10:16 AM, Scott James Remnant
<email address hidden> wrote:
> Whether or not they're built in or modules, they still have to be loaded
> for your USB hardware to work.
True.
> 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).
OK, I should research this. A laptop user can save energy by
unloading the hcd modules, which puts the corresponding PCI functions
into D3. How can you achieve the same thing with the drivers
built-in?