From: Randy Dunlap <rdunlap@infradead.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
"Dr. David Alan Gilbert" <linux@treblig.org>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org,
npiggin@gmail.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: Use shared font data
Date: Wed, 2 Aug 2023 07:44:57 -0700 [thread overview]
Message-ID: <182b08ea-04f3-3282-e3c3-9448bab6568a@infradead.org> (raw)
In-Reply-To: <871qgl1vs2.fsf@mail.lhotse>
On 8/2/23 05:19, Michael Ellerman wrote:
> "Dr. David Alan Gilbert" <linux@treblig.org> writes:
>> * Michael Ellerman (mpe@ellerman.id.au) wrote:
>>> linux@treblig.org writes:
>>>> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>>>>
>>>> PowerPC has a 'btext' font used for the console which is almost identical
>>>> to the shared font_sun8x16, so use it rather than duplicating the data.
>>>>
>>>> They were actually identical until about a decade ago when
>>>> commit bcfbeecea11c ("drivers: console: font_: Change a glyph from
>>>> "broken bar" to "vertical line"")
>>>>
>>>> which changed the | in the shared font to be a solid
>>>> bar rather than a broken bar. That's the only difference.
>>>>
>>>> This was originally spotted by PMD which noticed that sparc does
>>>
>>> PMD means "Page Middle Directory" to most Linux folks, I assume that's
>>> not what you meant :)
>>
>> Ah, any good TLA is ripe for reuse:
>> https://pmd.github.io/pmd/pmd_userdocs_cpd.html
>
> Thanks.
>
> Unfortunately this patch causes a warning:
>
> WARNING: unmet direct dependencies detected for FONT_SUN8x16
> Depends on [n]: FONT_SUPPORT [=y] && FRAMEBUFFER_CONSOLE [=y] && (!SPARC && FONTS [=n] || SPARC)
> Selected by [y]:
> - BOOTX_TEXT [=y] && PPC_BOOK3S [=y]
>
> And breaks allmodconfig with:
>
> ld: arch/powerpc/kernel/btext.o:(.toc+0x0): undefined reference to `font_sun_8x16'
> make[3]: *** [../scripts/Makefile.vmlinux:36: vmlinux] Error 1
>
> I guess the Kconfig logic needs some more work.
Also please see:
https://lore.kernel.org/all/dd29e5f5-d9f7-0103-e602-b98f26c88fb1@infradead.org/
for a similar problem on UML.
--
~Randy
next prev parent reply other threads:[~2023-08-02 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 0:01 [PATCH] powerpc: Use shared font data linux
2023-07-25 17:01 ` Sam Ravnborg
2023-07-25 17:08 ` Dr. David Alan Gilbert
2023-07-28 3:44 ` Michael Ellerman
2023-07-28 10:39 ` Dr. David Alan Gilbert
2023-08-02 12:19 ` Michael Ellerman
2023-08-02 14:44 ` Randy Dunlap [this message]
2023-08-02 16:43 ` 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=182b08ea-04f3-3282-e3c3-9448bab6568a@infradead.org \
--to=rdunlap@infradead.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=sam@ravnborg.org \
/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).