Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757883AbYFEM1X (ORCPT ); Thu, 5 Jun 2008 08:27:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757105AbYFEM0w (ORCPT ); Thu, 5 Jun 2008 08:26:52 -0400 Received: from out1.smtp.messagingengine.com ([66.111.4.25]:53780 "EHLO out1.smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757024AbYFEM0v (ORCPT ); Thu, 5 Jun 2008 08:26:51 -0400 X-Sasl-enc: 4Q0BAsVkMs6aw5zUc/I1s4w3xmF5O0zAx63ay5VZzuPb 1212668810 Message-ID: <4847DB82.60408@ladisch.de> Date: Thu, 05 Jun 2008 14:26:42 +0200 From: Clemens Ladisch User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: David Woodhouse CC: linux-kernel@vger.kernel.org Subject: Re: [PATCH 10/18] ihex.h: binary representation of ihex records References: <20080605.foo@pmac.infradead.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 695 Lines: 17 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. Regards, Clemens -- 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/