Op 7 aug. 2012, om 18:14 heeft Darren Hart <dvh...@linux.intel.com> het volgende geschreven:
> > > On 08/06/2012 11:21 AM, Phil Blundell wrote: >> On Mon, 2012-08-06 at 11:10 -0700, Darren Hart wrote: >>> On 08/05/2012 08:54 AM, Javier Martinez Canillas wrote: >>>> It is considered good practice to use the build system provided >>>> variables instead of directly specify hardcoded paths. >>> >>> The firmware location is explicitly set because this is where the Linux >>> kernel requires it to be. >> >> Is that actually true? I thought the kernel just supplied the leafname >> that it wanted and the knowledge about what directory to search was >> encoded in the hotplug helper scripts. > > I was sure it was true at the time, but trying to get a reference from > the source suggests I was mistaken. According to > Documentation/firmware_class/README, the hotplug script is responsible > for locating the firmware by basename and catting it to a sysfs file for > the kernel to then read. That hasn't been the case for a long, long time. CONFIG_HOTPLUG should be "", the kernel can load it on its own now. Any reference to 'hotplug' as something executable is very outdated. regards, Koen _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
