From: Finn Thain <fthain@linux-m68k.org>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: Stan Johnson <userm57@yahoo.com>,
mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu, sam@ravnborg.org,
benh@kernel.crashing.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, rdunlap@infradead.org,
Cedar Maxwell <cedarmaxwell@mac.com>
Subject: Re: [PATCH v4] powerpc: Use shared font data
Date: Mon, 3 Nov 2025 18:26:16 +1100 (AEDT) [thread overview]
Message-ID: <797f0a13-350f-e26d-f1ef-876419e1c013@linux-m68k.org> (raw)
In-Reply-To: <aQgJ95Y3pA-8GdbP@gallifrey>
On Mon, 3 Nov 2025, Dr. David Alan Gilbert wrote:
>
> > Anyway, I imagine that the problem with your patch was that it relies
> > on font data from a different (read only) section, which is
> > unavailable for some reason (MMU not fully configured yet?)
> >
> > So I've asked Stan to test a patch that simply removes the relevant
> > 'const' keywords. It's not a solution, but might narrow-down the
> > search.
>
Stan tested my patch to remove 'const' from the font_desc and font_data
structs but it did not help. (There goes that theory.)
> I wonder if this is a compiler-flag-ism; I see
> arch/powerpc/kernel/Makefile has a pile of special flags, and for
> btext.o it has a -fPIC (as well as turning off some other flags). I
> wonder if bodging those in lib/fonts/Makefile for
> lib/fonts/font_sun8x16.c fixes it? But... this is data - there's no code
> is there - are any of those flags relevant for data only?
>
I don't know. But I'm sure Stan would be willing to test a patch for you.
> >
> > The BootX bootloader doesn't work on New World systems, which is
> > probably why we don't see this regression on anything newer than a
> > Wallstreet.
> >
> > It's likely that other Old World systems are also affected, if they
> > are using BootX. We don't yet know whether the regression also affects
> > Old World systems using the iQUIK bootloader instead of BootX.
>
> OK, remember I don't think I've ever tried PPC via MacOS booting, so not
> familiar with it.
>
I will try to set up a MacOS guest in QEMU, to see if the hang can be
reproduced that way.
next prev parent reply other threads:[~2025-11-03 7:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 14:27 [PATCH v4] powerpc: Use shared font data linux
2023-09-30 13:15 ` Dr. David Alan Gilbert
2023-10-01 12:08 ` Michael Ellerman
2023-10-02 12:21 ` Dr. David Alan Gilbert
2023-10-15 10:04 ` Michael Ellerman
2025-11-02 5:02 ` Stan Johnson
2025-11-02 11:20 ` Finn Thain
2025-11-02 17:09 ` Dr. David Alan Gilbert
2025-11-02 19:01 ` Stan Johnson
2025-11-03 1:33 ` Finn Thain
2025-11-03 1:48 ` Dr. David Alan Gilbert
2025-11-03 7:26 ` Finn Thain [this message]
2025-11-04 17:59 ` Dr. David Alan Gilbert
2025-11-04 19:49 ` Stan Johnson
2025-11-04 21:59 ` Dr. David Alan Gilbert
2025-11-05 4:13 ` QEMU limitations, was " Finn Thain
2025-11-05 14:58 ` Dr. David Alan Gilbert
2025-11-05 21:44 ` Christophe Leroy
2025-11-05 23:48 ` Finn Thain
2025-11-06 4:11 ` Finn Thain
2025-11-06 9:28 ` Christophe Leroy
2025-11-06 11:50 ` Finn Thain
2025-11-06 12:07 ` Dr. David Alan Gilbert
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=797f0a13-350f-e26d-f1ef-876419e1c013@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=benh@kernel.crashing.org \
--cc=cedarmaxwell@mac.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=rdunlap@infradead.org \
--cc=sam@ravnborg.org \
--cc=userm57@yahoo.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).