On Fri, Jul 13, 2007 at 05:39:38PM +0200, Jachym Holecek wrote:
> From a quick look, the kernel interface as-is cannot easily deal with
> multi-segment images. It should be extended if and only if there's
> considerable amount of devices that require it. If OTOH we're talking
> about a few isolated cases I think it's fine for them to have private
> ways of firmware loading.
>
AFAIK, this can be used for all Cypress EZ-USB chip, the TI tusb* serie ...

> If it turns out we need generic support for multi-segment firmware 
> images, I'd agree with Herb in that in-kernel S-Record parser is no 
> big deal -- it's just a couple of lines of code. I'd prefer to avoid
> Intel HEX, it's somewhat bloated (supports weird addressing modes)
> and its use tends to come with byteorder doubts associated IMO.
byte order and addressing mode should not and will not be interpreted 
by firmload(9), it's the driver's job to do this. The interface just
present a convenient way to handle data rather than re-implementing 
the wheel each time.

 - Arnaud