From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail05.groups.io (mail05.groups.io [45.79.224.7]) by spool.mail.gandi.net (Postfix) with ESMTPS id 0E8CB74003E for ; Thu, 24 Oct 2024 03:25:41 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=AJ4dmuwK63swqO8GUDS0TdposZ+qqmlWd64nEs31sFY=; c=relaxed/simple; d=groups.io; h=From:To:Subject:Thread-Topic:Thread-Index:Date:Message-ID:References:In-Reply-To:Accept-Language:msip_labels:MIME-Version:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Resent-Date:Resent-From:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Language:Content-Type; s=20240830; t=1729740341; v=1; x=1729999540; b=J2bi64JsFteXMFpmSsu5eXcHst871tszJ0u+QS5Cp6hdGPaeQXW+7ixrNEcmm7v4xzeddo7E xQf3DqWN3vc+M2QQ8UmTjbR+TPTKO+IJ3S1KsauwGIxa4XjzBpDno7psGnoRVfUH8tDpjp9GI0G jWG8nt95m3tI9SVEbzQQlOi6gn/PJ4uJULsOhE2eLIaSh3wQnSJfO9HNQzGfKT2yd4H29H+bfiI zoHSTJd+J2Jm1kjBNFnVIGxJwNiEZ4205AvXTiGzUcUy+RNI83CJn6T0Z4EWZUOO6VLmhtcCGk4 TUZuzsxf0PJ4I3hrpEhcjvA4n0tfnuihhqCDj8oh58I0A== X-Received: by 127.0.0.2 with SMTP id oN7LYY7687511xVFFzWpoCSQ; Wed, 23 Oct 2024 20:25:40 -0700 X-Received: from NAM11-BN8-obe.outbound.protection.outlook.com (NAM11-BN8-obe.outbound.protection.outlook.com [40.107.236.57]) by mx.groups.io with SMTP id smtpd.web11.6307.1729740339635326587 for ; Wed, 23 Oct 2024 20:25:39 -0700 X-Received: from CH3PR12MB8851.namprd12.prod.outlook.com (2603:10b6:610:180::11) by DS7PR12MB6046.namprd12.prod.outlook.com (2603:10b6:8:85::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8069.28; Thu, 24 Oct 2024 03:25:32 +0000 X-Received: from CH3PR12MB8851.namprd12.prod.outlook.com ([fe80::1883:4070:cb88:b94b]) by CH3PR12MB8851.namprd12.prod.outlook.com ([fe80::1883:4070:cb88:b94b%3]) with mapi id 15.20.8048.017; Thu, 24 Oct 2024 03:25:32 +0000 From: "Nickle Wang via groups.io" To: "devel@edk2.groups.io" , "tdoedline@atto.com" , "Chang, Abner" Subject: Re: [edk2-devel] Exposing Redfish data via HII Thread-Topic: [edk2-devel] Exposing Redfish data via HII Thread-Index: AQHbJW0cvCivgGwsoku+txQD9kbcVLKVO5oV Date: Thu, 24 Oct 2024 03:25:32 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US X-Mentions: abner.chang@amd.com X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: x-ms-publictraffictype: Email x-ms-traffictypediagnostic: CH3PR12MB8851:EE_|DS7PR12MB6046:EE_ x-ms-office365-filtering-correlation-id: 95a6559a-7579-44ea-ee3c-08dcf3db845e x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam-message-info: =?iso-8859-1?Q?TxAk1sD7e8zB8141/2V4mKbTUEmQ8VWGZwoym+TPT+k8WEyGPHqf1Ocm0U?= =?iso-8859-1?Q?24NxLVYb97psRwmiPt1gcQ+DcyzImcY0sX3VbgmfCGaplzBk0STbEsgl9z?= =?iso-8859-1?Q?M/iigafRT96btkZoztb5twNR2IZf+QPaTO3cKUVM6dqbNHOXkMHUyhQxko?= =?iso-8859-1?Q?u7XavzYomrdnfA7Ng6gHhKzwXoH5rnyINCr7i7cV9qW8r1yo/5cwKnG7zu?= =?iso-8859-1?Q?bvP10eXLhgQPa+CYXjMfPa3wghvd8Yb+Mubbl3cnqusd8THKPn4UF6xwKW?= =?iso-8859-1?Q?5BzEATQwtztVSXyb5A1zA2UAX/Wl3qtg8PNGPlMjnIaZPMc7rEdxoTR+4f?= =?iso-8859-1?Q?nC3T8GN3euVa12QOddZFQVzs6BLJk2J2TID7HkNELBldzFkgUIz3D+P2xC?= =?iso-8859-1?Q?0x80uS/Jqm2Mr1YpJWDeryQ3h9xq4Vnmgz/4G3PWbPFy4wobecaWiDhVTD?= =?iso-8859-1?Q?i4wV70m7Ap/EVhcpV1vub77o67VXMfowcdl127AjGcOPYrLrg0kgzDdtuE?= =?iso-8859-1?Q?rTmwKc5c9weINWWIVji2LaNc87Mu9AC2BOxJNPioYMOrTHMWMeUwP5wpos?= =?iso-8859-1?Q?iXzTQco3xs9kHxmWt8Zx6FIx0qKX4NZhQxyRen1UDzATqCX3Z15eQeCv4r?= =?iso-8859-1?Q?mBO+5dWH0U2vwf/vyX8aIDONGs5x2XqTC/3H/5JEp2CxJFlZbRcqS/wHSY?= =?iso-8859-1?Q?/L8nlM0bKAlpb6gyFnkgIx/h1GJYIWMU6folBHfHgu0sPavdc9ODSts03I?= =?iso-8859-1?Q?OFxRgQkwH07mFLtYA3KHMzi5ftVDnryCRPSPe65p4goi1cINH3F1eMVfkX?= =?iso-8859-1?Q?1GstrqNE9eQAH+7SIFiBk1d3lPM72l2g8QuNyICb4rZO+I3+2sd1xzlyk+?= =?iso-8859-1?Q?Ww5290wF0FghAJaof67dVKcL99QwwDw+AzQJhPEWGPWkEK+NYREfL4hfLP?= =?iso-8859-1?Q?lgqrkXP1kKmG4tSjjy+PWNysqz4IvciGoqc2fAdPWYDxClLul/DB+NEi40?= =?iso-8859-1?Q?AN1ZpIj5Ds0/Vrv6DDI1WHR0tFXmCfMXXXWaeK2p0ZUbL6nvkLW/ma20tP?= =?iso-8859-1?Q?04JeJztjxNYDxJp6M9P0vfxloiTiy3LLD3B0aMbJrI8IBQDqA9OCeDPGk4?= =?iso-8859-1?Q?esfqZ7Ji1Lgyjzo2leaWhyo4GT5sDhszXc36lmZfihMSE27k+diD0KWmIx?= =?iso-8859-1?Q?7osecP58cuiyi4vwNC8XWHVt/rnX5oP0z8iPnjrH/HNw9WxNV6N5Ehc6LW?= =?iso-8859-1?Q?nMGfHSq7OZ8Zzpq24L4+4kSMsVBYSaT+7VJld+7cy4qPx5QbI9sVejOEV8?= =?iso-8859-1?Q?apygn6TwHO8G8qrBDMjJMHyWANo6e1ACrqyyUwiv4/0xTgVh+saUB1eLRW?= =?iso-8859-1?Q?POJxYusZ8YUGl9gTfMaJ8XWgv7OJpgTg=3D=3D?= x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?iso-8859-1?Q?yaAZGmoLICUcUnrOj6Hdg53TJLXDrADmKJJttU4XMAJZZabBp31Yu7HQsd?= =?iso-8859-1?Q?qBuWA3L7tkYgHd4IBAQyAGemGqUOKknyFGHd+InAHQSBBnVReZRqb3jfDM?= =?iso-8859-1?Q?MPAYbMkrhx4r/bMxbw7z1UHSAtubJqMadAtfdIIo9yNoDx0zU2wEQtjWF+?= =?iso-8859-1?Q?HkjQK2ZDDshOTgz42Z5koz6hVAFeOc8l+nhxrcOfCxVX7KnRZ4PMQQqdxY?= =?iso-8859-1?Q?p6D5OOLPLMkJ1rPo0gnmWBxtG8l77To+iQVJ5/Vf9AcFVTQYu9Cxg+jhPe?= =?iso-8859-1?Q?0O0ivZlQVU73WcZ1/WJmhWKVxw4fNKsq+FngcWmCQetLCiBEk13vcDidkt?= =?iso-8859-1?Q?MOFqBe4JgnTwaR0/SuY5CQGkeBzSnpWgikLnUpvigfqRvAJ02+FsFPpcsO?= =?iso-8859-1?Q?0M7O+1fy8vDpgF6TtjSNGiMZWSd5r//Y/q7tAv7IgJ6YMAiwUCnP5Tl57j?= =?iso-8859-1?Q?LfBRwiIotu2ioVqYz/yi3hj297k9pEmbD/52JPQD2gaVFTu8xxrlpqZL3U?= =?iso-8859-1?Q?YJPD9RdLN7/sZyt3CdudvB+yVIV6qKVuxclG16xy74RKDN0qWK+Z1YMRKc?= =?iso-8859-1?Q?XY5RxUln9XecLstqpJIgrLT+WUFdsnNt2NOwwk5mGnlIZrOjzax3KenF2s?= =?iso-8859-1?Q?0gi5vWx+ptpmPI32rWSBEGMGtZniYEd1m2t1sWyuaMVsId4OpJjj600SyW?= =?iso-8859-1?Q?lI24TzjjFWoR7gus4CrTIt8S4KVroVSO8YS2F3hIhn4mzjSX04eo4aoTlj?= =?iso-8859-1?Q?CziS4GiYwLAOEXK7SSp3gkNNn5cok+AiJOVu1I76x//c9jFQ6XCDniW8z0?= =?iso-8859-1?Q?iYS+H2bj4xIbrJsQaj8iCsuURgcUfJ+I3fCR6MZPyVtL5PFPF/962CUD5W?= =?iso-8859-1?Q?RMpbnLpY3ClhJ49h7EtD3VPJtfiuyWABOs1nhrVHVxZ8rgSbdILVl3ARA6?= =?iso-8859-1?Q?Fjk/WsBIZMk5iBh1WgnRck1RLL+/gwjTGjypM21X33sa2+TzHHvR1ufwqs?= =?iso-8859-1?Q?7dcrfMJC2n0uyd9q+rmnc5mqpLRG2TIRhG/o+LQrA0FG3kV9GFesJSP28X?= =?iso-8859-1?Q?8LyoPoGpCHVMDPn8s2j1o7WKLvcAC66ekkmbyICDWSiR0O6mDRUZ4oixFk?= =?iso-8859-1?Q?ahpa1GUZVyD1SE070FdkRTjIw7GIReqd4LplKG14EJQdV9+qcIQHXtW7VJ?= =?iso-8859-1?Q?olsDIzvO715mJPwMgt2cwtIiBv8kJQNNefnFvzQDhaXT6Xr8YMv3VC+G/h?= =?iso-8859-1?Q?5frgT4Qlw7tMI3WGlFZXMtCNhGJm4kXPdOZVQAWKTTOnyQawVleBSNDU1u?= =?iso-8859-1?Q?ccyrKePCTPZgPxoGWETm04qYryK39u3hBc7XqbO3qWZBgO1HTQgPjIvaSs?= =?iso-8859-1?Q?pfGHVgbEuMbqkzsqaqew48yA2ww51Mxbs/aQUCTEYElHStJgpe4LdtMogm?= =?iso-8859-1?Q?8+YK4JRJSkn1wpVoRYILlu7xpa89tmfYxo0Saxw9s2ANMkjM/aVcmTkAc+?= =?iso-8859-1?Q?siOUEkEckp5LMZ7tOVXXlrh3rFzrcWyMDrRxXidnMc7DhGKAqUkcMCk6r9?= =?iso-8859-1?Q?hThtNItCNy/G06KYnueyZ0NfvEz9lFH80Iar9ST9xAXKNYdnL0lMg9omyW?= =?iso-8859-1?Q?/K9OqsIam3z2Q=3D?= MIME-Version: 1.0 X-OriginatorOrg: Nvidia.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: CH3PR12MB8851.namprd12.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 95a6559a-7579-44ea-ee3c-08dcf3db845e X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Oct 2024 03:25:32.3482 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 43083d15-7273-40c1-b7db-39efd9ccc17a X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: ZgSs8+iZ81Gd56sRXaf2wx5YIIpRdq8x9H0jTtL4w2TcWzaV75kY3VetQQ4ki9JMuT4e0Y/5o3STJg5MkUCm5g== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DS7PR12MB6046 Precedence: Bulk List-Subscribe: List-Help: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Resent-Date: Wed, 23 Oct 2024 20:25:39 -0700 Resent-From: nicklew@nvidia.com Reply-To: devel@edk2.groups.io,nicklew@nvidia.com List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: X-Gm-Message-State: qX6P6tzw0Sf9HJGtT7kfTZPyx7686176AA= Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_CH3PR12MB8851339B59B07C6FF1875D26D94E2CH3PR12MB8851namp_" X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20240830 header.b=J2bi64Js; dmarc=pass (policy=none) header.from=groups.io; spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 45.79.224.7 as permitted sender) smtp.mailfrom=bounce@groups.io --_000_CH3PR12MB8851339B59B07C6FF1875D26D94E2CH3PR12MB8851namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi tdoedline, For the UEFI Redfish design and implementation, please check below links: * Redfish foundation support: https://github.com/tianocore/edk2/tree/master/R= edfishPkg * Redfish application implementation by using RedfishPkg: https://github.com= /tianocore/edk2-redfish-client/tree/main/RedfishClientPkg And it seems to me that you are working on PCIe storage device. I would sug= gest you to check Redfish Device Enablement (RDE): https://www.dmtf.org/dsp= /DSP0218 In this way, you don't rely on UEFI BIOS to communicate with BMC. Add @Chang, Abner for this Redfish topic. Regards, Nickle ________________________________ From: devel@edk2.groups.io on behalf of tdoedline vi= a groups.io Sent: Monday, October 21, 2024 9:41 PM To: devel@edk2.groups.io Subject: [edk2-devel] Exposing Redfish data via HII External email: Use caution opening links or attachments Hi, Let me know if this isn't the correct place to post this, but I was directe= d here from the Redfish forum. I work for a hardware company that develops= storage and network HBAs. We already expose a set of HII configuration uti= lities for display and modification of settings and health data for our ada= pters in UEFI. We are looking to add some of these features and functional= ity to the system's exposed Redfish interface to allow user configuration t= hrough additional means. Specifically, we are interested in the section "B= ridging HII and Redfish" in the following presentation: uefi.org/sites/default/files/resources/13_Jason_HPE_redfish%20implementatio= n_FINAL.pdf In order understand better how this works we attempted to use the DriverSam= pleDxe in the edk2 as an example of what we should expect to see when somet= hing with a REST_STYLE flag is presented to a system. Specifically, lookin= g at examples like the x-UEFI HII options, like this one: #string STR_ONE_OF_PROMPT_X_UEFI #language en-US "x-UEFI HII Option" #language fr-FR "x-UEFI HII Option" #language x-UEFI-ns "xUefiHiiOption" #string STR_ONE_OF_PROMPT_X_UEFI_HELP #language en-US "This is an HII optio= n which has REST_STYLE flag and x-UEFI namespace UNI string associated. Thi= s HII option could be configured by either in-band edk2 setup browser or th= e remote management in out-of-band such as Redfish service. This HII option= is configured through EFI_KEYWORD_HANDLER_PROTOCOL." We built and loaded the DriverSampleDxe driver on example servers from thre= e different vendors, and while the HII forms show up correctly in the Syste= m Setup when booting the system (including these fields that are flagged as= REST_STYLE with help text saying that they should be present in Redfish), = nothing new shows up under $(IP)/redfish/v1/Systems/1/Bios. To be clear, w= hat we did was boot to a UEFI shell, load the DriverSampleDxe, exit back to= the System Setup to confirm that the HII forms are loaded successfully, th= en attempted to query the Redfish data looking for additional fields. Is the expected behavior of the sample driver? Is our issue that the infor= mation about the BIOS settings has already been queried by / pushed to the = BMC, so any changes once we boot to the shell are not reflected in the BMC?= Or are we not looking in the correct location for fields that are present= ed by an add-in driver? Or is this model not really supported for add-in d= rivers and the REST_STYLE functionality is reserved for drivers present in = the system firmware itself? Is there another example or methodology to do = what we want to do, which is to populate Redfish data / configuration param= eters for our HBAs using our UEFI driver? As a follow-up, we did some more experimentation for this issue and, while = we haven't yet figured out what the issue is, maybe someone will have some = insight into what we're seeing. The first thing we wanted to confirm was whether the reason data was not sh= owing up under Redfish was because I was loading the sample driver too late= in the boot process. To confirm this, we changed to using our own Option = ROM instead of the DriverSample, specifically changing some of our HII sett= ings to flag that they were REST_STYLE, as well as added the "x-UEFI-ns" la= nguage to them, which is what the sample details. These changes were built = into our Option ROM driver so they automatically load on system boot. Howe= ver, this did not change the behavior on the system and our parameters stil= l do not show up under $(IP)/redfish/v1/Systems/1/Bios (or anywhere else I = searched for). Is possible that these settings are pushed to the BMC before= any Option ROM drivers are loaded? To confirm that I was building these settings correctly, I created a test a= pplication that used the EFI_CONFIG_KEYWORD_HANDLER_PROTOCOL to query param= eters in the system by their namespaces. I could see tons of settings in th= e "x-UEFI" namespace, and the couple that I've presented in the "x-UEFI-ns"= namespace. I even see some onboard Option ROM settings (like an Onboard NI= C) that show up using the EFI_CONFIG_KEYWORD_HANDLER_PROTOCOL and show up u= nder some /Oem attribute area in the Redfish output (not under the expected= System/1/Bios area). However, no matter what I've done I can't see to get = any of our settings to show up in the Redfish output. I even changed our na= mespace to "x-UEFI" as a test, but that didn't do anything. Does anyone have any experience with this? Is this something that System Fi= rmware will do on a case-by-case basis, based on what is expected on the sy= stem? Is there a consistent place I should be looking for HII settings fla= gged in this way, or will that vary based on implementation. I plan on try= ing a wider variety of platforms to see if this is consistent behavior, but= I wanted to make sure what I was doing made sense in the first place. Thank you for any insight into this. -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#120678): https://edk2.groups.io/g/devel/message/120678 Mute This Topic: https://groups.io/mt/109174504/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io] -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- --_000_CH3PR12MB8851339B59B07C6FF1875D26D94E2CH3PR12MB8851namp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi tdoedline,

For the UEFI Redfish design and implementation, please check below links:
And it seems to me that you are working on PCIe storage device. I would sug= gest you to check Redfish Device Enablement (RDE): https://www= .dmtf.org/dsp/DSP0218  In this way, you don't rely on UEFI BIOS to= communicate with BMC. 

Add @Chang, Abner for this Redfish topic.

Regards,

Nickle

 


From: devel@= edk2.groups.io <devel@edk2.groups.io> on behalf of tdoedline via grou= ps.io <tdoedline=3Datto.com@groups.io>
Sent: Monday, October 21, 2024 9:41 PM
To: devel@edk2.groups.io <devel@edk2.groups.io>
Subject: [edk2-devel] Exposing Redfish data via HII
 
External email: Use caution opening links or attachments

Hi,
 
Let me know if this isn't the correct place to post this, but I was di= rected here from the Redfish forum.  I work for a hardware company tha= t develops storage and network HBAs. We already expose a set of HII configu= ration utilities for display and modification of settings and health data for our adapters in UEFI.  We are looking= to add some of these features and functionality to the system's exposed Re= dfish interface to allow user configuration through additional means. = Specifically, we are interested in the section "Bridging HII and Redfish" in the following presentation:
 
uefi.org/sites/d= efault/files/resources/13_Jason_HPE_redfish%20implementation_FINAL.pdf<= /div>
 
 
In order understand better how this works we attempted to use the Driv= erSampleDxe in the edk2 as an example of what we should expect to see when = something with a REST_STYLE flag is presented to a system.  Specifical= ly, looking at examples like the x-UEFI HII options, like this one:
 
#string STR_ONE_OF_PRO= MPT_X_UEFI #language en-US "x-UEFI HII Option"
#language fr-FR "x-UEFI HII Option"
#language x-UEFI-ns "xUefiHiiOption"
#string STR_ONE_OF_PROMPT_X_UEFI_HELP #language en-US "This is an HII = option which has REST_STYLE flag and x-UEFI namespace UNI string associated= . This HII option could be configured by either in-band edk2 setup browser = or the remote management in out-of-band such as Redfish service. This HII option is configured through EFI_KEYWORD= _HANDLER_PROTOCOL."
 
 
We built and loaded the DriverSampleDxe driver on example servers from= three different vendors, and while the HII forms show up correctly in the = System Setup when booting the system (including these fields that are flagg= ed as REST_STYLE with help text saying that they should be present in Redfish), nothing new shows up under= $(IP)/redfish/v1/Systems/1/Bios.  To be clear, what we did was boot t= o a UEFI shell, load the DriverSampleDxe, exit back to the System Setup to = confirm that the HII forms are loaded successfully, then attempted to query the Redfish data looking for additio= nal fields.

Is the expected behavior of the sample driver?  Is our issue that the = information about the BIOS settings has already been queried by / pushed to= the BMC, so any changes once we boot to the shell are not reflected in the= BMC?  Or are we not looking in the correct location for fields that are presented by an add-in driver?  Or is th= is model not really supported for add-in drivers and the REST_STYLE functio= nality is reserved for drivers present in the system firmware itself? = Is there another example or methodology to do what we want to do, which is to populate Redfish data / configuration p= arameters for our HBAs using our UEFI driver?
 
 
As a follow-up, we did some more experimentation for this issue and, w= hile we haven't yet figured out what the issue is, maybe someone will have = some insight into what we're seeing.
 
The first thing we wanted to confirm was whether the reason data was n= ot showing up under Redfish was because I was loading the sample driver too= late in the boot process.  To confirm this, we changed to using our o= wn Option ROM instead of the DriverSample, specifically changing some of our HII settings to flag that they were REST= _STYLE, as well as added the "x-UEFI-ns" language to them, which = is what the sample details. These changes were built into our Option ROM dr= iver so they automatically load on system boot.  However, this did not change the behavior on the system and ou= r parameters still do not show up under $(IP)/redfish/v1/Systems/1/Bios (or= anywhere else I searched for). Is possible that these settings are pushed = to the BMC before any Option ROM drivers are loaded?
 
To confirm that I was building these settings correctly, I created a t= est application that used the EFI_CONFIG_KEYWORD_HANDLER_PROTOCOL to query = parameters in the system by their namespaces. I could see tons of settings = in the "x-UEFI" namespace, and the couple that I've presented in the "x-UEFI-ns" namespace. I even = see some onboard Option ROM settings (like an Onboard NIC) that show up usi= ng the EFI_CONFIG_KEYWORD_HANDLER_PROTOCOL and show up under some /Oem attr= ibute area in the Redfish output (not under the expected System/1/Bios area). However, no matter what I've done I can'= t see to get any of our settings to show up in the Redfish output. I even c= hanged our namespace to "x-UEFI" as a test, but that didn't do an= ything.
 
Does anyone have any experience with this? Is this something that Syst= em Firmware will do on a case-by-case basis, based on what is expected on t= he system?  Is there a consistent place I should be looking for HII se= ttings flagged in this way, or will that vary based on implementation.  I plan on trying a wider variety of pl= atforms to see if this is consistent behavior, but I wanted to make sure wh= at I was doing made sense in the first place.

Thank you for any insight into this.
_._,_._,_
Groups.io Links:

=20 You receive all messages sent to this group. =20 =20

View/Reply Online (#120678) | =20 | Mute= This Topic | New Topic
Your Subscriptio= n | Contact Group Owner | Unsubscribe [rebecca@openfw.io]

_._,_._,_
--_000_CH3PR12MB8851339B59B07C6FF1875D26D94E2CH3PR12MB8851namp_--