All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Grub get and set efi variables
Date: Sun, 29 Nov 2015 12:00:07 +0300	[thread overview]
Message-ID: <565ABE97.5060109@gmail.com> (raw)
In-Reply-To: <CALrw=nF5-e62xHQq7NByUUNsPi7iv4EqYc=qUF4VCf=4NJd8nw@mail.gmail.com>

27.11.2015 17:25, Ignat Korchagin пишет:
>> I would add:
>> * hex. To print and store in hex form
>> * utf16. Decode utf16 into utf8. utf16 is a common encoding in EFI land.
> 
> hex is already part of the latest proposed patch:
>>> +    case EFI_VAR_HEX:
> 
> I'm not sure whether utf16 will be useful, as all standard UEFI
> variables now are using ASCII for string data.
> 

I agree; it can be added later if use case emerges. So far all
"interesting" cases that use UTF-16 are not limited to strings, and need
much more elaborate parsing. That is why I mentioned generic format
specifier before. But this also can be added if needed, overall syntax
seems to be flexible enough.

> On Fri, Nov 27, 2015 at 2:07 PM, Vladimir 'φ-coder/phcoder' Serbinenko
> <phcoder@gmail.com> wrote:
>> On 14.11.2015 05:03, Andrei Borzenkov wrote:
>>> 13.11.2015 22:42, Ignat Korchagin пишет:
>>>>>>> +static enum efi_var_type
>>>>>>> +parse_efi_var_type (const char *type)
>>>>>>> +{
>>>>>>> +  if (!grub_strncmp (type, "string", sizeof("string")))
>>>>>>> +    return EFI_VAR_STRING;
>>>>>>> +
>>>>>>
>>>>>>
>>>>>> I think this should be "ascii" or "utf8". "string" is too ambiguous
>>>>>> in UEFI
>>>>>> environment, it can also mean sequence of UCS-2 characters.
>>>>> I'm still not sure how exactly GRUB + UEFI interprets "raw buffers"
>>>>> when printing. Maybe, to avoid confusion, it might be better to
>>>>> completely remove this option. Basically, you do not want to interpret
>>>>> raw buffers as strings. For best compatibility "hex" mode should be
>>>>> promoted, I guess. What do you think?
>>>> Checked again the UEFI spec. For globally defined variables which are
>>>> strings they specify ASCII. So if we leave this option, ascii is the
>>>> best name.
>>>>
>>>
>>> What about
>>>
>>>   - ascii - print ASCII characters verbatim, escape non-ASCII in usual
>>> way (similar to "od -c")
>>>
>>>   - raw - simply put raw variable without any interpretation.
>>>
>> I would add:
>> * hex. To print and store in hex form
>> * utf16. Decode utf16 into utf8. utf16 is a common encoding in EFI land.
>> I would also skip on raw, at least until we have a real need for it as
>> we currently are not equiped to handle raw strings in variable contents,
>> including but not limited to \0 being considered a terminator
>>> This is better aligned with argument describing output formatting rather
>>> than attempting to "type" variable.
>>>
>>> Alternative (or in addition to) ascii - dump which prints usual pretty
>>> hex dump of content (hexdump -C). This is handy to interactively look at
>>> variable content.
>>>
>>> Or, and change name from --type to --format :)
>>>
>>> _______________________________________________
>>> Grub-devel mailing list
>>> Grub-devel@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>
>>
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> 



  reply	other threads:[~2015-11-29  9:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 19:39 Grub get and set efi variables Mat Troi
2015-11-03 20:12 ` SevenBits
2015-11-03 23:05   ` Mat Troi
2015-11-04  5:38     ` Andrei Borzenkov
2015-11-05 18:25       ` SevenBits
2015-11-06  2:00         ` Ignat Korchagin
2015-11-11 18:09           ` Andrei Borzenkov
2015-11-13 19:34             ` Ignat Korchagin
2015-11-13 19:42               ` Ignat Korchagin
2015-11-14  4:03                 ` Andrei Borzenkov
2015-11-17 11:48                   ` Ignat Korchagin
2015-11-29  8:57                     ` Andrei Borzenkov
2015-11-24 19:23                   ` Mat Troi
2015-11-24 20:48                     ` Seth Goldberg
2015-11-27 14:07                   ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-11-27 14:25                     ` Ignat Korchagin
2015-11-29  9:00                       ` Andrei Borzenkov [this message]
2015-12-02 12:53                         ` Ignat Korchagin
2015-12-02 13:00                           ` Andrei Borzenkov
2015-12-02 13:05                             ` Vladimir 'phcoder' Serbinenko
2015-12-02 14:52                               ` Ignat Korchagin
2015-12-03 16:43                                 ` Andrei Borzenkov
2015-12-03 17:19                                   ` Ignat Korchagin
2015-12-09 14:42                                     ` Ignat Korchagin
2015-12-12  8:36                                     ` Andrei Borzenkov
2015-12-14 11:08                                       ` Ignat Korchagin
2015-12-14 11:17                                         ` Ignat Korchagin
2016-01-29 16:25                                           ` Ignat Korchagin

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=565ABE97.5060109@gmail.com \
    --to=arvidjaar@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.