From: Waldemar Brodkorb <wbx@openadk.org>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Waldemar Brodkorb <wbx@openadk.org>,
Rong Zhang <rongrong@oss.cipunited.com>,
Jonas Gorski <jonas.gorski@gmail.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
Rong Zhang <i@rong.moe>
Subject: Re: serial console on Mikrotik RB532 non-working
Date: Sat, 21 Feb 2026 17:08:35 +0100 [thread overview]
Message-ID: <aZnYg-1GZgwBbaqk@waldemar-brodkorb.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2602211020130.3233@angie.orcam.me.uk>
Hi Maciej,
Maciej W. Rozycki wrote,
> On Sat, 21 Feb 2026, Waldemar Brodkorb wrote:
>
> > just for your information. This commit also breaks bootup of
> > Microchip PIC32MZ Graphics (DA) Starter Kit.
>
> I'm working on a fix, but it's a tough issue, because at kernel entry we
> don't know the state of the TLB and the existence/activation of the hidden
> TLB "entry disable" bit can't be determined (in which case we could just
> proceed to the final initialisation). I should have something in the next
> week or so, but in the meanwhile please just revert the commits that
> affect your particular configuration.
Great to hear that you are working on a fix.
Thanks for sharing your plan.
best regards
Waldemar
next prev parent reply other threads:[~2026-02-21 16:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 18:39 serial console on Mikrotik RB532 non-working Waldemar Brodkorb
2026-02-03 15:24 ` Jiaxun Yang
2026-02-03 15:28 ` Jiaxun Yang
2026-02-03 18:25 ` Waldemar Brodkorb
2026-02-04 10:14 ` Jonas Gorski
2026-02-04 11:19 ` Waldemar Brodkorb
2026-02-04 11:33 ` Jonas Gorski
2026-02-04 16:38 ` Waldemar Brodkorb
2026-02-05 6:27 ` Rong Zhang
2026-02-05 7:29 ` Waldemar Brodkorb
2026-02-21 9:23 ` Waldemar Brodkorb
2026-02-21 10:28 ` Maciej W. Rozycki
2026-02-21 16:08 ` Waldemar Brodkorb [this message]
2026-02-12 7:35 ` Waldemar Brodkorb
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=aZnYg-1GZgwBbaqk@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=i@rong.moe \
--cc=jiaxun.yang@flygoat.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=rongrong@oss.cipunited.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 read-only IMAP folder(s) and NNTP newsgroup(s).