From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: PATCH: added GRUB command to get and set (U)EFI firmware variables
Date: Wed, 27 Nov 2013 21:14:49 +0100 [thread overview]
Message-ID: <529652B9.8030601@gmail.com> (raw)
In-Reply-To: <20131127225752.153b1495@opensuse.site>
[-- Attachment #1: Type: text/plain, Size: 2536 bytes --]
On 27.11.2013 19:57, Andrey Borzenkov wrote:
> В Wed, 27 Nov 2013 13:44:41 -0500
> SevenBits <sevenbitstech@gmail.com> пишет:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>
>> On 11/25/2013 07:22 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>> On 25.11.2013 23:28, SevenBits wrote:
>>>>
>>>> On 11/25/2013 05:07 PM, Vladimir '?-coder/phcoder' Serbinenko
>>>> wrote:
>>>>> On 25.11.2013 23:03, SevenBits wrote:
>>>>>>
>>>>>> Thanks for your quick reply.
>>>>>>
>>>>>> I just have a couple of questions. How do you prefer I allow
>>>>>> the user to specify the vendor UUID? By typing it in via the
>>>>>> keyboard? And secondly, by saying it needs "readable aliases
>>>>>> for known types" do you mean that there should be a function
>>>>>> to set an integer, one to set a boolean, etc?
>>>>>>
>>>>> I meant for UUIDs. E.g. one alias "efi" for shared space,
>>>>> "apple" for apple and so on.
>>>> So other than a generic variable UUID and Apple, are there others
>>>> that you think might be necessary? I can try and put in some
>>>> common ones but manufacturers may not disclose what their
>>>> specific UUIDs are.
>>>>
>>> I'd include a command to list variables (interactively). We would
>>> pretty quickly collect most common UUIDs this way.
>
>> So, I've got a command written to print out the system's firmware
>> variables. Trouble is I'm not sure what the best way would be to print
>> or otherwise display the UUIDs gathered so that we can collect them.
>
>
> I think it is rather premature at this point.
Agreed. I wasn't clear enough that I meant that in the first
implementation we need to put just few UUIDs we already know about as
aliases and expand them with the time.
> What is needed first is
> sane framework for handling EFI variables, which means - handling GUID,
> options (during set or as filter in listing variables) and conversion of
> arbitrary binary data from/to external printable representation.
>
>
>>>>> But type of variable is also an issue and there should be at
>>>>> least following available: hex - transform all in hex utf16 -
>>>>> decode utf16 into utf8 Probably more, didn't really look into
>>>>> issue
>>>> I see, okay, I'll add some in.
>>>>
>
>
> Yes, please. Adding aliases for GUID can always come later and is not
> really that important.
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
next prev parent reply other threads:[~2013-11-27 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 21:34 PATCH: added GRUB command to get and set (U)EFI firmware variables SevenBits
2013-11-25 21:41 ` Vladimir 'phcoder' Serbinenko
2013-11-25 22:03 ` SevenBits
2013-11-25 22:07 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-25 22:28 ` SevenBits
2013-11-26 0:22 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-27 18:44 ` SevenBits
2013-11-27 18:57 ` Andrey Borzenkov
2013-11-27 20:14 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-11-28 15:33 ` SevenBits
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=529652B9.8030601@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
/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.