public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: devel@edk2.groups.io
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>
Subject: Re: [edk2-devel] [PATCH edk2-non-osi 1/1] Qemu/Sbsa: update TF-A binaries to get needed SMC calls
Date: Thu, 14 Mar 2024 15:21:04 +0100	[thread overview]
Message-ID: <27c22689-a1b9-4d4f-9c34-64b711b2bb6c@linaro.org> (raw)
In-Reply-To: <17BCA7402EE479C0.22340@groups.io>

W dniu 14.03.2024 o 15:17, Marcin Juszkiewicz via groups.io pisze:
> We want to stop parsing DeviceTree (in EDK2) to gather hardware information.
> 
> Instead we ask TF-A for those details using SMC calls. On real hardware
> platform it could be asking on-board Embedded Controller.
> 
> Hardware information (CPU, Memory) is now in SbsaQemuHardwareInfoLib together
> with new code for handling SMC stuff. If TF-A answer to SMC call would be not
> success then we go back to parsing DeviceTree data directly. There is no DT
> parsing elsewhere.
> 
> This change brings TF-A with all changes needed for it.

Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>

I really need to enable it to be automatic...


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116753): https://edk2.groups.io/g/devel/message/116753
Mute This Topic: https://groups.io/mt/104927188/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



       reply	other threads:[~2024-03-14 14:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17BCA7402EE479C0.22340@groups.io>
2024-03-14 14:21 ` Marcin Juszkiewicz [this message]
2024-03-19 13:26   ` [edk2-devel] [PATCH edk2-non-osi 1/1] Qemu/Sbsa: update TF-A binaries to get needed SMC calls Ard Biesheuvel
2024-03-14 14:17 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=27c22689-a1b9-4d4f-9c34-64b711b2bb6c@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