linux-kernel - Re: [PATCH 10/18] ihex.h: binary representation of ihex records

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 31 May 2008 23:20:51 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Clemens Ladisch <clemens@...isch.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 10/18] ihex.h: binary representation of ihex records

On Thu, 2008-06-05 at 14:26 +0200, Clemens Ladisch wrote:
> 
> David Woodhouse wrote:
> > Some devices need their firmware as a set of {address, len, data...}
> > records in some specific order rather than a simple blob.
> 
> At least in the case of EZ-USB-based devices, this is not a requirement.
> It seems most tools just do not bother to order the records in Intel hex
> files.  Any firmware that is downloaded with the EZ-USB's "load
> internal" request (0xa0) can be converted to a plain memory dump.

Hm, in that case it might be worth converting this stuff into raw
binaries. I'm not in a position to test, and wanted to keep my own
changes as unintrusive as possible though.

-- 
dwmw2

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