Re: [RFC] firmware load: defer request_firmware during early boot and resume
From: Francois Romieu
Date: Sat Jul 21 2012 - 17:14:30 EST
Ming Lei <tom.leiming@xxxxxxxxx> :
> On Sun, Jul 22, 2012 at 1:31 AM, Linus Torvalds
> <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
> > On Fri, Jul 20, 2012 at 5:33 AM, Ming Lei <tom.leiming@xxxxxxxxx> wrote:
> >> The RFC patch is just for discussing if the idea of deferring
> >> request_firmware is doable for addressing the issue of
> >> request_firmware in resume path, which is caused by driver
> >> unbind/rebind during resume.
> > NAK.
> Suppose it is not good for resume case, I think it still makes sense
> for early boot
> situation, at least the patch will support to request firmware inside
> init call, and
> allow drivers to be built in kernel in case of requesting firmware from probe().
Could there be a simple, static and inefficient way to link firmware
and code together ?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/