On Tue, Jun 24, 2014 at 2:58 PM, Francois Romieu wrote:
> Thanks for the pointers.
>
> I can't help thinking that there's a bit of sensationalism in the
> timeout * num CPUs argument though. :o)
Indeed, this actually only applies to microcode which will end up
using the API for each CPU it seems.
Luis R. Rodriguez :
> On Sat, Jun 21, 2014 at 12:52:05PM +0200, Francois Romieu wrote:
> > Luis R. Rodriguez :
[...]
> Note that in the worst case if udev is present in the worst case if the
> firmware is not present loading can take up to timeout * num CPUs [0],
> but work is underway to try to
On Sat, Jun 21, 2014 at 12:52:05PM +0200, Francois Romieu wrote:
> Luis R. Rodriguez :
> > I was just porting over an ethernet driver [0] to use
> > request_firmware_nowait()
> > since firmware loading seems can take over a minute on one device, while
> > at it I noticed no other ethernet drivers
Luis R. Rodriguez :
> I was just porting over an ethernet driver [0] to use
> request_firmware_nowait()
> since firmware loading seems can take over a minute on one device, while
> at it I noticed no other ethernet drivers yet use this API so figure
> this may be a trend coming if devices are get
4 matches
Mail list logo
