From: Tom Rini Date: Thu, 31 Jan 2019 09:41:11 -0500 Subject: [U-Boot] [PATCH v3 00/22] mx6sabre: Add DM and SPL FIT support In-Reply-To: <20190131125918.ez2rmktsxswtwve7@fsr-ub1664-175> References: <1548855578-12529-1-git-send-email-abel.vesa@nxp.com> <20190130185819.GN30838@bill-the-cat> <20190131125918.ez2rmktsxswtwve7@fsr-ub1664-175> Message-ID: <20190131144111.GW30838@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 Thu, Jan 31, 2019 at 12:59:19PM +0000, Abel Vesa wrote: > On 19-01-30 13:58:19, Tom Rini wrote: > > On Wed, Jan 30, 2019 at 01:39:50PM +0000, Abel Vesa wrote: > > > > > The second version is here: > > > https://lists.denx.de/pipermail/u-boot/2019-January/356557.html > > > > > > Changes since v2: > > > * Removed the unecessary SYS_MALLOC_F_LEN from both defocnfig > > > * Fixed the copyright for all the *u-boot.dtsi files > > > > OK, but you didn't answer why you need to specify your own its file when > > the TI examples show how to have mkimage generate this for you, thanks! > > > > I might be wrong here but TI is doing this for MLO, which AFAIU, it's for > SPL. The fit_spl.its I'm adding here is actually for u-boot proper. > > SPL expects descriptions in the configurations and that can't be done > without its file, again, AFAIK. > > Please let me know what exactly am I missing here. The flag to mkimage is not about SPL but rather "create a single configurations its file on the fly". This should also be fine for the its file in patch 10/22 (of v2, don't have v3 in front of me in patchwork). -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: