From: "Liming Gao" <liming.gao@intel.com>
To: "Oram, Isaac W" <isaac.w.oram@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Kubacki, Michael A" <michael.a.kubacki@intel.com>
Subject: Re: [edk2-devel] [RFC][edk2-platform][Add new packages in Platform\Intel directory]
Date: Fri, 24 May 2019 05:22:20 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E450AC7@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <3155A53C14BABF45A364D10949B7414C970E867F@ORSMSX116.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 3080 bytes --]
Isaac:
So, how about BoardModulePkg for them?
Thanks
Liming
From: Oram, Isaac W
Sent: Thursday, May 23, 2019 1:00 AM
To: devel@edk2.groups.io; Kubacki, Michael A <michael.a.kubacki@intel.com>; Gao, Liming <liming.gao@intel.com>
Subject: RE: [edk2-devel] [RFC][edk2-platform][Add new packages in Platform\Intel directory]
I am concerned that BoardSupportPkg is misleading. My understanding is that many people are familiar with board support files, board support packages, and similar concepts explicitly using the words board and support. And in my experience, they have always had the board specific details. Our package does not, it has code supporting board specific code.
Basically, I think that this is likely to be misleading to a lot of people. And I don’t particularly understand that common, generic, and universal are common, but support is not. I don’t really have a better suggestion, not having more specific details on the content handy, all names are “common”. Maybe we need to think more about what goes in here longer term so we have more coherence and thus a more specific name is possible.
Regards,
Isaac
From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> On Behalf Of Kubacki, Michael A
Sent: Tuesday, May 21, 2019 9:17 PM
To: Gao, Liming <liming.gao@intel.com<mailto:liming.gao@intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: Re: [edk2-devel] [RFC][edk2-platform][Add new packages in Platform\Intel directory]
In that case, I’d like to move the proposed name to BoardSupportPkg.
Thanks,
Michael
From: Gao, Liming
Sent: Tuesday, May 21, 2019 9:00 PM
To: Kubacki, Michael A <michael.a.kubacki@intel.com<mailto:michael.a.kubacki@intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: RE: [edk2-devel] [RFC][edk2-platform][Add new packages in Platform\Intel directory]
Michael:
I am OK for both name. I think they have same meaning. To avoid the common word in Package name, such as Generic or Universal, BoardSupportPkg name may be better.
Thanks
Liming
From: Kubacki, Michael A [mailto:michael.a.kubacki@intel.com]
Sent: Monday, May 20, 2019 1:30 PM
To: Gao; Gao, Liming <liming.gao@intel.com<mailto:liming.gao@intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: Re: [edk2-devel] [RFC][edk2-platform][Add new packages in Platform\Intel directory]
Hi Liming,
I agree with the need for both packages. We should wait at least another day for any additional feedback on the package name GenericBoardPkg. That name may give the impression the package can generically be used on various boards whereas the intent here is a package containing common or supporting board functionality. An alternative name to consider is BoardSupportPkg.
As a reminder, ensure the separation of content follows 8.1 (or update the document if necessary):
https://edk2-docs.gitbooks.io/edk-ii-minimum-platform-specification/8_stage_6_advanced_feature_selection/
Thanks,
Michael
[-- Attachment #2: Type: text/html, Size: 11491 bytes --]
next prev parent reply other threads:[~2019-05-24 5:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 13:28 [RFC][edk2-platform][Add new packages in Platform\Intel directory] Liming Gao
2019-05-20 5:29 ` [edk2-devel] " Kubacki, Michael A
2019-05-22 4:00 ` Liming Gao
2019-05-22 4:16 ` Kubacki, Michael A
2019-05-22 16:59 ` Oram, Isaac W
2019-05-24 5:22 ` Liming Gao [this message]
2019-05-24 16:31 ` Oram, Isaac W
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=4A89E2EF3DFEDB4C8BFDE51014F606A14E450AC7@SHSMSX104.ccr.corp.intel.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