From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4][v8] powerpc/mpc85xx: SECURE BOOT- NAND secure boot target for P3041
Date: Fri, 31 Jul 2015 08:33:10 -0700 [thread overview]
Message-ID: <55BB9536.10306@freescale.com> (raw)
In-Reply-To: <55BB9047.3070207@freescale.com>
On 07/31/2015 08:12 AM, York Sun wrote:
>
>
> On 07/31/2015 01:39 AM, Aneesh Bansal wrote:
>> Secure Boot Target is added for NAND for P3041.
>> Changes:
>> In PowerPC, the core begins execution from address 0xFFFFFFFC.
>> In case of secure boot, this default address maps to Boot ROM.
>> The Boot ROM code requires that the bootloader(U-boot) must lie
>> in 0 to 3.5G address space i.e. 0x0 - 0xDFFFFFFF.
>>
>> In case of NAND Secure Boot, CONFIG_SYS_RAMBOOT is enabled and CPC is
>> configured as SRAM. U-Boot binary will be located on SRAM configured
>> at address 0xBFF00000.
>> In the U-Boot code, TLB entries are created to map the virtual address
>> 0xFFF00000 to physical address 0xBFF00000 of CPC configured as SRAM.
>>
>> Signed-off-by: Aneesh Bansal <aneesh.bansal@freescale.com>
>> ---
>> Changes in v8:
>> New Patchset Created
>>
>
> This change log doesn't have anything. Please put meaningful log for future
> patches. You can try to use patman to ease the process.
Actually this new version doesn't change _ANYTHING_, except adding a new patch
to this set which should be separated anyway. Please do not send patches like these.
York
prev parent reply other threads:[~2015-07-31 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 8:39 [U-Boot] [PATCH 1/4][v8] powerpc/mpc85xx: SECURE BOOT- NAND secure boot target for P3041 Aneesh Bansal
2015-07-31 15:12 ` York Sun
2015-07-31 15:33 ` York Sun [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55BB9536.10306@freescale.com \
--to=yorksun@freescale.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.