From: Dominique Martinet <asmadeus@codewreck.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Tom Psyborg <pozega.tomislav@gmail.com>,
linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com,
Ellie Revves <ellierevves@gmail.com>
Subject: Re: ath9k driver may be broken on ARM64 ?
Date: Fri, 26 Oct 2018 07:11:49 +0200 [thread overview]
Message-ID: <20181026051149.GA20592@nautica> (raw)
In-Reply-To: <20181025062758.GA24209@nautica>
Dominique Martinet wrote on Thu, Oct 25, 2018:
> What I find surprising is that the mapping for sc->mem is done (as shown
> in the kernel page table dump), and some REG_WRITE worked before, but
> the first REG_READ fails despite being an aligned address so something
> is odd with how the memory is setup?
>
>
> I think it would be interesting to add some debug statement early in
> init (pci init to check how the memory is setup, if I'm not wrong about
> it being pci, and along the path I described earlier) ; but my free time
> ended long ago so don't think I'll be of much more use from now :p
(not sure if you got notified off list, but fwiw the bug is apparently
resolved by upgrading to a newer release of u-boot - same version, from
u-boot 2017.03 armada v17.06 to u-boot 2017.03 armada v17.10
I have no idea what they're doing in u-boot with the memory setup but I
guess the case is closed...)
--
Asmadeus | Dominique Martinet
prev parent reply other threads:[~2018-10-26 5:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 5:13 ath9k driver may be broken on ARM64 ? Ellie Revves
2018-10-24 12:09 ` Tom Psyborg
2018-10-24 18:39 ` Ellie Revves
2018-10-24 19:13 ` Ellie Revves
2018-10-24 22:53 ` Tom Psyborg
2018-10-24 23:05 ` Ellie Revves
2018-10-24 23:18 ` Tom Psyborg
2018-10-25 4:26 ` Ellie Revves
2018-10-25 6:27 ` Dominique Martinet
2018-10-26 5:11 ` Dominique Martinet [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-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=20181026051149.GA20592@nautica \
--to=asmadeus@codewreck.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=ellierevves@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pozega.tomislav@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