From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 1/2, v4] powerpc/mpc85xx: SECURE BOOT- NAND secure boot target for P3041
Date: Thu, 5 Mar 2015 11:08:03 -0600 [thread overview]
Message-ID: <1425575283.4698.132.camel@freescale.com> (raw)
In-Reply-To: <1425540416445.94572@freescale.com>
On Thu, 2015-03-05 at 01:26 -0600, Bansal Aneesh-B39320 wrote:
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Thursday, March 05, 2015 2:41 AM
> > To: Bansal Aneesh-B39320
> > Cc: u-boot at lists.denx.de; Sun York-R58495; Gupta Ruchika-R66431
> > Subject: Re: [U-Boot, 1/2, v4] powerpc/mpc85xx: SECURE BOOT- NAND
> > secure boot target for P3041
> >
> > Where does the 3.5G limitation come from? Even if the physical address
> > needs to be elsewhere due to bootrom constraints, we should be able to
> > map it wherever we want in the TLB once U-Boot takes control.
> >
> The 3.5G limitation comes from BootROM in case of secure Boot.
> Initially U-Boot has to run from CPC configured as SRAM with address
> Within 3.5G. Once U-boot has relocated to DDR, we have removed the
> Corresponding TLB entry.
Again, you could relocate the virtual address of L3 much earlier.
-Scott
next prev parent reply other threads:[~2015-03-05 17:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 8:47 [U-Boot] [PATCH 1/2][v4] powerpc/mpc85xx: SECURE BOOT- NAND secure boot target for P3041 Aneesh Bansal
2015-02-25 22:13 ` [U-Boot] [U-Boot, 1/2, v4] " Scott Wood
2015-02-27 4:35 ` aneesh.bansal at freescale.com
2015-02-27 4:51 ` Scott Wood
2015-02-27 5:50 ` aneesh.bansal at freescale.com
[not found] ` <DM2PR0301MB1312F158483C1E890256AF58F0150@DM2PR0301MB1312.namprd03.prod.outlook.com>
2015-03-04 21:10 ` Scott Wood
2015-03-05 7:26 ` aneesh.bansal at freescale.com
2015-03-05 17:08 ` Scott Wood [this message]
2015-03-10 8:50 ` aneesh.bansal at freescale.com
2015-03-10 17:03 ` Scott Wood
2015-03-10 17:52 ` aneesh.bansal at freescale.com
2015-03-10 17:59 ` Scott Wood
2015-03-10 18:27 ` aneesh.bansal at freescale.com
2015-03-10 18:33 ` Scott Wood
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=1425575283.4698.132.camel@freescale.com \
--to=scottwood@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.