From: Hunter Laux <hunterlaux@gmail.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Olivier Louvignes <olivier@mgcrea.io>,
Paul Cercueil <paul@crapouillou.net>,
Paul Boddie <paul@boddie.org.uk>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Discussions about the Letux Kernel <letux-kernel@openphoenux.org>
Subject: Re: [PATCH] MIPS: ingenic: Work around stale L2 data after DMA on XBurst II
Date: Thu, 12 Nov 2026 09:19:20 -0700 [thread overview]
Message-ID: <179450036033.3574224.1997492818519568890@gmail.com> (raw)
In-Reply-To: <988F3625-C300-4C68-AC70-E371E5D9A496@goldelico.com>
Hi Nikolaus,
On Thu, Nov 12, 2026 at 11:24 +0100, H. Nikolaus Schaller wrote:
> - LX26 board with X2600 (isn't running stable for unknown reasons and
> sometimes damages the µSD contents but your
> patch didn't help to solve)
I don't know that the stale L2 data is behind your instability or µSD
problem. A quick way to rule it in or out, independent of the patch,
is to turn the prefetcher off (MSCR.DisPFB2):
devmem 0x12200060 32 $(( $(devmem 0x12200060) | 2 ))
With it off I saw no stale reads here.
> Maybe the individuals and teams working on the XBurst devices should
> coordinate somehow to avoid double work and potentially incompatible
> fragments?
Agreed. I'll follow up off-list with what I have for the X2600.
What I have working on my board is here, on top of v7.3.3:
https://github.com/jolting/linux/tree/ad5x-7.3.3-rc1
The patches I send upstream are cherry-picked from it.
I don't have any dev boards. My X2600 is in a Flashforge Adventurer 5X
3D printer, which is quite cheap, and its mainboard is also sold on its
own as a replacement part. A few of the printers make an X2600 test lab
that doubles as a print farm.
Hunter
prev parent reply other threads:[~2026-11-12 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 20:47 Hunter Laux
2026-11-12 10:24 ` H. Nikolaus Schaller
2026-11-12 16:19 ` Hunter Laux [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=179450036033.3574224.1997492818519568890@gmail.com \
--to=hunterlaux@gmail.com \
--cc=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=olivier@mgcrea.io \
--cc=paul@boddie.org.uk \
--cc=paul@crapouillou.net \
--cc=tsbogend@alpha.franken.de \
/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
all inboxes | Powered by JetHome®