From: "Kirkendall, Garrett" <Garrett.Kirkendall@amd.com>
To: Leif Lindholm <leif.lindholm@linaro.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Michael D Kinney <michael.d.kinney@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Laszlo Ersek <lersek@redhat.com>, Andrew Fish <afish@apple.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [RFC 0/6] Create central repository for boilerplate configuration
Date: Thu, 21 Sep 2017 13:21:59 +0000 [thread overview]
Message-ID: <CY4PR12MB1702E4F5491E714C5698075985660@CY4PR12MB1702.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20170920172755.22767-1-leif.lindholm@linaro.org>
Something I have found useful is leaving the intended file extension at the end of the file name. That way, you still know it is intended to be "!include"ed, but any editor file extensions you have set up still work on these files.
ConfigPkg/Security/Security.dsc.inc => ConfigPkg/Security/Security.inc.dsc
Since DSC can merge sections from different files, one *.inc.dsc file is sufficient with multiple sections.
For FDF files, I've found that sections cannot be merged so it might be better to indicate where pieces are intended to be included *.pei.inc.fdf and *.dxe.inc.fdf. Also, these files probably shouldn't contain section headers because you don't know what a platform might call the sections/FVs. (general statements, not critique on this RFC)
This allows people to "!include" directly and know where the pieces are intended to go. Plus it gives a quick view indication in the platform DSC and FDF files that things have been "!include"ed in the correct sections of the file.
Thanks,
GARRETT KIRKENDALL
SMTS Firmware Engineer | CTE
7171 Southwest Parkway, Austin, TX 78735 USA
AMD facebook | amd.com
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Leif Lindholm
> Sent: Wednesday, September 20, 2017 12:28 PM
> To: edk2-devel@lists.01.org
> Cc: Michael D Kinney <michael.d.kinney@intel.com>; Jordan Justen
> <jordan.l.justen@intel.com>; Laszlo Ersek <lersek@redhat.com>; Andrew Fish
> <afish@apple.com>; Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Subject: [edk2] [RFC 0/6] Create central repository for boilerplate
> configuration
>
> An awful lot of platform configuration is just repeated verbatim for every
> platform. This is my first stab at eliminating some of this redundancy.
>
> I have additional bits as work in progress, but before I sink too much
> time into it, I would like to try to gather feedback on this approach (all
> the way down to directory structure).
>
> This first round deals with basic network support and Secure Boot
> requirements.
>
> Leif Lindholm (6):
> ConfigPkg: add new package for holding common config fragments
> ArmVirtPkg: use ConfigPkg for common network items
> OvmfPkg: use ConfigPkg for common network items
> ConfigPkg: add common Security settings
> ArmVirtPkg: use ConfigPkg for common security items
> OvmfPkg: use ConfigPkg for common security items
>
> ArmVirtPkg/ArmVirt.dsc.inc | 25 ++--------
> ArmVirtPkg/ArmVirtQemu.dsc | 46 +++---------------
> ArmVirtPkg/ArmVirtQemuFvMain.fdf.inc | 24 ++--------
> ArmVirtPkg/ArmVirtQemuKernel.dsc | 46 +++---------------
> ConfigPkg/Network/Network.dsc.inc | 92
> ++++++++++++++++++++++++++++++++++++
> ConfigPkg/Network/Network.fdf.inc | 47 ++++++++++++++++++
> ConfigPkg/Security/Security.dsc.inc | 67 ++++++++++++++++++++++++++
> ConfigPkg/Security/Security.fdf.inc | 17 +++++++
> OvmfPkg/OvmfPkgIa32.dsc | 92 ++++---------------------------
> -----
> OvmfPkg/OvmfPkgIa32.fdf | 37 +--------------
> OvmfPkg/OvmfPkgIa32X64.dsc | 90 ++++---------------------------
> ----
> OvmfPkg/OvmfPkgIa32X64.fdf | 37 +--------------
> OvmfPkg/OvmfPkgX64.dsc | 92 ++++---------------------------
> -----
> OvmfPkg/OvmfPkgX64.fdf | 37 +--------------
> 14 files changed, 276 insertions(+), 473 deletions(-) create mode 100644
> ConfigPkg/Network/Network.dsc.inc create mode 100644
> ConfigPkg/Network/Network.fdf.inc create mode 100644
> ConfigPkg/Security/Security.dsc.inc
> create mode 100644 ConfigPkg/Security/Security.fdf.inc
>
> --
> 2.11.0
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-09-21 13:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 17:27 [RFC 0/6] Create central repository for boilerplate configuration Leif Lindholm
2017-09-20 17:27 ` [RFC 1/6] ConfigPkg: add new package for holding common config fragments Leif Lindholm
2017-09-21 0:05 ` Ard Biesheuvel
2017-09-22 11:22 ` Laszlo Ersek
2017-09-20 17:27 ` [RFC 2/6] ArmVirtPkg: use ConfigPkg for common network items Leif Lindholm
2017-09-20 17:27 ` [RFC 3/6] OvmfPkg: " Leif Lindholm
2017-09-20 17:27 ` [RFC 4/6] ConfigPkg: add common Security settings Leif Lindholm
2017-09-20 17:27 ` [RFC 5/6] ArmVirtPkg: use ConfigPkg for common security items Leif Lindholm
2017-09-20 17:27 ` [RFC 6/6] OvmfPkg: " Leif Lindholm
2017-09-20 18:14 ` [RFC 0/6] Create central repository for boilerplate configuration Laszlo Ersek
2017-09-20 21:09 ` Leif Lindholm
2017-09-22 11:20 ` Laszlo Ersek
2017-09-23 16:58 ` Leif Lindholm
2017-09-25 5:27 ` Gao, Liming
2017-09-21 12:47 ` Yao, Jiewen
2017-09-21 13:21 ` Kirkendall, Garrett [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=CY4PR12MB1702E4F5491E714C5698075985660@CY4PR12MB1702.namprd12.prod.outlook.com \
--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