From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Sami Mujawar <Sami.Mujawar@arm.com>
Cc: Pierre Gondois <Pierre.Gondois@arm.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
edk2-devel-groups-io <devel@edk2.groups.io>,
"Feng, Bob C" <bob.c.feng@intel.com>,
"Gao, Liming" <liming.gao@intel.com>, nd <nd@arm.com>,
Matteo Carlini <Matteo.Carlini@arm.com>,
Laura Moretta <Laura.Moretta@arm.com>
Subject: Re: [edk2-devel] [PATCH v1 1/1] BaseTools: Build ASL files before C files
Date: Mon, 23 Dec 2019 17:09:59 +0100 [thread overview]
Message-ID: <CAKv+Gu8ZyEJkceivrPc6AD3sKcoqkVcfK6sOu32faEGJ9y_94Q@mail.gmail.com> (raw)
In-Reply-To: <DB6PR0802MB2375333EC30BDE02342413CF84520@DB6PR0802MB2375.eurprd08.prod.outlook.com>
On Thu, 19 Dec 2019 at 19:15, Sami Mujawar <Sami.Mujawar@arm.com> wrote:
>
> Hi Ard,
>
> This is required for loading the AML blob in memory so that we can parse and fixup tables.
>
> However, I understand your concern regarding dependency/relying on asl compilers for the .hex file.
> The .hex file can be easily generated by a post-processing python script (20-30 lines of code) that reads the AML file and dumps the blob in a C array.
> If preferred, we can post a patch that adds this support so that we don’t have to rely on intermediate outputs of asl compilers.
>
> Alternatively, we would be grateful if you can any suggest another option.
>
So this is for making changes at runtime, right? And are you only
using the char[] array in its entirety?
You could look at SynQuacer or Overdrive platforms: those also load
SSDT tables from FFS sections at runtime.
next prev parent reply other threads:[~2019-12-23 16:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 13:50 [PATCH v1 1/1] BaseTools: Build ASL files before C files PierreGondois
2019-10-30 13:52 ` [edk2-devel] " PierreGondois
2019-10-31 0:41 ` Liming Gao
2019-10-31 11:12 ` PierreGondois
2019-11-04 7:49 ` Bob Feng
2019-11-04 10:32 ` PierreGondois
2019-11-12 13:33 ` PierreGondois
2019-11-13 1:15 ` Liming Gao
2019-11-13 1:40 ` Bob Feng
2019-11-15 16:27 ` PierreGondois
2019-12-04 17:32 ` PierreGondois
2019-12-11 11:23 ` PierreGondois
2019-12-12 9:14 ` Bob Feng
2019-12-16 0:33 ` PierreGondois
2019-12-17 11:41 ` Bob Feng
2019-12-18 10:43 ` PierreGondois
2019-12-18 17:50 ` Ard Biesheuvel
2019-12-19 11:18 ` PierreGondois
2019-12-19 16:58 ` Ard Biesheuvel
2019-12-19 18:15 ` Sami Mujawar
2019-12-23 16:09 ` Ard Biesheuvel [this message]
2019-12-24 16:47 ` PierreGondois
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=CAKv+Gu8ZyEJkceivrPc6AD3sKcoqkVcfK6sOu32faEGJ9y_94Q@mail.gmail.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