public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Brian J. Johnson" <brian.johnson@hpe.com>,
	David Woodhouse <dwmw2@infradead.org>,
	"Ni, Ray" <ray.ni@intel.com>, Gerd Hoffmann <kraxel@redhat.com>,
	"Richardson, Brian" <brian.richardson@intel.com>
Cc: Anthony Perard <anthony.perard@citrix.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>
Subject: Re: Drop CSM support in OvmfPkg?
Date: Mon, 28 Jan 2019 09:23:56 +0100	[thread overview]
Message-ID: <f663651e-1836-41f9-357a-6e031497c31b@redhat.com> (raw)
In-Reply-To: <4dfb6a1f-da8f-4141-8687-be968ff261a9@hpe.com>

On 01/25/19 21:28, Brian J. Johnson wrote:
> On 1/24/19 5:30 AM, Laszlo Ersek wrote:
>> On 01/24/19 10:31, David Woodhouse wrote:
>>> 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.
>>
>> I think you haven't. And, I'm curious too. :)
>>
>> Thanks
>> Laszlo
>>
>>> 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?
>>>
> 
> In fall of 2017, Intel declared their intention to end legacy BIOS
> support on their platforms by 2020.
> 
> http://www.uefi.org/sites/default/files/resources/Brian_Richardson_Intel_Final.pdf
> 
> 
> I believe they have stuck to this story at subsequent UEFI plugfests.

Thank you! For me that answers the question.

--*--

BTW, I'm glad slides 11, 17, 18 say "Remove user motivations to stick
with BIOS: Improve experience with UEFI Secure Boot". It's incredible
how many UEFI implementations do not offer any *real* BootOrder/Boot####
management even, not to mention the obscure hacks such as forcibly
re-setting the first boot option to Windows, if it is installed etc.
It's no surprise people rely on "shim" and "grub" (and other 3rd party
boot loaders) more than ever -- they want to get out of the crappy
platform firmware UI as soon as they can, and reach a UI they can
actually control.

Thanks,
Laszlo


  reply	other threads:[~2019-01-28  8:24 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 [this message]
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=f663651e-1836-41f9-357a-6e031497c31b@redhat.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