All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: David Michael <fedora.dm0@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
	Vladimir Serbinenko <phcoder@gmail.com>
Subject: Re: [PATCH v4 1/2] Add support for SMBIOS3 entry point structures
Date: Sun, 20 Sep 2015 07:48:12 +0300	[thread overview]
Message-ID: <55FE3A8C.8020800@gmail.com> (raw)
In-Reply-To: <CAEvUa7mC9p+Osvkdke5htAUu_+zqYLuxka3ddWOcuUCMy=tawA@mail.gmail.com>

26.08.2015 20:01, David Michael пишет:
> On Fri, Aug 21, 2015 at 8:12 AM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
>> On Sun, Aug 16, 2015 at 5:26 AM, David Michael <fedora.dm0@gmail.com> wrote:
>>>   grub-core/commands/efi/loadbios.c    | 18 ++++++++++++++---
>>
>> I am not sure we want to touch it. From what I could gather it had
>> been used as workaround for lack of proper EFI support in Linux kernel
>> long ago and it is unlikely any system that required it would have
>> SMBIOS v3.
>>
>>>   grub-core/commands/efi/lsefisystab.c |  1 +
>>>   grub-core/efiemu/i386/pc/cfgtables.c | 38 ++++++++++++++++++++++++++----------
>>
>> More or less the same. efiemu is used for (assuming it is still used
>> by anyone) for Apple systems only, so unless Apple actually supports
>> SMBIOS v3 it is probably better to leave it.
>
> I haven't tried any recent Apple systems, but in my quest to find v3
> hardware, I looked at a MacBook Air from a generation or two ago.  It
> only supported v2.4.
>
> Do you want an updated patch, or is this usable with those files'
> changes deleted?
>

Update patch would be nice. Thank you!


      reply	other threads:[~2015-09-20  4:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-16  2:26 [PATCH v4 1/2] Add support for SMBIOS3 entry point structures David Michael
2015-08-17 19:31 ` Leif Lindholm
2015-08-26 16:51   ` David Michael
2015-08-21 12:12 ` Andrei Borzenkov
2015-08-26 17:01   ` David Michael
2015-09-20  4:48     ` Andrei Borzenkov [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-all 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=55FE3A8C.8020800@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=fedora.dm0@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=phcoder@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.