built-in USB drivers

Dan Williams dcbw at redhat.com
Tue Feb 10 20:51:09 UTC 2009


On Tue, 2009-02-10 at 21:43 +0100, Philippe Carriere wrote:
> > 
> > > -------- Message transféré --------
> > > De: Dan Williams <dcbw at redhat.com>
> > > Reply-to: Development discussions related to Fedora
> > > <fedora-devel-list at redhat.com>
> > > À: Development discussions related to Fedora
> > > <fedora-devel-list at redhat.com>
> > > Sujet: Re: built-in USB drivers
> > > Date: Mon, 09 Feb 2009 10:43:56 -0500
> > > 
> > > On Sun, 2009-02-08 at 16:06 +0100, Philippe Carriere wrote:
> > > > Hi,
> > > > 
> > > > since Fedora 10, USB drivers (more precisely, ehci-hcd for which a
> > > > patch is required to be snd-ubs-us112l - alsa-1.0.18 - compatible) are
> > > > "built-in" in the official kernel package.
> > > > For previous releases (F9), USB drivers always were modules, with the
> > > > advantage that providing a patched module (using kmod rpmfusion
> > > > framework) just required, after installing the kmod rpms, to
> > > > disable/enable the module.
> > > > 
> > > > I do not know the motivation of Fedora developers for choosing
> > > > built-in rather than module in the pre-compilation configuration: is
> > > > it indeed unavoidable ? Or does it exist a fairly simple way (I found
> > > > nothing like this in documentations) to disable a built-in driver so
> > > > as to replace it by a module, avoiding lengthy kernel compilation for
> > > > just a few modified lines ?
> > > 
> > > Building modules in speeds up boot times.  Obviously you only want to
> > > build in modules that almost all of the machines of a certain
> > > architecture are likely to need.  The USB host controller drivers are
> > > probably the best candidate for this.
> 
> I'm probably a too old man to understand that (a few seconds of boot)
> time saving is preferable than (keeping some degrees of) freedom.
> Anyway, almost all is not all and undoubtfully not all hardware-to-be.
> 
> > > 
> > > My suggestion would be to encourage the upstream ALSA maintainers to
> > > accept the patch necessary for your hardware, and then that patch will
> > > find its way into the Fedora kernel when the ALSA folks push updates to
> > > Linus.
> > > 
> > > Dan
> > > 
> 
> Well, ehci-hcd is not Alsa maintainers dependent and as can be seen in the attached emails, we do our best effort for having the patch 

Ah right, not the sound module, but ehci-hcd needs the patch, so you're
correct.

Dan





More information about the fedora-devel-list mailing list