All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH v3] Add a module for retrieving SMBIOS information
Date: Fri, 27 Mar 2015 16:22:23 +0300	[thread overview]
Message-ID: <20150327162223.38111e73@opensuse.site> (raw)
In-Reply-To: <5515541A.2020808@gmail.com>

В Fri, 27 Mar 2015 13:59:06 +0100
Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> пишет:

> Could we avoid exposing such details as offset in structures? It's way 
> too technical perhaps something like
> smbios [--handle=HANDLE|--instance=N] [--set VAR] [TABLE.VARNAME]
> where table and varname will be string identifiers and would be 
> translated using dictionaries. TABLE.VARNAME as whole string can be the 
> key, that format is just to avoid conflicts when similar fields are 
> exported in different tables. You can just put the vars you care about 
> in the dictionary.

Do you mean something like "BIOS Information.BIOS Characteristics
Extension Bytes"? Because otherwise where these names should come from
and how users will know them? SMBIOS at the end is defined in terms of
structure offsets. I suppose that any user of this command will know
them.

Either we will limit ourselves to known names documented in grub
manual, but even then documentation will have to say "foo.bar refers to
table bar at offset XX". Not sure how is it better.


  reply	other threads:[~2015-03-27 13:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23  2:01 [PATCH v3] Add a module for retrieving SMBIOS information David Michael
2015-03-27 12:59 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-03-27 13:22   ` Andrei Borzenkov [this message]
2015-03-27 15:24 ` Andrei Borzenkov
2015-03-27 16:46   ` Rajat Jain
2015-03-30  3:18     ` David Michael
2015-03-30 17:46       ` Rajat Jain

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=20150327162223.38111e73@opensuse.site \
    --to=arvidjaar@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.