From: David Woodhouse <dwmw2@infradead.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Ni, Ray" <ray.ni@intel.com>, Laszlo Ersek <lersek@redhat.com>,
"Richardson, Brian" <brian.richardson@intel.com>,
"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: Wed, 23 Jan 2019 08:42:45 +0000 [thread overview]
Message-ID: <7014fcde58e347c88fbd60d02c71f898dffb5f8d.camel@infradead.org> (raw)
In-Reply-To: <20190123061220.f4dr2bpmp6udfyeu@sirius.home.kraxel.org>
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
On Wed, 2019-01-23 at 07:12 +0100, Gerd Hoffmann wrote:
> > A one-size-fits-all BIOS using OVMF+CSM is very much
> > preferable.
>
> Building a one-size-fits-all BIOS is pretty much impossible due to CSM
> being incompatible with secure boot.
Booting with CSM is incompatible with Secure Boot, of course.
But it doesn't prevent Secure Boot unless we actually use the CSM for
booting, surely?
I'm interested in what happened to generic CSM support. Has Intel
really ditched CSM completely from all other TianoCore builds? Nobody
else will ever be able to build a Tiano-based UEFI firmware again,
unless they also squirrel away a copy of the code before it disappears?
The code really is otherwise being deleted?
Or is this an "open source regression", with code that was in the
public repository now disappearing and only being maintained in
private?
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]
prev parent reply other threads:[~2019-01-23 8:42 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
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 [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=7014fcde58e347c88fbd60d02c71f898dffb5f8d.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