Date   

lost stderr in console

wenyi,xie
 

Hi,everyone,

I used to set makeflags like below,so that only message from stderr will be shown in console while compiling, and at the same time message from stderr and stdout will all be saved in xxx.log.
COMMAND MAKEFLAGS= set -eo pipefail && sh xxx.sh 2>&1 >> ${LOG_FILE_DIR}/xxx.log | tee -a ${LOG_FILE_DIR}/xxx.log

But after updating edk2 from 201903 to 202011, the message from stderr is not shown in console any more. In xxx.log, the message from stderr and stdout are still saved.
Do anything change in edk2 may affect on it ?


回复: [edk2-discuss] 回复: Non-reproducible binaries generated by GenFw

gaoliming
 

Yes. Just RELEASE_*_*_GENFW_FLAGS = --zero

The format is defined in DSC spec. = means append, == means replacement.

Thanks
Liming

-----邮件原件-----
发件人: Ross Burton <ross@burtonini.com>
发送时间: 2021年3月17日 0:27
收件人: Laszlo Ersek <lersek@redhat.com>
抄送: discuss@edk2.groups.io; gaoliming <gaoliming@byosoft.com.cn>;
bob.c.feng@intel.com; yuwei.chen@intel.com
主题: Re: [edk2-discuss] 回复: Non-reproducible binaries generated by
GenFw

On Tue, 16 Mar 2021 at 16:15, Laszlo Ersek <lersek@redhat.com> wrote:
But: if you post such a patch for OVMF (modifying *all* DSC files in
OvmfPkg), then I'll review & merge it.
Is there any documentation for the dsc format? Specifically if a dsc
already has:

!if $(SOURCE_DEBUG_ENABLE) == TRUE
INTEL:*_*_X64_GENFW_FLAGS = --keepexceptiontable
!endif

Can I just do:
RELEASE_*_*_GENFW_FLAGS = --zero

Or do I need to use += or something else?

Ross


Re: GSOC 21 interested student

Nate DeSimone
 

Hi Vikas,

Great to meet you and welcome to the TianoCore project! Glad you hear you are interested! There are some existing tasks listed in the wiki for proposals. Another project which I haven't had a chance to add to the wiki yet is implementing a multi-threaded TCP/IP stack. There are been some work already done on this, that work is currently sitting here: https://github.com/tianocore/edk2-staging/tree/MpNetworkStack

I believe Maciej ran into issues with reconciling this work with the current UEFI spec and UNDI driver requirements. Though there is definitely a lot of promise here. From what I remember it increased network performance from 100 Mb/s to 1000 Mb/s. Figuring out what work is required to make this production ready and get it merged into the mainline would be a great improvement.

Let me know if you have any questions!

With Best Regards,
Nate

-----Original Message-----
From: discuss@edk2.groups.io <discuss@edk2.groups.io> On Behalf Of
vikasraist@gmail.com
Sent: Monday, March 15, 2021 11:42 AM
To: discuss@edk2.groups.io
Subject: [edk2-discuss] GSOC 21 interested student

Hi everyone, I am Vikas Kundu, a post-grad student of Computer Science in
India. I can code in Python, node.js, C and C++ and is aware of networking
concepts especially DNS. I wish to work on the UEFI Networking
Improvements part. Currently i am in the process of reading the
documentation for the same on the tianocore and nbd repos. I wish to look
forward for guidance from this community. My github profile is:
https://www.github.com/vikas-kundu.





Re: Google Summer of Code Interested Student

Nate DeSimone
 

Hi Laszlo,

-----Original Message-----
From: discuss@edk2.groups.io <discuss@edk2.groups.io> On Behalf Of
Laszlo Ersek
Sent: Tuesday, March 16, 2021 8:24 AM
To: Desimone, Nathaniel L <nathaniel.l.desimone@intel.com>
Cc: discuss@edk2.groups.io; cadenkline9@gmail.com; edk2-devel-groups-io
<devel@edk2.groups.io>; Ard Biesheuvel (TianoCore)
<ardb+tianocore@kernel.org>; Leif Lindholm (Nuvia address)
<leif@nuviainc.com>
Subject: Re: [edk2-discuss] Google Summer of Code Interested Student

Hi Nate,

(adding Leif and Ard)

On 03/13/21 03:52, Desimone, Nathaniel L wrote:
I've created a new wiki page for this task with all the information I
have gathered thus far. I've done some more experimentation and found
that there are several newer terminal emulators that don't support DEC
Special Graphics so I've reduced the number of modes where DEC Special
Graphics should be preferred. Laszlo, if you could take a look at the
terminal type matrix I created that would be very helpful.

https://github.com/tianocore/tianocore.github.io/wiki/Tasks-Terminal-d
river-improvements
(

My background:

I settled on plain (non-UTF-8) xterm around 1998, and have been using it
ever since. Whenever something was off, I always tried to hammer the
application into conformance with my particular xterm setup, rather than the
other way around. I also have some quirky terminal settings -- for me,
"backspace" generates ^H / keycode 22 (stty sets erase to ^H), "delete"
generates keycode 119, and there's no "rubout". I still don't use UTF-8 (I use
latin2).

)

* Regarding ArmVirtPkg, I stick with the default TTY_TERMINAL=FALSE
setting (which means VT-100). Using that setting, I see the following
kind of "ASCII approximation" for box drawing:

/------------------------------------------------------------------------------\
| Boot Manager |
\------------------------------------------------------------------------------/

I'm really happy with this, as I don't care much for nice-looking
boxes; instead I prefer portability.

(NB: this seems to disagree with your "Current Behavior (Which is
wrong)" line for VT100, as it suggests CP437. That's not what I'm
seeing with VT100.)
I went back and looked at this is more detail, and I missed the following critical detail:

if (TerminalDevice->TerminalType != TerminalTypePcAnsi) {
GraphicChar = AsciiChar;
}

Yes you are totally right! I've adjusted the table to reflect this behavior.


TTY_TERMINAL=TRUE would mainly affect backspace / delete I think -- as
far as I recall, that's why I asked Roy not to make TTY_TERMINAL=TRUE
the default, in 2015:

http://mid.mail-archive.com/555458DB.3090602@redhat.com
http://mid.mail-
archive.com/CAFECyb_E+bGZt5xv7QhRqyD0jX=AzoEMw7VW_tjZr+E=sQf8w
w@mail.gmail.com

(I'd like to CC Roy, but I can't tell if he's now working for Linaro,
Cavium, HPE, Marvell, or another company.)

* Regarding OvmfPkg, currently PC_ANSI is hard-coded, and for me it
looks like this:


ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄż
ł Boot Manager ł

ŔÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄŮ

Obviously I'd much prefer if I got the simple ASCII approximation here
as well.

* Whether VT100 and/or PC_ANSI and/or TTY_TERM are *officially*
supposed
to use DEC Special Graphics, I can't tell.
The UEFI spec doesn't read on this at all, even though it describes VT100 and VT100+ as separate modes... it doesn't say how they differ. I agree with you that it seems reasonable for VT100 to keep character output to strict ASCII only... that way the "+" in VT100+ actually means something. I've updated the wiki accordingly.

I'd advocate for the default to be switched to VT_UTF8. I really don't think you will run into many terminal emulators that don't implement UTF-8 anymore, XTerm included. Those who want pure ASCII output can switch to VT100.


I know what my preferences are:

- the current BackSpace and Delete mappings (which work fine for me
with both VT100 and PC_ANSI, but *not* with TTY_TERM),

- and the most primitive ASCII mapping (no special graphics, no UTF-8
sequences, etc). I really like a super dumb terminal, where taking
simple "ASCII screenshots" (and pasting them into plaintext emails!)
is *trivial*.

... Looking at your "Expected Behavior" table, there is only one line
left with "poor man's ASCII" -- namely, TTY_TERM. Unfortunately,
TTY_TERM breaks my BackSpace / Delete settings :(

* In summary, I'd prefer if (a) VT100 stayed as-is (using "poor man's
ASCII", as seen in ArmVirtPkg), and (b) if OVMF used *that* VT100,
rather than PC_ANSI, by default.

Thanks!
Laszlo





GSOC 21 interested student

vikasraist@...
 

Hi everyone, I am Vikas Kundu, a post-grad student of Computer Science in India. I can code in Python, node.js, C and C++ and is aware of networking concepts especially DNS. I wish to work on the UEFI Networking Improvements part. Currently i am in the process of reading the documentation for the same on the tianocore and nbd repos. I wish to look forward for guidance from this community. My github profile is: https://www.github.com/vikas-kundu.


Re: 回复: Non-reproducible binaries generated by GenFw

Ross Burton
 

On Tue, 16 Mar 2021 at 16:15, Laszlo Ersek <lersek@redhat.com> wrote:
But: if you post such a patch for OVMF (modifying *all* DSC files in
OvmfPkg), then I'll review & merge it.
Is there any documentation for the dsc format? Specifically if a dsc
already has:

!if $(SOURCE_DEBUG_ENABLE) == TRUE
INTEL:*_*_X64_GENFW_FLAGS = --keepexceptiontable
!endif

Can I just do:
RELEASE_*_*_GENFW_FLAGS = --zero

Or do I need to use += or something else?

Ross


Re: 回复: Non-reproducible binaries generated by GenFw

Laszlo Ersek
 

On 03/15/21 18:40, Ross Burton wrote:
On Fri, 12 Mar 2021 at 18:37, Laszlo Ersek <lersek@redhat.com> wrote:
I'm failing at making this actually stick in the makefiles though...
Can you provide your platform DSC file?

What is your exact "build" command line? (I'm looking for the "-a",
"-b", "-t" options.)
Essentially, OvmfPkg/build.sh -a X86 -b RELEASE -t GCC5. It appears I
should be editing OvmfPkg/OvmfX86.dsc instead of ShellPkg.dsc.

Is it agreed that this should be fixed? Is putting
RELEASE_*_*_GENFW_FLAGS=-z all over the repository the right solution,
or is there a better solution that can be done once centrally?
I'm a bit torn myself (I can't imagine a good reason why we *wouldn't*
want to make --zero the default for GenFw in RELEASE builds).

But: if you post such a patch for OVMF (modifying *all* DSC files in
OvmfPkg), then I'll review & merge it.

OvmfPkg/AmdSev/AmdSevX64.dsc
OvmfPkg/Bhyve/BhyveX64.dsc
OvmfPkg/OvmfPkgIa32.dsc
OvmfPkg/OvmfPkgIa32X64.dsc
OvmfPkg/OvmfPkgX64.dsc
OvmfPkg/OvmfXen.dsc

Thanks
Laszlo


Re: Google Summer of Code Interested Student

Laszlo Ersek
 

Hi Nate,

(adding Leif and Ard)

On 03/13/21 03:52, Desimone, Nathaniel L wrote:
I've created a new wiki page for this task with all the information I
have gathered thus far. I've done some more experimentation and found
that there are several newer terminal emulators that don't support
DEC Special Graphics so I've reduced the number of modes where DEC
Special Graphics should be preferred. Laszlo, if you could take a
look at the terminal type matrix I created that would be very
helpful.

https://github.com/tianocore/tianocore.github.io/wiki/Tasks-Terminal-driver-improvements
(

My background:

I settled on plain (non-UTF-8) xterm around 1998, and have been using it
ever since. Whenever something was off, I always tried to hammer the
application into conformance with my particular xterm setup, rather than
the other way around. I also have some quirky terminal settings -- for
me, "backspace" generates ^H / keycode 22 (stty sets erase to ^H),
"delete" generates keycode 119, and there's no "rubout". I still don't
use UTF-8 (I use latin2).

)

* Regarding ArmVirtPkg, I stick with the default TTY_TERMINAL=FALSE
setting (which means VT-100). Using that setting, I see the following
kind of "ASCII approximation" for box drawing:

/------------------------------------------------------------------------------\
| Boot Manager |
\------------------------------------------------------------------------------/

I'm really happy with this, as I don't care much for nice-looking
boxes; instead I prefer portability.

(NB: this seems to disagree with your "Current Behavior (Which is
wrong)" line for VT100, as it suggests CP437. That's not what I'm
seeing with VT100.)

TTY_TERMINAL=TRUE would mainly affect backspace / delete I think -- as
far as I recall, that's why I asked Roy not to make TTY_TERMINAL=TRUE
the default, in 2015:

http://mid.mail-archive.com/555458DB.3090602@redhat.com
http://mid.mail-archive.com/CAFECyb_E+bGZt5xv7QhRqyD0jX=AzoEMw7VW_tjZr+E=sQf8ww@mail.gmail.com

(I'd like to CC Roy, but I can't tell if he's now working for Linaro,
Cavium, HPE, Marvell, or another company.)

* Regarding OvmfPkg, currently PC_ANSI is hard-coded, and for me it
looks like this:

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄż
ł Boot Manager ł
ŔÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄŮ

Obviously I'd much prefer if I got the simple ASCII approximation here
as well.

* Whether VT100 and/or PC_ANSI and/or TTY_TERM are *officially* supposed
to use DEC Special Graphics, I can't tell.

I know what my preferences are:

- the current BackSpace and Delete mappings (which work fine for me
with both VT100 and PC_ANSI, but *not* with TTY_TERM),

- and the most primitive ASCII mapping (no special graphics, no UTF-8
sequences, etc). I really like a super dumb terminal, where taking
simple "ASCII screenshots" (and pasting them into plaintext emails!)
is *trivial*.

... Looking at your "Expected Behavior" table, there is only one line
left with "poor man's ASCII" -- namely, TTY_TERM. Unfortunately,
TTY_TERM breaks my BackSpace / Delete settings :(

* In summary, I'd prefer if (a) VT100 stayed as-is (using "poor man's
ASCII", as seen in ArmVirtPkg), and (b) if OVMF used *that* VT100,
rather than PC_ANSI, by default.

Thanks!
Laszlo


Re: Redfish Host Interface

Russell Peterson
 

Thanks so much, Abner. This is all very helpful to me.

Regards,

Russell

-----Original Message-----
From: discuss@edk2.groups.io <discuss@edk2.groups.io> On Behalf Of Abner Chang via groups.io
Sent: Monday, March 15, 2021 9:10 PM
To: Russell Peterson <russell@nvidia.com>; discuss@edk2.groups.io; Laszlo Ersek <lersek@redhat.com>
Cc: Wang, Nickle (HPS SW) <nickle.wang@hpe.com>
Subject: Re: [edk2-discuss] Redfish Host Interface



-----Original Message-----
From: Russell Peterson [mailto:russell@nvidia.com]
Sent: Monday, March 15, 2021 7:42 PM
To: discuss@edk2.groups.io; Chang, Abner (HPS SW/FW Technologist)
<abner.chang@hpe.com>; Laszlo Ersek <lersek@redhat.com>
Cc: Wang, Nickle (HPS SW) <nickle.wang@hpe.com>
Subject: RE: [edk2-discuss] Redfish Host Interface

Thanks for the response Laszlo and Abner. Very much appreciated.

Do I understand correctly that if I have a BMC with the proper schema
for my system UEFI, when the system boots it (UEFI) will fetch data
from the BMC via the Redfish host interface and that data would in effect, "take priority"
over the data stored in the UPVS? I mean not only for boot order but
also any other configuration data?
Not quite sure what is UPVS stands for.
You are right, not only the boot order but also other properties defined in schema. Map HII to Redfish property using EFI keyword is the phase 2 plan for edk2.


I assume UEFI has some type of discovery mechanism and authentication
mechanism to find and use the BMC Redfish data. From what I have read
this seems to be the case.
Yes, the discovery mechanism for Redfish service is over Redfish HI or SSDP. Platform library has to provide the library to edk2 Redfish core code to build up SMBIOS type 42 table, and the library for acquiring Redfish credential which is OEM implementation-specific.
You can refer to below link for detail information, https://github.com/tianocore/edk2-staging/tree/UEFI_Redfish, few diagrams and descriptions may out of date but not too far from the implementation on edk2.

We still in the progress of contributing edk2 Redfish foundation code. It is almost there, we can finish this phase 1 work once UEFI spec 2.9 is released because there are some spec updates for EFI Redfish Discover Protocol.
After edk2 Redfish foundation, we will start to contribute edk2 Redfish client code. That is what I mentioned to map HII (BIOS configuration) to Redfish property for the remote management.

Thanks
Abner





--Russ

-----Original Message-----
From: discuss@edk2.groups.io <discuss@edk2.groups.io> On Behalf Of
Abner Chang via groups.io
Sent: Sunday, March 14, 2021 9:24 PM
To: Laszlo Ersek <lersek@redhat.com>; Russell Peterson
<russell@nvidia.com>
Cc: discuss@edk2.groups.io; Wang, Nickle (HPS SW)
<nickle.wang@hpe.com>
Subject: Re: [edk2-discuss] Redfish Host Interface



-----Original Message-----
From: Laszlo Ersek [mailto:lersek@redhat.com]
Sent: Saturday, March 13, 2021 6:11 AM
To: russell@nvidia.com
Cc: discuss@edk2.groups.io; Chang, Abner (HPS SW/FW Technologist)
<abner.chang@hpe.com>; Wang, Nickle (HPS SW)
<nickle.wang@hpe.com>
Subject: Re: [edk2-discuss] Redfish Host Interface

Hi Russell,

On 03/11/21 22:02, Russell Peterson wrote:
Hello,

I am interested in a UEFI Redfish Host Interface that does not
require an
OS.
Redfish Host Interface is built for OS to communicate with Redfish
service on either BMC or out-of-band service (I don’t see this use
case yet). UEFI use case is similar to how OS communicates with
Redfish service through Redfish HI.

That is, the Redfish service would be provided by UEFI itself (via
an IP interface)... or perhaps an EFI application.
This is interesting , however you will need edk2 web server and the
implementation of Redfish service on edk2 as well. Not sure how this
use case works for OS <-> in-band Redfish service on edk2. Or you just
would like to build up an stand along Redfish service on edk2 and
other Redfish clients can connect to it?

For example, if a BMC wanted to access EFI variables directly from
UEFI via
an IP interface with no functional OS present.
Redfish HI just provides the Redfish information to Redfish clients,
the majority users are OS and firmware. Client sends the request to
service for the property through HTTP. Rare use cases that service
asks client for something on its own initiative, Redfish event service
is one of the service- to-client action however client has to registers even first.
So BMC accesses to EFI variable through Redfish HI seems to me not an
use case of generic Redfish services.


Is this crazy for me to think this? Already exists? Under
development? An
idea... but I would need to do some work?

At least the following TianoCore bugzilla <INVALID URI REMOVED
re.org_&d=DwIGaQ&c=C5b8zRQO1miGmBeVZ2LFWg&r=_SN6FZBN4Vgi4Ulk
skz6qU3NYR
O03nHp9P7Z5q59A3E&m=cleBHtjxzgg6TX8uY7CL9wbNT3KZExKhTcVbhTAay
M4&s=Bj48
Z9S2NrOzp1mB8LD4F83t22B1dBuQqeIcseTXQYQ&e= > tickets relate to
RedFish, one way or
another:
Laszlo, thanks for providing below information.
Abner

2337
2906
2910
2911
2912
2913
2918
2919
2930
2931
2932
2933
2934
2936
3102
3173
3174

At least the following USWG Mantis tickets relate to RedFish:

0001221
0001834
0001853
0001920
0001925
0001935
0001941
0002000
0002009
0002172

In UEFI v2.8B, there is a chapter called "31 - EFI Redfish Service Support".

A top-level RedfishPkg exists in edk2, and it seems like EmulatorPkg
has received some enablement. Not sure about the state in
edk2-platforms (or in other out-of-tree platforms).

Adding Abner and Nickle to the CC list (per "Maintainers.txt");
hopefully they can summarize the status for you.

Thanks
Laszlo





Re: Redfish Host Interface

Abner Chang
 

-----Original Message-----
From: Russell Peterson [mailto:russell@nvidia.com]
Sent: Monday, March 15, 2021 7:42 PM
To: discuss@edk2.groups.io; Chang, Abner (HPS SW/FW Technologist)
<abner.chang@hpe.com>; Laszlo Ersek <lersek@redhat.com>
Cc: Wang, Nickle (HPS SW) <nickle.wang@hpe.com>
Subject: RE: [edk2-discuss] Redfish Host Interface

Thanks for the response Laszlo and Abner. Very much appreciated.

Do I understand correctly that if I have a BMC with the proper schema for my
system UEFI, when the system boots it (UEFI) will fetch data from the BMC
via the Redfish host interface and that data would in effect, "take priority"
over the data stored in the UPVS? I mean not only for boot order but also
any other configuration data?
Not quite sure what is UPVS stands for.
You are right, not only the boot order but also other properties defined in schema. Map HII to Redfish property using EFI keyword is the phase 2 plan for edk2.


I assume UEFI has some type of discovery mechanism and authentication
mechanism to find and use the BMC Redfish data. From what I have read
this seems to be the case.
Yes, the discovery mechanism for Redfish service is over Redfish HI or SSDP. Platform library has to provide the library to edk2 Redfish core code to build up SMBIOS type 42 table, and the library for acquiring Redfish credential which is OEM implementation-specific.
You can refer to below link for detail information,
https://github.com/tianocore/edk2-staging/tree/UEFI_Redfish, few diagrams and descriptions may out of date but not too far from the implementation on edk2.

We still in the progress of contributing edk2 Redfish foundation code. It is almost there, we can finish this phase 1 work once UEFI spec 2.9 is released because there are some spec updates for EFI Redfish Discover Protocol.
After edk2 Redfish foundation, we will start to contribute edk2 Redfish client code. That is what I mentioned to map HII (BIOS configuration) to Redfish property for the remote management.

Thanks
Abner





--Russ

-----Original Message-----
From: discuss@edk2.groups.io <discuss@edk2.groups.io> On Behalf Of
Abner Chang via groups.io
Sent: Sunday, March 14, 2021 9:24 PM
To: Laszlo Ersek <lersek@redhat.com>; Russell Peterson
<russell@nvidia.com>
Cc: discuss@edk2.groups.io; Wang, Nickle (HPS SW)
<nickle.wang@hpe.com>
Subject: Re: [edk2-discuss] Redfish Host Interface



-----Original Message-----
From: Laszlo Ersek [mailto:lersek@redhat.com]
Sent: Saturday, March 13, 2021 6:11 AM
To: russell@nvidia.com
Cc: discuss@edk2.groups.io; Chang, Abner (HPS SW/FW Technologist)
<abner.chang@hpe.com>; Wang, Nickle (HPS SW)
<nickle.wang@hpe.com>
Subject: Re: [edk2-discuss] Redfish Host Interface

Hi Russell,

On 03/11/21 22:02, Russell Peterson wrote:
Hello,

I am interested in a UEFI Redfish Host Interface that does not require an
OS.
Redfish Host Interface is built for OS to communicate with Redfish service on
either BMC or out-of-band service (I don’t see this use case yet). UEFI use
case is similar to how OS communicates with Redfish service through Redfish
HI.

That is, the Redfish service would be provided by UEFI itself (via an
IP interface)... or perhaps an EFI application.
This is interesting , however you will need edk2 web server and the
implementation of Redfish service on edk2 as well. Not sure how this use
case works for OS <-> in-band Redfish service on edk2. Or you just would like
to build up an stand along Redfish service on edk2 and other Redfish clients
can connect to it?

For example, if a BMC wanted to access EFI variables directly from
UEFI via
an IP interface with no functional OS present.
Redfish HI just provides the Redfish information to Redfish clients, the
majority users are OS and firmware. Client sends the request to service for
the property through HTTP. Rare use cases that service asks client for
something on its own initiative, Redfish event service is one of the service-
to-client action however client has to registers even first.
So BMC accesses to EFI variable through Redfish HI seems to me not an use
case of generic Redfish services.


Is this crazy for me to think this? Already exists? Under
development? An
idea... but I would need to do some work?

At least the following TianoCore bugzilla
<INVALID URI REMOVED
re.org_&d=DwIGaQ&c=C5b8zRQO1miGmBeVZ2LFWg&r=_SN6FZBN4Vgi4Ulk
skz6qU3NYR
O03nHp9P7Z5q59A3E&m=cleBHtjxzgg6TX8uY7CL9wbNT3KZExKhTcVbhTAay
M4&s=Bj48
Z9S2NrOzp1mB8LD4F83t22B1dBuQqeIcseTXQYQ&e= > tickets relate to
RedFish, one way or
another:
Laszlo, thanks for providing below information.
Abner

2337
2906
2910
2911
2912
2913
2918
2919
2930
2931
2932
2933
2934
2936
3102
3173
3174

At least the following USWG Mantis tickets relate to RedFish:

0001221
0001834
0001853
0001920
0001925
0001935
0001941
0002000
0002009
0002172

In UEFI v2.8B, there is a chapter called "31 - EFI Redfish Service Support".

A top-level RedfishPkg exists in edk2, and it seems like EmulatorPkg
has received some enablement. Not sure about the state in
edk2-platforms (or in other out-of-tree platforms).

Adding Abner and Nickle to the CC list (per "Maintainers.txt");
hopefully they can summarize the status for you.

Thanks
Laszlo





回复: [edk2-discuss] Non-reproducible binaries generated by GenFw

gaoliming
 

Andrew:

-----邮件原件-----
发件人: discuss@edk2.groups.io <discuss@edk2.groups.io> 代表 Andrew
Fish via groups.io
发送时间: 2021年3月16日 2:56
收件人: discuss <discuss@edk2.groups.io>; ross@burtonini.com
抄送: Feng, Bob C <bob.c.feng@intel.com>; Liming Gao (Byosoft address)
<gaoliming@byosoft.com.cn>; yuwei.chen@intel.com
主题: Re: [edk2-discuss] Non-reproducible binaries generated by GenFw


On Mar 10, 2021, at 11:36 AM, Ross Burton <ross@burtonini.com> wrote:

Hi,

As per https://bugzilla.tianocore.org/show_bug.cgi?id=3256, GenFw
writes non-reproducible binaries by embedding a build path. In fact in
a build of ovmf with embedded shell, this one path is the sole source
of non-determinism.

WriteDebug64() is always called in GenFw on output and that embeds
into the NB10 entry the input filename. As build paths change this is
a source of non-determinism. There already exists a --zero option to
wipe out debug paths but this is in release builds so I'm not sure
what the best solution is. I can see several options:

1) Release builds should not call WriteDebug64() at all
2) --zero should wipe the NB10 entry, and release builds should pass that
3) GenFw should support path remapping (like gcc's -ffile-prefix-map)
to turn build paths into something consistent.

Any suggestions?
This is kind of a tangent, but for clang we solved a similar problem a different
way.
1) in the build_rule.txt file we added a cd $(WORKSPACE); on the compile line
so __FILE__ is always relative to the $(WORKSPACE);
[Liming] CLANG compiler supports __FILE_NAME__ macro for the file name only. MdePkg DebugLib.h has applied this definition.

#if defined(__clang__) && defined(__FILE_NAME__)
#define _ASSERT(Expression) DebugAssert (__FILE_NAME__, __LINE__, #Expression)
#else
#define _ASSERT(Expression) DebugAssert (__FILE__, __LINE__, #Expression)
#endif

Thanks
Liming
2) We added a post build step to create a Symbols directory in the Build
output.
a) The debug directory entry paths are relative to that symbols directory.
They generally look like IA32/PeiCore or X64/DxeCore etc.
b) In the old days we would launch the debugger from the Symbols
directory so relative files got searched relative to the symbols directory.
c) Now we use the UUID we have in the
EFI_IMAGE_DEBUG_CODEVIEW_RSDS_ENTRY[1]PE/COFF debug entry. On a
Mac these mach-O UUIDs are automatically indexed by Spotlight so the
debugger can just find them. It is also possible to write a tool to lookup these
UUIDs that makes them available to the debugger.

I’m not sure it is possible to do something like this with all the toolchains, but
I wanted to at least let people know we figured out a way with clang.

[1]
https://github.com/tianocore/edk2/blob/master/MdePkg/Include/IndustrySt
andard/PeImage.h#L659

Thanks,

Andrew Fish

Cheers,
Ross








回复: [edk2-discuss] 回复: Non-reproducible binaries generated by GenFw

gaoliming
 

Ross:
This solution is for the reproduced binary images. If your platform has this request, you can update the platform DSC [BuildOptions] to include the option RELEASE_*_*_GENFW_FLAGS=-z.

Thanks
Liming

-----邮件原件-----
发件人: Ross Burton <ross@burtonini.com>
发送时间: 2021年3月16日 1:40
收件人: Laszlo Ersek <lersek@redhat.com>
抄送: discuss@edk2.groups.io; gaoliming <gaoliming@byosoft.com.cn>;
bob.c.feng@intel.com; yuwei.chen@intel.com
主题: Re: [edk2-discuss] 回复: Non-reproducible binaries generated by
GenFw

On Fri, 12 Mar 2021 at 18:37, Laszlo Ersek <lersek@redhat.com> wrote:
I'm failing at making this actually stick in the makefiles though...
Can you provide your platform DSC file?

What is your exact "build" command line? (I'm looking for the "-a",
"-b", "-t" options.)
Essentially, OvmfPkg/build.sh -a X86 -b RELEASE -t GCC5. It appears I
should be editing OvmfPkg/OvmfX86.dsc instead of ShellPkg.dsc.

Is it agreed that this should be fixed? Is putting
RELEASE_*_*_GENFW_FLAGS=-z all over the repository the right solution,
or is there a better solution that can be done once centrally?

Ross


Re: Non-reproducible binaries generated by GenFw

Andrew Fish
 

On Mar 10, 2021, at 11:36 AM, Ross Burton <ross@burtonini.com> wrote:

Hi,

As per https://bugzilla.tianocore.org/show_bug.cgi?id=3256, GenFw
writes non-reproducible binaries by embedding a build path. In fact in
a build of ovmf with embedded shell, this one path is the sole source
of non-determinism.

WriteDebug64() is always called in GenFw on output and that embeds
into the NB10 entry the input filename. As build paths change this is
a source of non-determinism. There already exists a --zero option to
wipe out debug paths but this is in release builds so I'm not sure
what the best solution is. I can see several options:

1) Release builds should not call WriteDebug64() at all
2) --zero should wipe the NB10 entry, and release builds should pass that
3) GenFw should support path remapping (like gcc's -ffile-prefix-map)
to turn build paths into something consistent.

Any suggestions?
This is kind of a tangent, but for clang we solved a similar problem a different way.
1) in the build_rule.txt file we added a cd $(WORKSPACE); on the compile line so __FILE__ is always relative to the $(WORKSPACE);
2) We added a post build step to create a Symbols directory in the Build output.
a) The debug directory entry paths are relative to that symbols directory. They generally look like IA32/PeiCore or X64/DxeCore etc.
b) In the old days we would launch the debugger from the Symbols directory so relative files got searched relative to the symbols directory.
c) Now we use the UUID we have in the EFI_IMAGE_DEBUG_CODEVIEW_RSDS_ENTRY[1]PE/COFF debug entry. On a Mac these mach-O UUIDs are automatically indexed by Spotlight so the debugger can just find them. It is also possible to write a tool to lookup these UUIDs that makes them available to the debugger.

I’m not sure it is possible to do something like this with all the toolchains, but I wanted to at least let people know we figured out a way with clang.

[1] https://github.com/tianocore/edk2/blob/master/MdePkg/Include/IndustryStandard/PeImage.h#L659

Thanks,

Andrew Fish

Cheers,
Ross





Re: 回复: Non-reproducible binaries generated by GenFw

Ross Burton
 

On Fri, 12 Mar 2021 at 18:37, Laszlo Ersek <lersek@redhat.com> wrote:
I'm failing at making this actually stick in the makefiles though...
Can you provide your platform DSC file?

What is your exact "build" command line? (I'm looking for the "-a",
"-b", "-t" options.)
Essentially, OvmfPkg/build.sh -a X86 -b RELEASE -t GCC5. It appears I
should be editing OvmfPkg/OvmfX86.dsc instead of ShellPkg.dsc.

Is it agreed that this should be fixed? Is putting
RELEASE_*_*_GENFW_FLAGS=-z all over the repository the right solution,
or is there a better solution that can be done once centrally?

Ross


Re: Redfish Host Interface

Russell Peterson
 

Thanks for the response Laszlo and Abner. Very much appreciated.

Do I understand correctly that if I have a BMC with the proper schema for my system UEFI, when the system boots it (UEFI) will fetch data from the BMC via the Redfish host interface and that data would in effect, "take priority" over the data stored in the UPVS? I mean not only for boot order but also any other configuration data?

I assume UEFI has some type of discovery mechanism and authentication mechanism to find and use the BMC Redfish data. From what I have read this seems to be the case.

--Russ

-----Original Message-----
From: discuss@edk2.groups.io <discuss@edk2.groups.io> On Behalf Of Abner Chang via groups.io
Sent: Sunday, March 14, 2021 9:24 PM
To: Laszlo Ersek <lersek@redhat.com>; Russell Peterson <russell@nvidia.com>
Cc: discuss@edk2.groups.io; Wang, Nickle (HPS SW) <nickle.wang@hpe.com>
Subject: Re: [edk2-discuss] Redfish Host Interface



-----Original Message-----
From: Laszlo Ersek [mailto:lersek@redhat.com]
Sent: Saturday, March 13, 2021 6:11 AM
To: russell@nvidia.com
Cc: discuss@edk2.groups.io; Chang, Abner (HPS SW/FW Technologist)
<abner.chang@hpe.com>; Wang, Nickle (HPS SW) <nickle.wang@hpe.com>
Subject: Re: [edk2-discuss] Redfish Host Interface

Hi Russell,

On 03/11/21 22:02, Russell Peterson wrote:
Hello,

I am interested in a UEFI Redfish Host Interface that does not require an OS.
Redfish Host Interface is built for OS to communicate with Redfish service on either BMC or out-of-band service (I don’t see this use case yet). UEFI use case is similar to how OS communicates with Redfish service through Redfish HI.

That is, the Redfish service would be provided by UEFI itself (via an
IP interface)... or perhaps an EFI application.
This is interesting , however you will need edk2 web server and the implementation of Redfish service on edk2 as well. Not sure how this use case works for OS <-> in-band Redfish service on edk2. Or you just would like to build up an stand along Redfish service on edk2 and other Redfish clients can connect to it?

For example, if a BMC wanted to access EFI variables directly from
UEFI via
an IP interface with no functional OS present.
Redfish HI just provides the Redfish information to Redfish clients, the majority users are OS and firmware. Client sends the request to service for the property through HTTP. Rare use cases that service asks client for something on its own initiative, Redfish event service is one of the service-to-client action however client has to registers even first.
So BMC accesses to EFI variable through Redfish HI seems to me not an use case of generic Redfish services.


Is this crazy for me to think this? Already exists? Under
development? An
idea... but I would need to do some work?

At least the following TianoCore bugzilla
<https://bugzilla.tianocore.org/> tickets relate to RedFish, one way
or
another:
Laszlo, thanks for providing below information.
Abner

2337
2906
2910
2911
2912
2913
2918
2919
2930
2931
2932
2933
2934
2936
3102
3173
3174

At least the following USWG Mantis tickets relate to RedFish:

0001221
0001834
0001853
0001920
0001925
0001935
0001941
0002000
0002009
0002172

In UEFI v2.8B, there is a chapter called "31 - EFI Redfish Service Support".

A top-level RedfishPkg exists in edk2, and it seems like EmulatorPkg
has received some enablement. Not sure about the state in
edk2-platforms (or in other out-of-tree platforms).

Adding Abner and Nickle to the CC list (per "Maintainers.txt");
hopefully they can summarize the status for you.

Thanks
Laszlo


Re: Redfish Host Interface

Abner Chang
 

-----Original Message-----
From: Laszlo Ersek [mailto:lersek@redhat.com]
Sent: Saturday, March 13, 2021 6:11 AM
To: russell@nvidia.com
Cc: discuss@edk2.groups.io; Chang, Abner (HPS SW/FW Technologist)
<abner.chang@hpe.com>; Wang, Nickle (HPS SW) <nickle.wang@hpe.com>
Subject: Re: [edk2-discuss] Redfish Host Interface

Hi Russell,

On 03/11/21 22:02, Russell Peterson wrote:
Hello,

I am interested in a UEFI Redfish Host Interface that does not require an OS.
Redfish Host Interface is built for OS to communicate with Redfish service on either BMC or out-of-band service (I don’t see this use case yet). UEFI use case is similar to how OS communicates with Redfish service through Redfish HI.

That is, the Redfish service would be provided by UEFI itself (via an IP
interface)... or perhaps an EFI application.
This is interesting , however you will need edk2 web server and the implementation of Redfish service on edk2 as well. Not sure how this use case works for OS <-> in-band Redfish service on edk2. Or you just would like to build up an stand along Redfish service on edk2 and other Redfish clients can connect to it?

For example, if a BMC wanted to access EFI variables directly from UEFI via
an IP interface with no functional OS present.
Redfish HI just provides the Redfish information to Redfish clients, the majority users are OS and firmware. Client sends the request to service for the property through HTTP. Rare use cases that service asks client for something on its own initiative, Redfish event service is one of the service-to-client action however client has to registers even first.
So BMC accesses to EFI variable through Redfish HI seems to me not an use case of generic Redfish services.


Is this crazy for me to think this? Already exists? Under development? An
idea... but I would need to do some work?

At least the following TianoCore bugzilla <https://bugzilla.tianocore.org/>
tickets relate to RedFish, one way or
another:
Laszlo, thanks for providing below information.
Abner

2337
2906
2910
2911
2912
2913
2918
2919
2930
2931
2932
2933
2934
2936
3102
3173
3174

At least the following USWG Mantis tickets relate to RedFish:

0001221
0001834
0001853
0001920
0001925
0001935
0001941
0002000
0002009
0002172

In UEFI v2.8B, there is a chapter called "31 - EFI Redfish Service Support".

A top-level RedfishPkg exists in edk2, and it seems like EmulatorPkg has
received some enablement. Not sure about the state in edk2-platforms (or
in other out-of-tree platforms).

Adding Abner and Nickle to the CC list (per "Maintainers.txt"); hopefully they
can summarize the status for you.

Thanks
Laszlo


Re: Google Summer of Code Interested Student

Nate DeSimone
 

Hi Laszlo,

-----Original Message-----
From: discuss@edk2.groups.io <discuss@edk2.groups.io> On Behalf Of
Laszlo Ersek
Sent: Friday, March 12, 2021 10:51 AM
To: Desimone, Nathaniel L <nathaniel.l.desimone@intel.com>;
cadenkline9@gmail.com
Cc: discuss@edk2.groups.io; devel@edk2.groups.io
Subject: Re: [edk2-discuss] Google Summer of Code Interested Student

As far as I can remember, the terminal type has always been hard-coded in
OVMF like this -- I believe it's not a regression (old or recent). I guess I
haven't seen a good PlatformBootManagerLib example on this topic.
Yeah specifically on the topic of properly setting the terminal type, I don't think I've seen a completely correct implementation of PlatformBootManagerLib either. Agreed it is probably not a regression, but I still think it would be a great contribution to get this sorted out properly.


Thanks
Laszlo





Re: Google Summer of Code Interested Student

Nate DeSimone
 

I've created a new wiki page for this task with all the information I have gathered thus far. I've done some more experimentation and found that there are several newer terminal emulators that don't support DEC Special Graphics so I've reduced the number of modes where DEC Special Graphics should be preferred. Laszlo, if you could take a look at the terminal type matrix I created that would be very helpful.

https://github.com/tianocore/tianocore.github.io/wiki/Tasks-Terminal-driver-improvements

Thanks,
Nate

-----Original Message-----
From: discuss@edk2.groups.io <discuss@edk2.groups.io> On Behalf Of Nate
DeSimone
Sent: Thursday, March 11, 2021 9:46 PM
To: cadenkline9@gmail.com
Cc: Laszlo Ersek <lersek@redhat.com>; discuss@edk2.groups.io;
devel@edk2.groups.io
Subject: Re: [edk2-discuss] Google Summer of Code Interested Student

Hi Caden,

Great to meet you and welcome to the TianoCore project! Glad you hear you
are interested! Sorry it has taken me a while to get back to you, researching
the topics you are interested in ended up being somewhat involved 😊.

I went back and did some investigation of current state of the terminal
driver, and some of the work has already been done. However, there are
some things missing and some odd bugs that need attention. To give you a
little more detail, the Terminal driver is located at
https://github.com/tianocore/edk2/tree/master/MdeModulePkg/Universal
/Console/TerminalDxe

The most prevalent use case for the terminal driver is to display the BIOS
setup menu on headless server systems using a PC style serial port
connected to a laptop via null modem. This allows administrators to adjust
BIOS settings on rack mounted systems without needing to connect a
monitor and keyboard.

Historically, the BIOS setup menu would be rendered using the IBM PC VGA
text mode, which encoded text using code page 437 (CP437). This was
important for box-drawing characters, such as ┌ , ─ , and ┐ , which VGA text
mode encodes as 0xDA, 0xC4, and 0xBF respectively. However, most
terminal emulators assume text to be encoded in UTF-8. Unicode defines
these box drawing characters as 0x250C, 0x2500, and 0x2510. In UTF-8
encoding, these characters translate into 3 byte sequences of (0xE2, 0x94,
0x8C), (0xE2, 0x94, 0x80), and (0xE2, 0x94, 0x90) respectively. The VGA
encodings of these box characters will end up generating errors if one
attempts to decode them as strict UTF-8, though most terminals assume that
the intended characters to be drawn are Ú, Ä, and ¿, which have the Unicode
character codes 0xDA, 0xC4, and 0xBF. The end result is the BIOS setup menu
looks like this:

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Device Manager ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

Devices List List all the Driver
> Driver Health Manager Health instances to
> RAM Disk Configuration manage
> OVMF Platform Configuration
> iSCSI Configuration
> Network Device List


Press ESC to exit.


ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ ³
³ ^v=Move Highlight <Enter>=Select Entry Esc=Exit ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

Instead of like this:

┌─────────────────────────────────────────────────────────
─────────────────────┐
│ Device Manager │
└─────────────────────────────────────────────────────────
─────────────────────┘

Devices List List all the Driver
> Driver Health Manager Health instances to
> RAM Disk Configuration manage
> OVMF Platform Configuration
> iSCSI Configuration
> Network Device List


Press ESC to exit.


┌─────────────────────────────────────────────────────────
─────────────────────┐
│ │
│ ^v=Move Highlight <Enter>=Select Entry Esc=Exit │
└─────────────────────────────────────────────────────────
─────────────────────┘

The terminal driver has fully supported both the legacy CP437 encoding and
the UTF-8 encoding for more than 10 years now. Which mode to use is part
of the configuration settings given to the terminal driver at start up.
However, those configuration settings need to come from somewhere. For
example, OVMF has the following page in its setup menu for configuring the
serial terminal:

┌─────────────────────────────────────────────────────────
─────────────────────┐
│ Set COM Attributes │
└─────────────────────────────────────────────────────────
─────────────────────┘

Set COM Baud Rate <115200> Set COM Baud Rate
Set COM Data Bits <8>
Set COM Parity <None>
Set COM Stop Bits <One>
Set COM Terminal Type <PC_ANSI>
Set COM Flow Control <None>

Commit Changes and Exit
Discard Changes and Exit


┌─────────────────────────────────────────────────────────
─────────────────────┐
│ F9=Reset to Defaults F10=Save │
│ ^v=Move Highlight <Enter>=Select Entry Esc=Exit │
└─────────────────────────────────────────────────────────
─────────────────────┘

The default terminal type is PC_ANSI, which uses CP437. In this day and age
that is probably not the right default anymore, though one could argue
whether PC_ANSI being the default is a "bug". Here is the list of supported
terminal types:

- PC_ANSI
- VT_100
- VT_100_PLUS
- VT_UTF8
- TTY_TERM
- LINUX
- XTERM_R6
- VT_400
- SCO

Now, here is the first unquestionable bug. All of these terminal types except
for VT_UTF8 output the box drawing characters using CP437. The VT-100 did
not use CP437 for box drawing characters. On the VT-100, the terminal driver
should output the escape sequence "ESC ( 0" to switch the character set
from ASCII to "DEC Special Graphics". Then, while in DEC Special Graphics
mode, ┌ , ─ , and ┐ , are encoded as 0x6C, 0x71, and 0x6B respectively. After
outputting the box drawing characters, the terminal driver should switch
back to ASCII using the escape sequence "ESC ( B". Implementing this will
introduce the interesting problem of optimizing display performance by
limiting the number of character mode switches.

For all the modes listed above, the VT-100 method should be used for
drawing box characters (and other characters in the DEC special graphics
character set) with the exception of PC_ANSI and VT_UTF8, which should
use CP437 and UTF-8 respectively. In general, DEC special graphics has been
around for such a long time that all terminal emulators support it, so it should
be the preferred method of outputting characters outside the initial 0-127
basic ASCII codes, with UTF-8 as a fallback if the character can't be encoded
by either basic ASCII or DEC special graphics. The difference between
VT_UTF8 and the other modes is that DEC special graphics should never be
used. PC_ANSI mode should never use DEC special graphics either.

Now, here is the second bug. That BIOS setup menu page that OVMF has for
configuring the serial port has a field for setting the terminal type. But,
changing the value in that field doesn't actually change the configuration data
that is sent to the terminal driver. So the terminal driver always ends up using
PC_ANSI mode even if the user changes that setting. This isn’t a bug in the
terminal driver really, it’s a bug in OVMF's setup menu implementation. But it
does create the appearance of a problem in the terminal driver and should
be fixed as part of this GSoC project. This should be fixed in both he OVMF
implementation and the MinPlatform implementation.

I'm not sure if the terminal driver improvements would absorb the entire 10
week coding window. If you had time left, you could consider spending it
writing unit tests.

Looking at your experience, it seems like you have more experience with
Python coding than with C coding. Both the terminal driver improvements
and unit tests would be written in C. Another option you could consider is we
have a lot of Python code in TianoCore as well. The two major pieces of
Python code are BaseTools and EdkRepo. BaseTools provides the build
system for TianoCore and implements the logic necessary to compile a BIOS
ROM file from source. EdkRepo is the multi-repository tool for EDK II.
EdkRepo automates common developer workflows for projects that use
more than one git repository (many TianoCore projects do). We would gladly
accept project proposals for either BaseTools or EdkRepo. If either of those
interest you I can point you to some places where they can be improved and
give you some project ideas.

The most important outcome from GSoC in our view is that our students
learn something, get some exposure, and have a great experience that they
will remember fondly for years to come. We want you to be successful.
Gauge your comfort level and pick a project that you feel you can achieve in
the 10 week period. Sorry for the long email, but I hope it helps. Finally I'd
like to reiterate... Welcome to the project!

With Best Regards,
Nate

-----Original Message-----
From: Laszlo Ersek <lersek@redhat.com>
Sent: Wednesday, March 10, 2021 8:17 AM
To: discuss@edk2.groups.io
Cc: cadenkline9@gmail.com; Desimone, Nathaniel L
<nathaniel.l.desimone@intel.com>
Subject: Re: [edk2-discuss] Google Summer of Code Interested Student

adding Nate

On 03/10/21 03:10, mailto:cadenkline9@gmail.com wrote:
Hello, My name is Caden Kline. I am a freshmen Computer Science major in
the US. I intend to specialize in Systems or Security or both. The main two
tasks I am hoping to apply for are "Terminal driver improvements" and
"Writing Unit Tests". However, I am primarily interested in any system level
work and willing to work on anything. I am concerned about the difficulty in
completing these tasks so I'm going to list my experience.

My relevant experience for C programming language is a one semester
introduction to C and Unix class I am currently taking. Outside of formal
experience, I have primarily interacted with C and assembly with capture the
flag/wargame binary exploitation challenges, and unfinished projects such as
a chip8 emulator. My primary programming experience is Java and Python
thanks to my high school and college classes. I have participated in several
past google code-ins. My github profile is https://github.com/Pokemod97 .

Is there anything I can do to improve my chances to be selected or any
other feedback? Thank you for taking the time to read this message.








Re: Redfish Host Interface

Laszlo Ersek
 

Hi Russell,

On 03/11/21 22:02, Russell Peterson wrote:
Hello,

I am interested in a UEFI Redfish Host Interface that does not require an OS. That is, the Redfish service would be provided by UEFI itself (via an IP interface)... or perhaps an EFI application.
For example, if a BMC wanted to access EFI variables directly from UEFI via an IP interface with no functional OS present.

Is this crazy for me to think this? Already exists? Under development? An idea... but I would need to do some work?
At least the following TianoCore bugzilla
<https://bugzilla.tianocore.org/> tickets relate to RedFish, one way or
another:

2337
2906
2910
2911
2912
2913
2918
2919
2930
2931
2932
2933
2934
2936
3102
3173
3174

At least the following USWG Mantis tickets relate to RedFish:

0001221
0001834
0001853
0001920
0001925
0001935
0001941
0002000
0002009
0002172

In UEFI v2.8B, there is a chapter called "31 - EFI Redfish Service Support".

A top-level RedfishPkg exists in edk2, and it seems like EmulatorPkg has
received some enablement. Not sure about the state in edk2-platforms (or
in other out-of-tree platforms).

Adding Abner and Nickle to the CC list (per "Maintainers.txt");
hopefully they can summarize the status for you.

Thanks
Laszlo


Redfish Host Interface

Russell Peterson
 

Hello,

I am interested in a UEFI Redfish Host Interface that does not require an OS. That is, the Redfish service would be provided by UEFI itself (via an IP interface)... or perhaps an EFI application.
For example, if a BMC wanted to access EFI variables directly from UEFI via an IP interface with no functional OS present.

Is this crazy for me to think this? Already exists? Under development? An idea... but I would need to do some work?

Any advice much appreciated.

Regards,

Russell

181 - 200 of 808