From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: devel@edk2.groups.io
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Rebecca Cran <rebecca@bsdio.com>,
Pedro Falcato <pedro.falcato@gmail.com>
Subject: Re: [edk2-devel] [PATCH v4] add ArmCpuInfo EFI application
Date: Fri, 7 Apr 2023 17:11:02 +0200 [thread overview]
Message-ID: <62c5c936-a108-0a10-d1ab-9db9dd71a6ee@linaro.org> (raw)
In-Reply-To: <1753ABF1A296B040.11304@groups.io>
W dniu 7.04.2023 o 16:02, Marcin Juszkiewicz via groups.io pisze:
> +++ b/ArmPkg/Application/ArmCpuInfo/readregs.S
> @@ -0,0 +1,41 @@
> +#include <AsmMacroIoLibV8.h>
> +
> +ASM_FUNC(ReadAa64Pfr0El1)
> + mrs x0, ID_AA64PFR0_EL1
> + ret
> +
> +ASM_FUNC(ReadAa64Pfr1El1)
> + mrs x0, ID_AA64PFR1_EL1
> + ret
> +
> +ASM_FUNC(ReadAa64Dfr0El1)
> + mrs x0, ID_AA64DFR0_EL1
> + ret
> +
> +ASM_FUNC(ReadAa64Dfr1El1)
> + mrs x0, ID_AA64DFR1_EL1
> + ret
> +
> +ASM_FUNC(ReadAa64Isar0El1)
> + mrs x0, ID_AA64ISAR0_EL1
> + ret
> +
> +ASM_FUNC(ReadAa64Isar1El1)
> + mrs x0, ID_AA64ISAR1_EL1
> + ret
> +
> +ASM_FUNC(ReadAa64Isar2El1)
> + mrs x0, ID_AA64ISAR2_EL1
> + ret
> +
> +ASM_FUNC(ReadAa64Mmfr0El1)
> + mrs x0, ID_AA64MMFR0_EL1
> + ret
> +
> +ASM_FUNC(ReadAa64Mmfr1El1)
> + mrs x0, ID_AA64MMFR1_EL1
> + ret
> +
> +ASM_FUNC(ReadAa64Mmfr2El1)
> + mrs x0, ID_AA64MMFR2_EL1
> + ret
Those functions probably should be moved to
ArmPkg/Library/ArmLib/AArch64/ code. But I do not understand EDK2
buildbuildsystem enough to sort that part out.
next prev parent reply other threads:[~2023-04-07 15:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 18:02 [PATCH] add ArmCpuInfo EFI application Marcin Juszkiewicz
2023-04-06 21:05 ` [edk2-devel] " Rebecca Cran
2023-04-07 10:39 ` [PATCH v2] " Marcin Juszkiewicz
2023-04-07 10:55 ` [edk2-devel] " Ard Biesheuvel
2023-04-07 12:46 ` Marcin Juszkiewicz
2023-04-07 13:07 ` Ard Biesheuvel
2023-04-07 12:47 ` [PATCH v3] " Marcin Juszkiewicz
2023-04-07 13:02 ` [edk2-devel] " Pedro Falcato
2023-04-07 13:05 ` Pedro Falcato
2023-04-07 13:29 ` Marcin Juszkiewicz
2023-04-07 13:40 ` Pedro Falcato
2023-04-07 13:41 ` Pedro Falcato
2023-04-07 13:42 ` Marcin Juszkiewicz
2023-04-07 14:02 ` [PATCH v4] " Marcin Juszkiewicz
[not found] ` <1753ABF1A296B040.11304@groups.io>
2023-04-07 15:11 ` Marcin Juszkiewicz [this message]
2023-04-07 15:29 ` [PATCH v5 0/2] add ArmCpuInfo application Marcin Juszkiewicz
2023-04-07 15:29 ` [PATCH v5 1/2] ArmLib: add functions to read system registers Marcin Juszkiewicz
2023-04-20 10:54 ` Leif Lindholm
2023-04-07 15:29 ` [PATCH v5 2/2] add ArmCpuInfo EFI application Marcin Juszkiewicz
2023-04-20 12:43 ` Leif Lindholm
2023-04-20 14:42 ` [edk2-devel] " Marcin Juszkiewicz
2023-04-20 14:44 ` [PATCH v6 1/2] ArmLib: add functions to read system registers Marcin Juszkiewicz
2023-04-20 14:44 ` [PATCH v6 2/2] add ArmCpuInfo EFI application Marcin Juszkiewicz
2023-04-20 17:29 ` Leif Lindholm
2023-04-21 14:37 ` [edk2-devel] " Rebecca Cran
2023-04-21 14:59 ` Marcin Juszkiewicz
2023-04-21 15:15 ` Rebecca Cran
2023-04-21 15:51 ` [PATCH v7 1/2] ArmLib: add functions to read system registers Marcin Juszkiewicz
2023-04-21 15:51 ` [PATCH v7 2/2] add ArmCpuInfo EFI application Marcin Juszkiewicz
2023-04-21 20:18 ` Leif Lindholm
2023-04-21 16:33 ` [edk2-devel] [PATCH v6 " Leif Lindholm
2023-04-13 9:31 ` [PATCH v5 0/2] add ArmCpuInfo application 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=62c5c936-a108-0a10-d1ab-9db9dd71a6ee@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