From: Leif Lindholm <leif.lindholm@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH] ArmPkg: drop ArmBds remnant Pcds from .dec
Date: Wed, 19 Dec 2018 11:53:37 +0000 [thread overview]
Message-ID: <20181219115337.pzzz2giwqtwcyxlo@bivouac.eciton.net> (raw)
In-Reply-To: <CAKv+Gu8RoEjkb2wt38YS0+OxC5YOMQiK7YmhNeGrwG5jwBu7YA@mail.gmail.com>
On Wed, Dec 19, 2018 at 11:08:48AM +0100, Ard Biesheuvel wrote:
> On Tue, 18 Dec 2018 at 19:38, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> >
> > The following Pcds
> > - gArmTokenSpaceGuid.PcdArmLinuxSpinTable
> > - gArmTokenSpaceGuid.PcdArmLinuxAtagMaxOffset
> > - gArmTokenSpaceGuid.PcdArmLinuxFdtMaxOffset
> > - gArmTokenSpaceGuid.PcdArmLinuxFdtAlignment
> > remained defined, without actual users.
> > So get rid of them.
> >
> > One reference to be deleted separately from edk2-platforms.
> >
> > Contributed-under: TianoCore Contribution Agreement 1.1
> > Signed-off-by: Leif Lindholm <leif.lindholm@linaro.org>
>
> Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Thanks!
Pushed as 5f0b035f10.
> > ---
> > ArmPkg/ArmPkg.dec | 20 --------------------
> > 1 file changed, 20 deletions(-)
> >
> > diff --git a/ArmPkg/ArmPkg.dec b/ArmPkg/ArmPkg.dec
> > index d99eb6769f..0ec5e8efd6 100644
> > --- a/ArmPkg/ArmPkg.dec
> > +++ b/ArmPkg/ArmPkg.dec
> > @@ -80,10 +80,6 @@ [PcdsFeatureFlag.common]
> > # it has been configured by the CPU DXE
> > gArmTokenSpaceGuid.PcdDebuggerExceptionSupport|FALSE|BOOLEAN|0x00000032
> >
> > - # Define if the spin-table mechanism is used by the secondary cores when booting
> > - # Linux (instead of PSCI)
> > - gArmTokenSpaceGuid.PcdArmLinuxSpinTable|FALSE|BOOLEAN|0x00000033
> > -
> > # Define if the GICv3 controller should use the GICv2 legacy
> > gArmTokenSpaceGuid.PcdArmGicV3WithV2Legacy|FALSE|BOOLEAN|0x00000042
> >
> > @@ -173,16 +169,6 @@ [PcdsFixedAtBuild.ARM]
> > # By default we do not do a transition to non-secure mode
> > gArmTokenSpaceGuid.PcdArmNonSecModeTransition|0x0|UINT32|0x0000003E
> >
> > - # The Linux ATAGs are expected to be under 0x4000 (16KB) from the beginning of the System Memory
> > - gArmTokenSpaceGuid.PcdArmLinuxAtagMaxOffset|0x4000|UINT32|0x00000020
> > -
> > - # If the fixed FDT address is not available, then it should be loaded below the kernel.
> > - # The recommendation from the Linux kernel is to have the FDT below 16KB.
> > - # (see the kernel doc: Documentation/arm/Booting)
> > - gArmTokenSpaceGuid.PcdArmLinuxFdtMaxOffset|0x4000|UINT32|0x00000023
> > - # The FDT blob must be loaded at a 64bit aligned address.
> > - gArmTokenSpaceGuid.PcdArmLinuxFdtAlignment|0x8|UINT32|0x00000026
> > -
> > # Non Secure Access Control Register
> > # - BIT15 : NSASEDIS - Disable Non-secure Advanced SIMD functionality
> > # - BIT14 : NSD32DIS - Disable Non-secure use of D16-D31
> > @@ -221,12 +207,6 @@ [PcdsFixedAtBuild.AARCH64]
> > # Other modes include using SP0 or switching to Aarch32, but these are
> > # not currently supported.
> > gArmTokenSpaceGuid.PcdArmNonSecModeTransition|0x3c9|UINT32|0x0000003E
> > - # If the fixed FDT address is not available, then it should be loaded above the kernel.
> > - # The recommendation from the AArch64 Linux kernel is to have the FDT below 512MB.
> > - # (see the kernel doc: Documentation/arm64/booting.txt)
> > - gArmTokenSpaceGuid.PcdArmLinuxFdtMaxOffset|0x20000000|UINT32|0x00000023
> > - # The FDT blob must be loaded at a 2MB aligned address.
> > - gArmTokenSpaceGuid.PcdArmLinuxFdtAlignment|0x00200000|UINT32|0x00000026
> >
> >
> > #
> > --
> > 2.11.0
> >
prev parent reply other threads:[~2018-12-19 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 18:38 [PATCH] ArmPkg: drop ArmBds remnant Pcds from .dec Leif Lindholm
2018-12-19 10:08 ` Ard Biesheuvel
2018-12-19 11:53 ` Leif Lindholm [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-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=20181219115337.pzzz2giwqtwcyxlo@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