From: "PierreGondois" <pierre.gondois@arm.com>
To: Rebecca Cran <rebecca@bsdio.com>, devel@edk2.groups.io
Cc: Thomas Abraham <thomas.abraham@arm.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Sami Mujawar <sami.mujawar@arm.com>,
Fabien Ficheau <fabien.ficheau@arm.com>
Subject: Re: [edk2-devel] [PATCH 1/1] Platform/ARM/JunoPkg: Don't setup PCIe root bridge for Juno-r0
Date: Fri, 14 Apr 2023 09:12:33 +0200 [thread overview]
Message-ID: <096ed77c-b39a-5277-d403-48944ba57fc4@arm.com> (raw)
In-Reply-To: <658b65fd-ea8b-bb91-c72a-5c0642623887@bsdio.com>
On 4/14/23 00:04, Rebecca Cran wrote:
> On 4/13/23 07:14, PierreGondois wrote:
>
>> diff --git a/Platform/ARM/JunoPkg/Library/JunoPciHostBridgeLib/XPressRich3.c b/Platform/ARM/JunoPkg/Library/JunoPciHostBridgeLib/XPressRich3.c
>> index 0755dc155616..583efd0efb16 100644
>> --- a/Platform/ARM/JunoPkg/Library/JunoPciHostBridgeLib/XPressRich3.c
>> +++ b/Platform/ARM/JunoPkg/Library/JunoPciHostBridgeLib/XPressRich3.c
>> @@ -69,6 +69,13 @@ HWPciRbInit (
>> UINTN TranslationTable;
>> EFI_CPU_IO2_PROTOCOL *CpuIo;
>> EFI_STATUS Status;
>> + UINT32 JunoRevision;
>> +
>> + GetJunoRevision (JunoRevision);
>> + DEBUG ((DEBUG_ERROR, "Juno rev=%d\n", JunoRevision));
>
> Should that be DEBUG_INFO? Or is it DEBUG_ERROR because of the value of
> PcdDebugPrintErrorLevel which doesn't include INFO messages?
>
> I was just wondering a few days ago whether it should be 0x8000004F
> instead of 0x8000000F?
>
The DEBUG message is not necessary, I will remove it.
PcdDebugPrintErrorLevel effectively doesn't include INFO messages,
I assume this is ok not to have them even in the DEBUG build.
Regards,
Pierre
prev parent reply other threads:[~2023-04-14 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 13:14 [PATCH 1/1] Platform/ARM/JunoPkg: Don't setup PCIe root bridge for Juno-r0 PierreGondois
2023-04-13 16:04 ` Sami Mujawar
2023-04-13 22:04 ` [edk2-devel] " Rebecca Cran
2023-04-14 7:12 ` PierreGondois [this message]
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=096ed77c-b39a-5277-d403-48944ba57fc4@arm.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