From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: devel@edk2.groups.io
Cc: Sami Mujawar <sami.mujawar@arm.com>, Evan Lloyd <evan.lloyd@arm.com>
Subject: Re: [edk2-devel] ACPI table generators and ConfigurationManagerProtocol
Date: Fri, 12 Apr 2024 14:43:09 +0200 [thread overview]
Message-ID: <bc05c086-c6b8-48ae-a88e-8e5ced1944b0@linaro.org> (raw)
In-Reply-To: <178C31CFE9B284CD.5378@groups.io>
W dniu 8.10.2023 o 19:25, Marcin Juszkiewicz via groups.io pisze:
I hate replying to myself after half a year of not seeing any answer. So
added some people from repo to Cc:
> Can someone point me to documentation on how to use ACPI table
> generators and ConfigurationManagerProtocol?
https://github.com/tianocore/edk2/blob/master/DynamicTablesPkg/Readme.md
tells the story and points to presentation from 2018 with some pictures
in it.
Looks like the only documentation is the code itself. Is checkout of
some old tree and looking change by change how it was done on some
platform the easiest way to find out how to use it?
> And tell which of platforms is a good example of using those?
Juno, FVP, Morello, N1SDP, one NXP platform and ArmVirt use them.
Probably the last one would be best to look at but who knows...
> From first look it seems like using ACPI table generators may allow
> to simplify code by not creating tables by hand (or in ASL). I would
> like to do some changes around SBSA Reference Platform without
> rewriting ASL into C again.
In meantime I rewrote some ASL into C. Again. Now need a way to generate
DSDT for PCIe buses. Can write something in C again. But do I really
need to?
> I am aware that moving platform to use configuration manager may
> require even more work.
The more I look at */ConfigurationManager.[ch] the more I do not like
the amount of static structures there. All those
EDKII_PLATFORM_REPOSITORY_INFO covering 1000 lines looks like "how the
hell I will find what to change in other piece of code".
Any doc pointers? Recommendations (other than "change your job")?
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#117666): https://edk2.groups.io/g/devel/message/117666
Mute This Topic: https://groups.io/mt/105481311/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next parent reply other threads:[~2024-04-12 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <178C31CFE9B284CD.5378@groups.io>
2024-04-12 12:43 ` Marcin Juszkiewicz [this message]
2024-04-12 14:08 ` [edk2-devel] ACPI table generators and ConfigurationManagerProtocol Gerd Hoffmann
[not found] ` <17C588EF15E93250.19773@groups.io>
2024-04-16 7:38 ` Marcin Juszkiewicz
[not found] ` <17C6B2A6AFC6832B.12347@groups.io>
2024-04-16 9:02 ` Marcin Juszkiewicz
2023-10-08 17:25 Marcin Juszkiewicz
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=bc05c086-c6b8-48ae-a88e-8e5ced1944b0@linaro.org \
--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