On Fri, 2008-05-23 at 18:53 +0200, Rene Herman wrote:
quoted text
> On 23-05-08 18:44, Sam Ravnborg wrote:
> 
> > On Fri, May 23, 2008 at 12:38:41PM -0400, Lennart Sorensen wrote:
> >> On Fri, May 23, 2008 at 06:21:01PM +0200, Sam Ravnborg wrote:
> >>> Looks good.
> >>> But do we need the firmware after init?
> >>> In other owrds could it be inside a discard after init block?
> >> What is you can hotplug the device and hence need to initialize the same
> >> device type multiple times?  Wouldn't keeping the firmware around be
> >> useful then?  How about on suspend/resume, do you need to reload
> >> firmware in those cases?
> > 
> > There are cases where we need it after init.
> > But if there are cases where we do not need it after init maybe
> > we should be able to save some memory there?
> > 
> > Let us get it working as is - then we can add such features later.
> 
> If embedded is the main consumer I would consider this a fairly vital 
> feature though.

Remember, for now this is mostly just replacing the cases where the
firmware used to be unconditionally present in the kernel. If you really
want to avoid taking kernel memory, put it in userspace.

-- 
dwmw2

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/