|
[edk2-devel] [edk2-rfc] [RFC] code-first process for UEFI-forum specifications
Leif, A few comments included below. Thanks, Mike
Leif, A few comments included below. Thanks, Mike
|
By
Michael D Kinney
·
|
|
[edk2-devel] [RFC] BZ 2298 MdePkg/DevicePathLib merger or not
I agree -- I expect that most if not all platform DSC files will need updates. That's because the most frugal approach for a platform is to use the self-contained UefiDevicePathLib instance only in ve
I agree -- I expect that most if not all platform DSC files will need updates. That's because the most frugal approach for a platform is to use the self-contained UefiDevicePathLib instance only in ve
|
By
Laszlo Ersek
·
|
|
[RFC] BZ 2298 MdePkg/DevicePathLib merger or not 4 messages
HI all, REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2298 In the MdePkg, there are two folder for the DevicePathLib: 1. MdePkg\Library\UefiDevicePathLib 2. MdePkg\Library\UefiDevicePathLibDevic
HI all, REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2298 In the MdePkg, there are two folder for the DevicePathLib: 1. MdePkg\Library\UefiDevicePathLib 2. MdePkg\Library\UefiDevicePathLibDevic
|
By
Gao, Zhichao
·
|
|
Unified API for Hashing Algorithms in EDK2 17 messages
Hello, Currently the UEFI drivers using the SHA/SM3 hashing algorithms use hard-coded API to calculate the hash, such as, sha_256(...), etc. Since SHA384 and/or SM3 are being increasingly adopted, it
Hello, Currently the UEFI drivers using the SHA/SM3 hashing algorithms use hard-coded API to calculate the hash, such as, sha_256(...), etc. Since SHA384 and/or SM3 are being increasingly adopted, it
|
By
Sukerkar, Amol N
·
|
|
[EXTERNAL] Re: [edk2-devel] EDK2 Host-Based Unit Test RFC (Now with docs!) 11 messages
Andrew, I agree with your points. Mike, You’ve got a lot more there. Let me take a look and update the draft. I’ll ping back ASAP. - Bret Sent: Wednesday, December 4, 2019 9:50 AM To: devel@edk2.group
Andrew, I agree with your points. Mike, You’ve got a lot more there. Let me take a look and update the draft. I’ll ping back ASAP. - Bret Sent: Wednesday, December 4, 2019 9:50 AM To: devel@edk2.group
|
By
Bret Barkelew
·
|
|
[edk2-devel] EDK2 Host-Based Unit Test RFC (Now with docs!)
Mike, I like and agree with your comments. On the UnitTestPkg(s) dependency issue I think it would make sense to move as much as possible into the *Pkg/Test/ ( *Pkg/HostLibrary, MdePkg/MdePkgTest.dsc,
Mike, I like and agree with your comments. On the UnitTestPkg(s) dependency issue I think it would make sense to move as much as possible into the *Pkg/Test/ ( *Pkg/HostLibrary, MdePkg/MdePkgTest.dsc,
|
By
Andrew Fish
·
|
|
EDK2 Host-Based Unit Test RFC (Now with docs!)
Hi Bret, Thanks for posting this content. Host based unit testing is a very valuable addition to the CI checks. I have the following comments: 1. I see that MdePkg adds a dependency on UnitTestPkg. Th
Hi Bret, Thanks for posting this content. Host based unit testing is a very valuable addition to the CI checks. I have the following comments: 1. I see that MdePkg adds a dependency on UnitTestPkg. Th
|
By
Michael D Kinney
·
|
|
[edk2-devel] EDK II Stable Tag edk2-stable201911 will be created based on commit bd85bf54c268204c7a698a96f3ccd96cd77952cd
No objection from me. Thank you for managing the SFF / HFF process, and the release, again, Liming! Laszlo
No objection from me. Thank you for managing the SFF / HFF process, and the release, again, Liming! Laszlo
|
By
Laszlo Ersek
·
|
|
EDK II Stable Tag edk2-stable201911 will be created based on commit bd85bf54c268204c7a698a96f3ccd96cd77952cd
Hi, all Today, I review all patches in edk2 mail list. There is no patches for EDK II Stable Tag edk2-stable201911. Based on edk2-stable201911 tag planning, it will be released at 2019-11-29. So, I pl
Hi, all Today, I review all patches in edk2 mail list. There is no patches for EDK II Stable Tag edk2-stable201911. Based on edk2-stable201911 tag planning, it will be released at 2019-11-29. So, I pl
|
By
Liming Gao
·
|
|
[edk2-devel] [Qemu-devel] [PATCH 1/2] q35: implement 128K SMRAM at default SMBASE address 11 messages
"Laszlo Ersek" <lersek@...> wrote: [...] If I recall correctly, CPU consumes 64K of save/restore area. The rest 64K are temporary RAM for using in SMI relocation handler, if it's possible to get away
"Laszlo Ersek" <lersek@...> wrote: [...] If I recall correctly, CPU consumes 64K of save/restore area. The rest 64K are temporary RAM for using in SMI relocation handler, if it's possible to get away
|
By
Igor Mammedov
·
|
|
[edk2-devel] [RFC] EDK II Continuous Integration Phase 1 7 messages
Hi Sean, Which OS/Compiler configurations are currently enabled for the Code Compilation Test? I have been working on enabling multiple OS/Compiler configurations in Azure Pipelines. There are some to
Hi Sean, Which OS/Compiler configurations are currently enabled for the Code Compilation Test? I have been working on enabling multiple OS/Compiler configurations in Azure Pipelines. There are some to
|
By
Michael D Kinney
·
|
|
[edk2-devel] [RFC] EDK II Continuous Integration Phase 1
Hi Sean, This looks really good and I agree we can combine the RFCs and enable more pre-commits tests. Additional responses below. Mike
Hi Sean, This looks really good and I agree we can combine the RFCs and enable more pre-commits tests. Additional responses below. Mike
|
By
Michael D Kinney
·
|
|
[edk2-devel] [RFC] EDK II Continuous Integration Phase 1 9 messages
Yes. The maintainer will prepare a local branch that is rebased to master, and has all the mailing list feedback tags (Reviewed-by, etc) applied. The maintainer also does all the local testing that th
Yes. The maintainer will prepare a local branch that is rebased to master, and has all the mailing list feedback tags (Reviewed-by, etc) applied. The maintainer also does all the local testing that th
|
By
Laszlo Ersek
·
|
|
[RFC] EDK II Continuous Integration Phase 1 5 messages
Hello, This is a proposal for a first step towards continuous integration for all TianoCore repositories to help improve to quality of commits and automate testing and release processes for all EDK II
Hello, This is a proposal for a first step towards continuous integration for all TianoCore repositories to help improve to quality of commits and automate testing and release processes for all EDK II
|
By
Michael D Kinney
·
|
|
[Qemu-devel] [PATCH 1/2] q35: implement 128K SMRAM at default SMBASE address
Hi Igor, (+Brijesh) long-ish pondering ahead, with a question at the end. I haven't written any OVMF code for this yet, but I've spent a few hours thinking about it. Progress! :) So, this looks really
Hi Igor, (+Brijesh) long-ish pondering ahead, with a question at the end. I haven't written any OVMF code for this yet, but I've spent a few hours thinking about it. Progress! :) So, this looks really
|
By
Laszlo Ersek
·
|
|
[edk2-devel] [RFC] EDK II Continuous Integration Phase 1 3 messages
In that wiki page, it says: "To work with this branch and run tests immediately, all you need to do is: |pip install --upgrade -r requirements.txt stuart_setup -c .\CISettings.py stuart_update -c .\CI
In that wiki page, it says: "To work with this branch and run tests immediately, all you need to do is: |pip install --upgrade -r requirements.txt stuart_setup -c .\CISettings.py stuart_update -c .\CI
|
By
rebecca@...
·
|
|
[edk2-devel] [PATCH] q35: lpc: allow to lock down 128K RAM at default SMBASE address
"Laszlo Ersek" <lersek@...> wrote: If we don't have to 'park' hotplugged CPUs, then I don't see a need for an extra controller. Thanks for the tip! ... patches with a stolen register are on the way to
"Laszlo Ersek" <lersek@...> wrote: If we don't have to 'park' hotplugged CPUs, then I don't see a need for an extra controller. Thanks for the tip! ... patches with a stolen register are on the way to
|
By
Igor Mammedov
·
|
|
[PATCH 2/2] tests: q35: MCH: add default SMBASE SMRAM lock test
test lockable SMRAM at default SMBASE feature introduced by commit "q35: implement 128K SMRAM at default SMBASE address" Signed-off-by: Igor Mammedov <imammedo@...> --- tests/q35-test.c | 105 ++++++++
test lockable SMRAM at default SMBASE feature introduced by commit "q35: implement 128K SMRAM at default SMBASE address" Signed-off-by: Igor Mammedov <imammedo@...> --- tests/q35-test.c | 105 ++++++++
|
By
Igor Mammedov
·
|
|
[PATCH 1/2] q35: implement 128K SMRAM at default SMBASE address
Use commit (2f295167e0 q35/mch: implement extended TSEG sizes) for inspiration and (ab)use reserved register in config space at 0x9c offset [*] to extend q35 pci-host with ability to use 128K at 0x300
Use commit (2f295167e0 q35/mch: implement extended TSEG sizes) for inspiration and (ab)use reserved register in config space at 0x9c offset [*] to extend q35 pci-host with ability to use 128K at 0x300
|
By
Igor Mammedov
·
|
|
[PATCH 0/2] q35: mch: allow to lock down 128K RAM at default SMBASE address
Try #2 using PCI config space of MCH to negotiate/lock SMRAM at 0x30000. CC: yingwen.chen@... CC: devel@edk2.groups.io CC: phillip.goerl@... CC: alex.williamson@... CC: jiewen.yao@... CC: jun.nakajima
Try #2 using PCI config space of MCH to negotiate/lock SMRAM at 0x30000. CC: yingwen.chen@... CC: devel@edk2.groups.io CC: phillip.goerl@... CC: alex.williamson@... CC: jiewen.yao@... CC: jun.nakajima
|
By
Igor Mammedov
·
|