Re: request_firmware() hotplug interface, third round.

[Manuel Estrada Sainz]

On Sat, May 17, 2003 at 03:21:29PM +0200, Ingo Oeser wrote:
> On Fri, May 16, 2003 at 03:36:24PM -0700, Greg KH wrote:
> > Other than those very minor tweaks, I like this interface, it's looking
> > very good.  I wouldn't worry about any "checksum" calcuation crud, it's
> > up to the userspace tool dumping the firmware to the kernel to make sure
> 
> Ok, if that is true, then we could also have this tool enforce a
> size. Otherwise we are reading and reading without ever ending
> and allocating a lot of kernel resources while we are at it.

 A privileged script will be able to kill the system anyway it wants, I
 don't think that this is needed.

 However, forcing an standard header on firmware images including the
 size would allow size checks without the need for an specialized tool.

 Or to prevent memory reallocation every PAGE_SIZE bytes, a tentative
 size could be written to 'loading' so its meaning would become:

 loading > 1:
 	Start/restart a load of the specified size.
 loading = 1:
 	Start/restart a load of unknown size.
 loading = 0:
 	Finish load.
 loading = -1:
 	Cancel load.
 	
 
> If we know the size, then we also now start and end. So the
> "loading" attribute can certainly go.
 
 I personally like to have explicit start/end, which also allows
 cancellation and restart of the firmware load.

 Regards

 	Manuel
-- 
--- Manuel Estrada Sainz <[e-mail]>
                         <[e-mail]>
			 <[e-mail]>
------------------------ <[e-mail]> -------------------
Let us have the serenity to accept the things we cannot change, courage to
change the things we can, and wisdom to know the difference.