public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Marcin Wojtas <mw@semihalf.com>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	nadavh@marvell.com, "jsd@semihalf.com" <jsd@semihalf.com>,
	Grzegorz Jaszczyk <jaz@semihalf.com>,
	Kostya Porotchkin <kostap@marvell.com>
Subject: Re: [platforms: PATCH v2 1/4] Marvell/Armada7k8k: Shift PEI stack base
Date: Tue, 22 Jan 2019 21:09:37 +0000	[thread overview]
Message-ID: <20190122210937.rf44pvv6gaudlme7@bivouac.eciton.net> (raw)
In-Reply-To: <CAPv3WKchQx8OB0oec25z7XUA8iyVmvJW5gpf9D1LWeySiXrxGg@mail.gmail.com>

On Tue, Jan 22, 2019 at 09:56:14PM +0100, Marcin Wojtas wrote:
> > > > I think I gave my suggestion for the resolution of this problem (with
> > > > moving StackBase to 0x05400000 as the alternative) in my previous
> > > > reply.
> > > >
> > >
> > > Yes, and I answered, presenting the alternative memory map with
> > > additional 64kB "cut out" on top of 20MB "hole" of memory, which I'm
> > > not fancy, given available space inside the 20MB chunk.
> >
> > Please go back and reread my first and my second email.
> > Then please point out where I have, other than as an alternative
> > solution, suggested growing the cutout size.
> >
> > Then perhaps we can rewind this conversation and try again?
> 
> Ok. So would it be sufficient to replace
> gMarvellTokenSpaceGuid.PcdSecureRegionBase with two sets of separate
> PCDs for ARM-TF runtime services and OPTEE leaving the PEI stack base
> @0x43f0000?

That would be lovely, thank you :)

(Although your reference to wanting to keep the PEI stack area out of
the hands of the operating system might mean that you want three? I'll
leave that to your discretion.)

Best Regards,

Leif


  reply	other threads:[~2019-01-22 21:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22  1:32 [platforms: PATCH v2 0/4] Armada7k8k memory handling update Marcin Wojtas
2019-01-22  1:32 ` [platforms: PATCH v2 1/4] Marvell/Armada7k8k: Shift PEI stack base Marcin Wojtas
2019-01-22 17:26   ` Leif Lindholm
2019-01-22 18:26     ` Marcin Wojtas
2019-01-22 19:06       ` Leif Lindholm
2019-01-22 19:27         ` Marcin Wojtas
2019-01-22 20:26           ` Leif Lindholm
2019-01-22 20:56             ` Marcin Wojtas
2019-01-22 21:09               ` Leif Lindholm [this message]
2019-01-23  8:28                 ` Marcin Wojtas
2019-01-23  9:42                   ` Leif Lindholm
2019-01-23  9:45                     ` Marcin Wojtas
2019-01-22  1:32 ` [platforms: PATCH v2 2/4] Marvell/Library: Introduce common header for the SMC ID's Marcin Wojtas
2019-01-22 17:35   ` Leif Lindholm
2019-01-22 18:15     ` Marcin Wojtas
2019-01-22  1:32 ` [platforms: PATCH v2 3/4] Marvell/Library: ArmadaSoCDescLib: Add North Bridge description Marcin Wojtas
2019-01-22 17:38   ` Leif Lindholm
2019-01-22  1:32 ` [platforms: PATCH v2 4/4] Marvell/Armada7k8k: Read DRAM settings from ARM-TF Marcin Wojtas
2019-01-22 17:39   ` Leif Lindholm

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-list 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=20190122210937.rf44pvv6gaudlme7@bivouac.eciton.net \
    --to=devel@edk2.groups.io \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox