From: "Ard Biesheuvel" <ardb@kernel.org>
To: Jeremy Linton <jeremy.linton@arm.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Peter Batard <pete@akeo.ie>,
Samer El-Haj-Mahmoud <samer.el-haj-mahmoud@arm.com>,
Andrei Warkentin <awarkentin@vmware.com>,
Jared McNeill <jmcneill@invisible.ca>
Subject: Re: [PATCH v2 2/2] Platform/RaspberryPi: Increase genet dma window
Date: Wed, 12 May 2021 14:44:42 +0200 [thread overview]
Message-ID: <CAMj1kXEdh6tp28JM-5w5GWx3-Vr28iNOUoMVmKEpOYgG2OzFQg@mail.gmail.com> (raw)
In-Reply-To: <20210511223734.864455-3-jeremy.linton@arm.com>
On Wed, 12 May 2021 at 00:37, Jeremy Linton <jeremy.linton@arm.com> wrote:
>
> The genet is capable of addressing the entire memory space
> on the RPI4. Lets allow it to dma into those regions.
> This solves intermittent issues with grub/etc being able
> to communicate when the 3G limit is lifted on 8G boards.
>
> Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
> Reviewed-by: Jared McNeill <jmcneill@invisible.ca>
> ---
> Platform/RaspberryPi/RPi4/RPi4.dsc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Platform/RaspberryPi/RPi4/RPi4.dsc b/Platform/RaspberryPi/RPi4/RPi4.dsc
> index 5c6783eae7..cf796acf6a 100644
> --- a/Platform/RaspberryPi/RPi4/RPi4.dsc
> +++ b/Platform/RaspberryPi/RPi4/RPi4.dsc
> @@ -717,7 +717,7 @@
> Silicon/Broadcom/Drivers/Net/BcmGenetDxe/BcmGenetDxe.inf {
> <PcdsFixedAtBuild>
> gEmbeddedTokenSpaceGuid.PcdDmaDeviceOffset|0x00000000
> - gEmbeddedTokenSpaceGuid.PcdDmaDeviceLimit|0xffffffff
> + gEmbeddedTokenSpaceGuid.PcdDmaDeviceLimit|0xffffffffff
> }
>
> #
> --
> 2.13.7
>
As I said before, I am fine with this patch, but I would still like to
understand why this causes a failure. The device limit is used by the
DMA layer to decide whether bounce buffering is needed or not, but the
API should work as expected either way, with perhaps only an impact on
performance if bounce buffering is done unnecessarily.
What kind of errors are you seeing (and fixing) with this change?
next prev parent reply other threads:[~2021-05-12 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 22:37 [PATCH v2 0/2] rpi: Fix PXE issues with grub Jeremy Linton
2021-05-11 22:37 ` [PATCH v2 1/2] Silicon/Broadcom/BcmGenetDxe: Delay for linkup in transmit Jeremy Linton
2021-05-11 22:37 ` [PATCH v2 2/2] Platform/RaspberryPi: Increase genet dma window Jeremy Linton
2021-05-12 12:44 ` Ard Biesheuvel [this message]
2021-08-16 7:23 ` [PATCH v2 0/2] rpi: Fix PXE issues with grub Ard Biesheuvel
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=CAMj1kXEdh6tp28JM-5w5GWx3-Vr28iNOUoMVmKEpOYgG2OzFQg@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