Re: AIC94xx SAS question.

[Wakko Warner <wakko@animx.eu.org>]

James Bottomley wrote:
> > I can understand this from the point of the distrobution of the linux
> > kernel, but it still can be done.  If there were a patch or something that
> > would convert the file, that's all I care.  This for me would be preferred.
> 
> There is certainly a way to do this: all you really need to do is to
> render the firmware into hex as a character array, compile the array
> with the driver and return a pointer to the first byte at the
> request_firmware call.

I know I can make a .h file with the firmware in it.  I might beable to do
the other change as well, not sure yet.  I'm not a kernel hacker.

> The practical reason it's no-longer done (apart from the annoyance it
> causes debian) is simply that the file is huge and the firmware seems to
> change quite a lot.  For the qla2xxx driver (whose firmware, admittedly
> is larger than aic94xx) it used to result in a 4MB patch every time
> there was a tiny change to the file.

It would be nice if someone had a patch that would include a .h file to the
driver and the .h can be generated from whatever firmware is wanted.

If I ever decide to redesign my system, I may have a go at this.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???