public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Isaac Oram" <isaac.w.oram@intel.com>
To: "Kirkendall, Garrett" <Garrett.Kirkendall@amd.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Chiu, Chasel" <chasel.chiu@intel.com>,
	"Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>,
	"Gao, Liming" <gaoliming@byosoft.com.cn>,
	"Dong, Eric" <eric.dong@intel.com>,
	"Bobroff, Zachary" <zacharyb@ami.com>,
	"Zimmer, Vincent" <vincent.zimmer@intel.com>
Subject: Re: MinPlatformPkg question
Date: Thu, 12 Jan 2023 21:44:11 +0000	[thread overview]
Message-ID: <SA1PR11MB5801B1DEF8007598125A3C5FD0FD9@SA1PR11MB5801.namprd11.prod.outlook.com> (raw)
In-Reply-To: <PH7PR12MB6441B86AC5AE935BC1811C3C85FD9@PH7PR12MB6441.namprd12.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 2433 bytes --]

Garrett,

Preface:  I don't have a strong objection to moving MinPlatformPkg.  I would generally prefer to move silicon/platform/board specific content out of edk2 and into edk2-platforms or elsewhere.
I am concerned that moving content could negatively impact current users in a way that would increase fragmentation though.  I that eventually someone will make a package manager and then it will all be localized and won't matter where packages come from.


I am very interested in expanding use.  We have purposefully avoided "finishing" to a 1.0 version of spec until more adoption has occurred.

I have not seen any feedback on what would be needed to expand to different architectures.  I personally have some open questions for discussion, like the approach for standardized FV layout and the use of PCD to describe them.  And refactoring the DSC/FDF include content.  QemuOpenBoardPkg work generated a better option there.

I would propose that we modify and extend the current content in a mostly backwards compatible way.  Then, once we have the changes clear, we make an incompatible MinPlatformV1Pkg or something like that in conjunction with 1.0 spec.  The benefit I would like is not punishing existing adopters and ending up with a simple/minimal package for longer term use.

Regards,
Isaac

From: Kirkendall, Garrett <Garrett.Kirkendall@amd.com>
Sent: Thursday, January 12, 2023 5:33 AM
To: devel@edk2.groups.io; Chiu, Chasel <chasel.chiu@intel.com>; Desimone, Nathaniel L <nathaniel.l.desimone@intel.com>; Oram, Isaac W <isaac.w.oram@intel.com>; Gao, Liming <gaoliming@byosoft.com.cn>; Dong, Eric <eric.dong@intel.com>
Subject: MinPlatformPkg question


[Public]

+ MinPlatformPkg Maintainers

Start the conversation:
Some time back there were posts about promoting MinPlatformPkg up to a more generic level.  Is there still a desire to implement this and possibly even to promote this more generic MinPlatformPkg to the edk2 repository.  Would it be expanded to encompass different architectures other than x86, and maybe how?


GARRETT KIRKENDALL
----------------------------------------------------------------------------------------------------------------------------------
Facebook<https://www.facebook.com/AMD> |  Twitter<https://twitter.com/AMD> |  amd.com<http://www.amd.com/>
[cid:image001.png@01D92675.025F4F10]

Words to live by: "Slow is Smooth.  Smooth is Fast."


[-- Attachment #1.2: Type: text/html, Size: 7205 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 2614 bytes --]

  reply	other threads:[~2023-01-12 21:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 13:33 MinPlatformPkg question Kirkendall, Garrett
2023-01-12 21:44 ` Isaac Oram [this message]
2023-01-31 16:54   ` Kirkendall, Garrett
2023-01-31 18:57     ` [edk2-devel] " Pedro Falcato
2023-01-31 19:28       ` Kirkendall, Garrett
2023-01-31 20:43         ` Isaac Oram
2023-02-01  1:18         ` Pedro Falcato
  -- strict thread matches above, loose matches on Subject: below --
2023-01-09 17:30 Kirkendall, Garrett
2023-01-10  3:49 ` Chang, Abner

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=SA1PR11MB5801B1DEF8007598125A3C5FD0FD9@SA1PR11MB5801.namprd11.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