From: Prarit Bhargava <prarit@redhat.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Raghuraman Thirumalairajan <rthirumal@juniper.net>,
David Michael <fedora.dm0@gmail.com>,
Andrei Borzenkov <arvidjaar@gmail.com>,
Rajat Jain <rajatjain@juniper.net>,
Sanjay Jain <sanjayj@juniper.net>,
Stu Grossman <grossman@juniper.net>
Subject: Re: [PATCH] Add a module for retrieving SMBIOS information
Date: Tue, 03 Feb 2015 10:04:48 -0500 [thread overview]
Message-ID: <54D0E390.9060208@redhat.com> (raw)
In-Reply-To: <54CFCF5E.6040606@redhat.com>
On 02/02/2015 02:26 PM, Prarit Bhargava wrote:
>
>
> On 02/02/2015 12:09 PM, David Michael wrote:
>> On Mon, Feb 2, 2015 at 6:20 AM, Prarit Bhargava <prarit@redhat.com> wrote:
>>> On 02/01/2015 09:05 PM, David Michael wrote:
>>>> * grub-core/commands/i386/smbios.c: New file.
>>>> * grub-core/Makefile.core.def (smbios): New module.
>>>> * docs/grub.texi (smbios): New node.
>>>> (Command-line and menu entry commands): Add a menu entry for smbios.
>>>> ---
>>>>
>>>> Hi,
>>>>
>>>> There was some interest on help-grub about supporting SMBIOS access
>>>> upstream.
>>>
>>> OOC, why? Why would you need to do this? I'm certainly not against doing this
>>> but just wondering exactly why you want to do this.
>>
>> The thread on grub-help asked about booting particular kernel versions
>> off a hot-pluggable drive based on the detected hardware, which this
>> would allow.
>>
>> I originally wrote it to change what options are available based on
>> whether a disk is being booted physically or virtually. Since QEMU
>> makes it easy to add SMBIOS entries on the command line, I've also
>> been using it for random tweaks like showing a vga_text boot menu
>> instead of gfxterm when running QEMU with "-display curses".
>>
>
> Ah interesting David -- and good job on getting the efi.smbios stuff in there
> too as that's an easy thing to miss. I'll take a closer look ...
>
FWIW, I think it looks fine and it definitely has a valid use case. I'd suggest
that you update the description with Rajat's comment.
One odd thing in the patch (and it may be something weird on my end that I've
never seen before). When I saved and applied your patch via 'git am', the patch
contained a few "^L" lines. For example
^L
/* Reference: DMTF Standard DSP0134 2.7.1 Section 6.1.3 */
Not sure why that happened, but I do see them in the patch as well as the email
you sent to the list.
P.
next prev parent reply other threads:[~2015-02-03 15:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 2:05 [PATCH] Add a module for retrieving SMBIOS information David Michael
2015-02-02 11:20 ` Prarit Bhargava
2015-02-02 17:09 ` David Michael
2015-02-02 18:01 ` Rajat Jain
2015-02-02 19:25 ` Prarit Bhargava
2015-02-02 19:26 ` Prarit Bhargava
2015-02-03 15:04 ` Prarit Bhargava [this message]
2015-02-03 18:41 ` David Michael
2015-02-04 13:58 ` Prarit Bhargava
2015-02-02 20:06 ` Leif Lindholm
2015-02-02 22:01 ` David Michael
2015-02-02 22:48 ` Leif Lindholm
2015-02-03 18:53 ` David Michael
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=54D0E390.9060208@redhat.com \
--to=prarit@redhat.com \
--cc=arvidjaar@gmail.com \
--cc=fedora.dm0@gmail.com \
--cc=grossman@juniper.net \
--cc=grub-devel@gnu.org \
--cc=rajatjain@juniper.net \
--cc=rthirumal@juniper.net \
--cc=sanjayj@juniper.net \
/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;
as well as URLs for NNTP newsgroup(s).