From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Thompson Date: Thu, 13 Dec 2018 09:30:24 +0000 Subject: [U-Boot] [PATCH] qemu-arm: Add persistent environment support In-Reply-To: <20181213024358.754d360c@thinkpad> References: <1543231217-18799-1-git-send-email-sumit.garg@linaro.org> <20181212014255.GK21466@linaro.org> <20181213024358.754d360c@thinkpad> Message-ID: <20181213093024.aqqy7xz5on7po4tb@holly.lan> 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, Dec 13, 2018 at 02:43:58AM +0200, Tuomas Tynkkynen wrote: > > Another use case is atf + u-boot (although I don't know people are > > interested in it). Put bl1.bin in flash0(0x0-0x4000000) and put > > fip.bin in flash1(0x4000000-0x8000000). Please note that, with > > secure=on, flash0 is in secure and flash1 is in non-secure. > > While I admit that your patch is workable, my point is that there are > > different use cases and it may not be a good idea to put one > > configuration in qemu-arm.h. > > Can EDK2 in QEMU boot with ATF and if so, how does it lay out things? > > Would it be possible to build U-Boot in such a way that u-boot.bin > could be substituted in existing build scripts or instructions in place > of the EDK2 binary so that things still work the same? > > Or in other words, if EDK2 has already has a working > implementation of something (such as the flash layout), IMO we should > prefer to use that instead of reimplementing it in a different > way. The EDK2 binaries I am using don't include ATF. IIRC qemu with default arguments boots directly into EL1 so most of the off-the-shelf binaries will not include a trusted firmware. EDK2 keeps its varstore on the second pflash. Daniel.