All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Narendra.K@dell.com>
To: <linux-efi@vger.kernel.org>, <ard.biesheuvel@linaro.org>,
	<pjones@redhat.com>
Cc: <Stuart.Hayes@dell.com>
Subject: Re: [PATCH v0] Export Runtime Configuration Interface table to sysfs
Date: Sat, 29 Jun 2019 11:42:15 +0000	[thread overview]
Message-ID: <20190629114158.GA2565@localhost.localdomain> (raw)
In-Reply-To: <20190629112326.GA2366@localhost.localdomain>

On Sat, Jun 29, 2019 at 07:23:26AM -0400, Narendra K wrote:
> From: Narendra K <Narendra.K@dell.com>
> 
> System firmware advertises the address of the 'Runtime
> Configuration Interface table version 2 (RCI2)' via
> an EFI Configuration Table entry. This code retrieves the RCI2
> table from the address and exports it to sysfs as a binary
> attribute 'rci2' under /sys/firmware/efi/tables directory.
> The approach adopted is similar to the attribute 'DMI' under
> /sys/firmware/dmi/tables.
> 
> RCI2 table contains BIOS HII in XML format and is used to populate
> BIOS setup page in Dell EMC OpenManage Server Administrator tool.
> The BIOS setup page contains BIOS tokens which can be configured.
> 
> Signed-off-by: Narendra K <Narendra.K@dell.com>
> ---

Hi, apologies. I missed mentioning that the patch is created on the
'next' branch of efi tree.

> RFC -> v0:
> 
> - Removed rci2 table from struct efi and defined it in rci2_table.c similar to
> the way uv_systab_phys is define in dmesg.

Correcting the mistake above. It is defined similar to the way uv_systab_phys is
defined in arch/x86/platform/uv/bios_uv.c .

> - Removed the oem_tables array and added rci2 to common_tables array
> - Removed the string 'rci2' from the common_tables array so that it is 
> not printed in dmesg.
> - Merged function 'efi_rci2_table_init' into 'efi_rci2_sysfs_init' function to
> avoid calling early_memremap/unmap functions.
> 
> Also, a note unrelated to this patch - compilation error is observed when
> testing with make defconfig related to uv_systab_phys in
> arch/x86/platform/efi/efi.c. It seems like it needs to be protected with
> CONFIG_X86_UV in efi_tables array.
[...]
-- 
With regards,
Narendra K

  reply	other threads:[~2019-06-29 11:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-29 11:23 [PATCH v0] Export Runtime Configuration Interface table to sysfs Narendra.K
2019-06-29 11:42 ` Narendra.K [this message]
2019-07-02 19:57 ` Ard Biesheuvel
2019-07-08 12:26   ` Narendra.K

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=20190629114158.GA2565@localhost.localdomain \
    --to=narendra.k@dell.com \
    --cc=Stuart.Hayes@dell.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=pjones@redhat.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.