linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: "Dr. David Alan Gilbert" <linux@treblig.org>,
	Finn Thain <fthain@linux-m68k.org>
Cc: Stan Johnson <userm57@yahoo.com>,
	mpe@ellerman.id.au, npiggin@gmail.com, 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: Wed, 5 Nov 2025 22:44:38 +0100	[thread overview]
Message-ID: <3cc3d311-35b0-42f1-b20f-ed59391bb8e0@csgroup.eu> (raw)
In-Reply-To: <aQgJ95Y3pA-8GdbP@gallifrey>



Le 03/11/2025 à 02:48, Dr. David Alan Gilbert a écrit :
> * Finn Thain (fthain@linux-m68k.org) wrote:
>>
>> On Sun, 2 Nov 2025, Dr. David Alan Gilbert wrote:
>>
>>>
>>> So I'm not a PPC person specifically; so lets see if the PPC people have
>>> any suggestions, but:
>>>
>>>     a) Do you know if there's any way to recreate the same hang/works
>>> combination in qemu; I know it has a g3beige model but I don't know how
>>> to get something similar to your failing combo.
>>>
>>
>> I guess we could probably reproduce this in QEMU if the BootX bootloader
>> could be made to work there. In theory, 'qemu-system-ppc -M g3beige' might
>> work.
>>
>>>     b) Can you get any diagnostics out of the prom on the mac?  Like a PC
>>> or anything to have some idea where it hung?
>>>
>>
>> Well, that's the problem: if you enable the CONFIG_BOOTX_TEXT diagnostics,
>> the system hangs instead of printing stuff. If you disable the
>> CONFIG_BOOTX_TEXT diagnostics (in favour of serial diagnostics) the hang
>> goes away.
> 
> Ah, a bug that doesn't like to be seen :-)
> 
>> 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.
> 
> 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 think -fPIC is relevant for data-only here because font_sun_8x16 
contains a pointer to fontdata_sun8x16 in font_sun_8x16.data

I see two things to try:

1/ Either build font_sun8x16.o with -fPIC

diff --git a/lib/fonts/Makefile b/lib/fonts/Makefile
index e16f68492174a..844306d7b15e9 100644
--- a/lib/fonts/Makefile
+++ b/lib/fonts/Makefile
@@ -20,3 +20,5 @@ font-objs-$(CONFIG_FONT_6x8)       += font_6x8.o
  font-objs += $(font-objs-y)

  obj-$(CONFIG_FONT_SUPPORT)         += font.o
+
+CFLAGS_font_sun8x16.o             += -fPIC

2/ Or add a PTRRELOC:

diff --git a/arch/powerpc/kernel/btext.c b/arch/powerpc/kernel/btext.c
index 7f63f1cdc6c39..fc461cfaf4a34 100644
--- a/arch/powerpc/kernel/btext.c
+++ b/arch/powerpc/kernel/btext.c
@@ -20,6 +20,7 @@
  #include <asm/io.h>
  #include <asm/processor.h>
  #include <asm/udbg.h>
+#include <asm/setup.h>

  #define NO_SCROLL

@@ -463,7 +464,7 @@ static noinline void draw_byte(unsigned char c, long 
locX, long locY)
  {
  	unsigned char *base	= calc_base(locX << 3, locY << 4);
  	unsigned int font_index = c * 16;
-	const unsigned char *font	= font_sun_8x16.data + font_index;
+	const unsigned char *font	= PTRRELOC(font_sun_8x16.data) + font_index;
  	int rb			= dispDeviceRowBytes;

  	rmci_maybe_on();


Christophe




  parent reply	other threads:[~2025-11-05 22:20 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
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 [this message]
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=3cc3d311-35b0-42f1-b20f-ed59391bb8e0@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=benh@kernel.crashing.org \
    --cc=cedarmaxwell@mac.com \
    --cc=fthain@linux-m68k.org \
    --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).