From: "Kilian Kegel" <KILIAN_KEGEL@OUTLOOK.COM>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Maciej Rabeda <maciej.rabeda@linux.intel.com>
Cc: "Rabeda, Maciej" <maciej.rabeda@linux.intel.com>,
Rebecca Cran <rebecca@nuviainc.com>,
"tim.lewis@insyde.com" <tim.lewis@insyde.com>,
Mike Kinney <michael.d.kinney@intel.com>,
"afish@apple.com" <afish@apple.com>,
Leif Lindholm <leif@nuviainc.com>,
Michael Kubacki <Michael.Kubacki@microsoft.com>,
"abner.chang@hpe.com" <abner.chang@hpe.com>
Subject: CdePkgBlog 2022-01-16 -- Introduction of the ACPICA port to UEFI
Date: Sun, 16 Jan 2022 20:01:30 +0000 [thread overview]
Message-ID: <AM8P190MB0945420998C742947DFD6559EB569@AM8P190MB0945.EURP190.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <AM8P190MB09459D00D0D45C80CDB2D746EB7A9@AM8P190MB0945.EURP190.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 2094 bytes --]
Hi Andrew, hi Jordan, hi Maciej, hi all,
this task was suggested by @ajfish and @jljusten at tianocore / tianocore.github.io:
https://github.com/tianocore/tianocore.github.io/wiki/Tasks#port-acpi-ca-to-a-shell-application.
All in all it could be solved within a really small amount of time, with a small amount of changes and extensions some months ago
* build Visual-ACPICA-for-UEFI-Shell: https://www.youtube.com/watch?v=POfSJQXi2aM
* run ACPIDUMP.efi and ASLCOMPILER.efi: https://www.youtube.com/watch?v=oA1GA95WrF0
My concept here was to choose the existing Microsoft VisualStudio package and
adjust it to run in the UEFI environment, by reimplementing missing Win32-API functions (amount of 8).
This could be done using the Microsoft-C-Library compatible toro-C-Library<https://github.com/KilianKegel/toro-C-Library#toro-c-library-formerly-known-as-torito-c-library>
Maybe that concept is also useable for porting “openSSH” to UEFI Shell: https://github.com/tianocore/tianocore.github.io/wiki/Tasks#port-openssh-as-a-shell-application
@Maciej Rabeda<mailto:maciej.rabeda@linux.intel.com>
The toro-C-Library source code is included in the project.
You can check what is inside, how it works internally and how I do believe a
C-Library for UEFI Shell/SMM/DXE/PEI should be constructed that guarantees
compatibility/portability+testability for POST drivers and UEFI/Windows Shell applications by design.
The “toro-C-Library” build engine is VisualStudio/msbuild.exe only. It takes 20 Seconds to get it done.
The older “torito-C-Library” build engine is EDK2Build. It takes 120 seconds to get it done, for the same result,
on the same build machine.
If you want to build the samples, please get the entire CdePkg from edk2-staging that also includes the blog,
https://github.com/tianocore/edk2-staging/tree/CdePkg
If you just want to read the new blog:
https://github.com/tianocore/edk2-staging/blob/CdePkg/blogs/2022-01-16/README.md#cdepkgblog-2022-01-16
Enjoy the breathtaking speed and elegance of VisualStudio
Have fun,
Kilian
[-- Attachment #2: Type: text/html, Size: 9491 bytes --]
next prev parent reply other threads:[~2022-01-16 20:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 15:48 "StdLibPkg" branch on edk2-staging Maciej Rabeda
2021-07-28 15:34 ` [edk2-devel] " Rebecca Cran
2021-07-28 15:45 ` Maciej Rabeda
2021-07-28 15:59 ` Rebecca Cran
2021-07-28 22:25 ` Tim Lewis
2021-07-28 22:44 ` Rebecca Cran
2021-08-04 11:03 ` Leif Lindholm
2021-08-05 3:35 ` Andrew Fish
2021-08-05 4:14 ` Kilian Kegel
[not found] ` <16984DDFBF70DC40.16396@groups.io>
2021-08-11 13:19 ` Kilian Kegel
2021-11-14 19:51 ` CdePkgBlog 2021-11-14 Kilian Kegel
2021-11-22 16:31 ` [edk2-devel] " Maciej Rabeda
2021-11-24 20:21 ` Kilian Kegel
2021-11-24 22:50 ` Pedro Falcato
2021-11-28 20:35 ` CdePkgBlog 2021-11-18 Kilian Kegel
[not found] ` <16BBD01DEB5EF921.4083@groups.io>
2021-12-12 20:02 ` CdePkgBlog 2021-12-12 Kilian Kegel
2021-12-19 20:51 ` CdePkgBlog 2021-12-19 Kilian Kegel
2022-01-16 20:01 ` Kilian Kegel [this message]
2021-11-30 10:09 ` [edk2-devel] CdePkgBlog 2021-11-14 Maciej Rabeda
[not found] ` <16BC4B25BB307B73.14741@groups.io>
2021-11-30 20:15 ` Maciej Rabeda
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=AM8P190MB0945420998C742947DFD6559EB569@AM8P190MB0945.EURP190.PROD.OUTLOOK.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