linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Ondrej Jirman <megous@megous.com>
Subject: Re: Current mainline brcmfmac reports error on supposedly supported ap6256 chip
Date: Mon, 26 Jul 2021 14:31:22 +0200	[thread overview]
Message-ID: <7365182a-ab99-899b-7ac9-c13b31e02f06@broadcom.com> (raw)
In-Reply-To: <A76C51D0-C73B-43B0-9AE3-ABB4AED6AB86@gmail.com>

On 7/26/2021 2:21 PM, Piotr Oniszczuk wrote:
> Arend,
> 
> Neil Armstrong hinted me issue might be related to usage of memcpy() to/from an iomem mapping.
> arm64 memcpy update (285133040e6c ("arm64: Import latest memcpy()/memmove() implementation")) triggers a memory abort when dram-access-quirk
> is used on the G12A/G12B platforms.
> 
> I reverted https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mmc/host/meson-gx-mmc.c?h=v5.13.4&id=103a5348c22c3fca8b96c735a9e353b8a0801842
> 
> and got nicely working wifi.
> 
> So it looks root cause is amlogic specific - not brcmfmac.
> 
> Sorry for false report and many many thx for Your head-up!

Hi Piotr,

Thanks for letting me know. I hadn't worked yet on the patch I had in 
mind and I suspect it would not have helped.

Regards,
Arend

  reply	other threads:[~2021-07-26 12:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CB0AA0D2-A8F3-4217-A3C1-E14D7E9FF11E@gmail.com>
     [not found] ` <17ad94781a0.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
     [not found]   ` <6F6333F3-0BDB-48AF-B445-723958ABA8C9@gmail.com>
     [not found]     ` <be6c2b7f-2c85-59fb-3013-d0590c487c51@broadcom.com>
     [not found]       ` <53E7119F-D158-4EF0-940C-D0AA59C23CF6@gmail.com>
2021-07-26  7:54         ` Current mainline brcmfmac reports error on supposedly supported ap6256 chip Arend van Spriel
     [not found]           ` <286E2774-FAA5-47E3-A1FC-FDB09EB37FDC@gmail.com>
2021-07-26  9:37             ` Arend van Spriel
2021-07-26  9:39               ` Arend van Spriel
2021-07-26 12:21                 ` Piotr Oniszczuk
2021-07-26 12:31                   ` Arend van Spriel [this message]
2021-07-26  9:53           ` Piotr Oniszczuk
2021-07-24 13:22 Piotr Oniszczuk

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-all 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=7365182a-ab99-899b-7ac9-c13b31e02f06@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=megous@megous.com \
    --cc=piotr.oniszczuk@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).