From: Tom Rini Date: Mon, 19 Aug 2013 15:00:04 -0400 Subject: [U-Boot] [PATCH v2 0/7] The patchset fixes some issue in the generation of the imx image In-Reply-To: <52124B53.60807@denx.de> References: <1373548001-19728-1-git-send-email-sbabic@denx.de> <1376318374-3497-1-git-send-email-sbabic@denx.de> <20130819161933.GG1311@bill-the-cat> <52124B53.60807@denx.de> Message-ID: <20130819190004.GH1311@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, Aug 19, 2013 at 06:44:03PM +0200, Stefano Babic wrote: > Hi Tom, > > On 19/08/2013 18:19, Tom Rini wrote: > > On Mon, Aug 12, 2013 at 04:39:27PM +0200, Stefano Babic wrote: > > > >> (header for Freescale's i.MX processors) to allow the usage of > >> Freescale's tools to sign the u-boot image and provide a secure > >> boot. > >> > >> This has nothing to do with the Secure Boot extensions > >> implemented by Simon Glass, that can be in any case used to boot > >> later a secure image. Freescale's secure boot ensures that a > >> signed bootloader is started only if it is verified with a key > >> that is burned into the iMX fuses. Documentation about the > >> Freescale's secure process can be read from the AN4591, available > >> on the Freescale's Website. > > > > Where does Marek's patch fall in here exactly? > > Marek's patch is intended to add support for mxs based processor (mx23 > / mx28) and it is quite parallel to mine and I think Marek will > replace Freescale's own tool elftosb. But, for clarity, there's not a whole bunch of common code that could be used here, and these i.MXes are different from those i.MXes? -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: