Andrei Warkentin
Andrei Warkentin
- Allocate pool of type BootServiceCode - Copy code into pool allocation - Run copied code - ??? - Profit! (when https://github.com/intel/MultiArchUefiPkg/issues/5 is fixed)
Today the test is x64 only.
A backtrace of the emulated code would be immensely helpful. Yes, this won't work well if we're running code with a frame pointer, but it's better than nothing,
…re missing the RFC2119 keywords to indicate whether they are mandatory or optional."
Similar to https://github.com/riscv-non-isa/riscv-server-platform/blob/main/riscv-server-platform-ts.pdf
Seems straight forward enough. It's basically informative. If we are expecting to do driver probing matches on this, we probably want more rigor. _Originally posted by @adurbin-rivos in https://github.com/riscv-non-isa/riscv-brs/issues/148#issuecomment-2059857633_
As a continuation of https://github.com/riscv-non-isa/riscv-brs/issues/82: - ~~Require` authenticated variables to only be modifiable in-band (via the RT interface), no direct access from OS to hardware~~ (EDIT: this is already in...
Also need to add the rscv- Known Device Property Prefixex _Originally posted by @andreiw in https://github.com/riscv-non-isa/riscv-brs/issues/24#issuecomment-2057685015_ Do this by following the directions in https://github.com/UEFI/DSD-Guide/blob/main/dsd-guide.adoc: The add a prefix to this...
Looks good to me. Thanks a lot for taking care of this. Now, this spec being moved to BRS, an ECR to SMBIOS spec required to update the link it...
Current language for BRS-I mentions firmware-first (APEI) handling. We need to close on whether that's really doable for v1 of the BRS or whether we should just remove any requirement...