From: David Woodhouse <dwmw2@infradead.org>
To: "Ni, Ray" <ray.ni@intel.com>, Laszlo Ersek <lersek@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
"Richardson, Brian" <brian.richardson@intel.com>
Cc: "Justen, Jordan L" <jordan.l.justen@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Kevin O'Connor <kevin@koconnor.net>,
Anthony Perard <anthony.perard@citrix.com>
Subject: Re: Drop CSM support in OvmfPkg?
Date: Thu, 24 Jan 2019 09:31:18 +0000 [thread overview]
Message-ID: <73ed780d136faa94f5e01b58762250e009b794f9.camel@infradead.org> (raw)
In-Reply-To: <734D49CCEBEEF84792F5B80ED585239D5BFD28AE@SHSMSX103.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
On Thu, 2019-01-24 at 01:48 +0000, Ni, Ray wrote:
> David,
> I think we got an agreement here to move CSM components in OvmfPkg.
> I prefer we firstly clone the required CSM components in OvmfPkg right no.
> Finally I can remove the IntelFrameworkModulePkg/IntelFrameworkPkg in one patch.
> (I say "finally" because OVMF CSM dependency is not the only case that prevent removing
> the two framework packages.)
>
> Would you like to do the clone? Or if you are busy, I can do that.
I keep asking this question, I don't believe I've seen an
answer. Apologies if I've missed it.
Is this code genuinely not going to continue to exist anywhere else in
the Intel ecosystem, any more?
No TianoCore-based images from this point forth are ever going to even
have the option of supporting CSM?
Unless some third party also chooses to fork the CSM support code and
keep it on for themselves?
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2019-01-24 9:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 2:23 Drop CSM support in OvmfPkg? Ni, Ruiyu
2018-12-17 9:54 ` Laszlo Ersek
2018-12-17 10:44 ` Ni, Ruiyu
2018-12-20 6:44 ` Gerd Hoffmann
2018-12-20 13:37 ` David Woodhouse
2018-12-20 14:55 ` Ni, Ruiyu
2019-01-22 16:13 ` Ni, Ray
2019-01-22 16:23 ` David Woodhouse
2019-01-23 3:43 ` Ni, Ray
2019-01-23 4:00 ` Andrew Fish
2019-01-23 4:29 ` Ni, Ray
2019-01-23 9:46 ` Laszlo Ersek
2019-01-23 9:49 ` David Woodhouse
2019-01-24 1:48 ` Ni, Ray
2019-01-24 9:31 ` David Woodhouse [this message]
2019-01-24 11:30 ` Laszlo Ersek
2019-01-25 20:28 ` Brian J. Johnson
2019-01-28 8:23 ` Laszlo Ersek
2019-01-23 12:26 ` Ard Biesheuvel
2019-01-23 6:12 ` Gerd Hoffmann
2019-01-23 8:42 ` David Woodhouse
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=73ed780d136faa94f5e01b58762250e009b794f9.camel@infradead.org \
--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