public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>,
	devel@edk2.groups.io, jljusten@gmail.com, afish@apple.com,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: Ray Ni <ray.ni@intel.com>
Subject: Re: [edk2-devel] [PATCH 1/2] LegacyBios: set NumberBbsEntries to the size of BbsTable
Date: Tue, 25 Jun 2019 00:22:03 +0200	[thread overview]
Message-ID: <d995fbda-565d-c8e7-efc5-70c342f0a0ee@redhat.com> (raw)
In-Reply-To: <2d61fce0-b8b7-9cad-13ec-31ebd9682d86@redhat.com>

On 06/25/19 00:08, Laszlo Ersek wrote:
> On 06/21/19 12:59, David Woodhouse wrote:

>> Adding a generic way for block devices to report a human-readable
>> description in order to kill off all the device-type-specific functions
>> in BmBootDescription.c presumably *would* involve actually coordinating
>> with UEFI Specifications first?
>>
>> But we could consider that a second step. If I make the LegacyBm code
>> just call the existing (but renamed) EfiBootManagerGetBootDescription()
>> then all the horrid special cases and the specification work that's
>> required to fix them are purely an implementation detail in
>> EfiBootManagerLib? 
> 
> I think exposing EfiBootManagerGetBootDescription() as a public
> function, as-is, is a no-brainer, if platforms need it.
> 
> *Changing* EfiBootManagerGetBootDescription() is hairier.
> UefiBootManagerLib strives for strict spec compliance (and minimalism),
> if I remember correctly. However, I'm not a big fan of that approach
> myself, and recently, "extend first, standardize second" has seemed more
> accepted/tolerated than before. (I'm an active proponent of this latter
> approach.)
> 
> A new hook into PlatformBootManagerLib might help, either way. Please
> see TianoCore#982, and commit range cef7ecf6cdb4..1010873becc5.
> 
> So, please ask Ray (CC'd) :)

Wait, we already have EfiBootManagerRegisterBootDescriptionHandler().
Could that help?

Thanks,
Laszlo

  reply	other threads:[~2019-06-24 22:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1359122038.24865.19.camel@shinybook.infradead.org>
     [not found] ` <1359147866-15605-3-git-send-email-lersek@redhat.com>
2019-06-18  9:13   ` [PATCH 2/2] LegacyBbs: add boot entries for virtio-blk devices David Woodhouse
2019-06-19 12:44     ` [PATCH 1/2] LegacyBios: set NumberBbsEntries to the size of BbsTable David Woodhouse
2019-06-20 16:12       ` [edk2-devel] " Laszlo Ersek
2019-06-20 17:32         ` David Woodhouse
2019-06-20 20:35           ` Laszlo Ersek
2019-06-21 10:59             ` David Woodhouse
2019-06-24 22:08               ` Laszlo Ersek
2019-06-24 22:22                 ` Laszlo Ersek [this message]
     [not found]                   ` <F95F0A95-4638-4B08-BDAF-53A797A6B877@infradead.org>
2019-06-25  7:06                     ` Ni, Ray
2019-06-25 10:34                       ` Laszlo Ersek
2019-06-25  7:29                 ` David Woodhouse
2019-06-24 11:48             ` David Woodhouse
2019-06-24 21:49               ` Laszlo Ersek
2019-06-19 12:44     ` [PATCH 2/2] LegacyBbs: Add boot entries for VirtIO and NVME devices 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=d995fbda-565d-c8e7-efc5-70c342f0a0ee@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