public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ni, Ruiyu" <ruiyu.ni@intel.com>
To: "Justen, Jordan L" <jordan.l.justen@intel.com>,
	"lersek@redhat.com" <lersek@redhat.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	"Anthony Perard" <anthony.perard@citrix.com>,
	Julien Grall <julien.grall@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Drop CSM support in OvmfPkg?
Date: Mon, 17 Dec 2018 02:23:44 +0000	[thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5BF6035C@SHSMSX104.ccr.corp.intel.com> (raw)

Hi OvmfPkg maintainers and reviewers,
I am working on removing IntelFrameworkModulePkg and IntelFrameworkPkg. The biggest dependency now I see is the CSM components that OVMF depends on.
So I'd like to know your opinion about how to handle this. I see two options here:

  1.  Drop CSM support in OvmfPkg.
  2.  Create a OvmfPkg/Csm folder to duplicate all CSM components there.

What's your opinion about this?

Thanks/Ray



             reply	other threads:[~2018-12-17  2:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17  2:23 Ni, Ruiyu [this message]
2018-12-17  9:54 ` Drop CSM support in OvmfPkg? 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
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=734D49CCEBEEF84792F5B80ED585239D5BF6035C@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