From: "Brian J. Johnson" <brian.johnson@hpe.com>
To: <devel@edk2.groups.io>, <jbrasen@nvidia.com>
Subject: Re: [edk2-devel] HII Keyword utility
Date: Wed, 15 May 2024 12:13:46 -0500 [thread overview]
Message-ID: <db985546-2a52-4e7b-8473-228c51a4d430@hpe.com> (raw)
In-Reply-To: <63hO.1715617660260636459.KN8z@groups.io>
[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]
I like the idea; it sounds useful for automation. Although more and
more of that is moving to Redfish now. No idea where it should go, though.
*Brian J. Johnson
*Enterprise X86 Lab
Hewlett Packard Enterprise
------------------------------------------------------------------------
*From:* Jeff Brasen via groups.io [mailto:jbrasen=nvidia.com@groups.io]
*Sent:* Monday, May 13, 2024 at 11:27 AM
*To:* devel@edk2.groups.io
*Subject:* [edk2-devel] HII Keyword utility
> I have a UEFI shell application that can set/get UEFI x-UEFI HII
> Keyword values. edk2-nvidia/Silicon/NVIDIA/Application/HiiKeywordUtil
> at main · NVIDIA/edk2-nvidia (github.com)
> <https://github.com/NVIDIA/edk2-nvidia/tree/main/Silicon/NVIDIA/Application/HiiKeywordUtil>
>
> I have used this to configure iSCSI from the shell. Is this something
> that is desired to be in the main edk2 repo? If so, what package
> should this go under?
>
> If this is generally useful I'll do some cleanup and make a push
> request after the stable202405 release is out.
>
> -Jeff Brasen
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#118928): https://edk2.groups.io/g/devel/message/118928
Mute This Topic: https://groups.io/mt/106076569/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 3949 bytes --]
prev parent reply other threads:[~2024-05-15 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 16:27 [edk2-devel] HII Keyword utility Jeff Brasen via groups.io
2024-05-15 17:13 ` Brian J. Johnson [this message]
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-list 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=db985546-2a52-4e7b-8473-228c51a4d430@hpe.com \
--to=devel@edk2.groups.io \
/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