From: Robbie Harwood <rharwood@redhat.com>
To: Chris Coulson <chris.coulson@canonical.com>, grub-devel@gnu.org
Cc: daniel.kiper@oracle.com, Chris Coulson <chris.coulson@canonical.com>
Subject: Re: [PATCH] font: Try opening fonts from the bundled memdisk
Date: Wed, 26 Apr 2023 07:56:01 -0400 [thread overview]
Message-ID: <jlgr0s697se.fsf@redhat.com> (raw)
In-Reply-To: <20230426100652.150775-1-chris.coulson@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
Chris Coulson <chris.coulson@canonical.com> writes:
> Grub since 93a786a00163e50c29f0394df198518617e1c9a5 has enforced
> verification of font files in secure boot mode. In order to continue to
> be able to load some default fonts, vendors may bundle them with their
> signed EFI image by adding them to the built-in memdisk.
>
> This change makes the font loader try loading fonts from the memdisk
> before the prefix path when attempting to load a font file by specifying
> its filename, which avoids having to make changes to grub configurations
> in order to accommodate memdisk bundled fonts. It expects the directory
> structure to be the same as fonts stored in the prefix path
> (ie, /fonts/<name>.pf2).
>
> Signed-off-by: Chris Coulson <chris.coulson@canonical.com>
Thanks for posting this.
Reviewed-by: Robbie Harwood <rharwood@redhat.com>
Be well,
--Robbie
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2023-04-26 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 10:06 [PATCH] font: Try opening fonts from the bundled memdisk Chris Coulson
2023-04-26 10:28 ` Steve McIntyre
2023-04-26 11:56 ` Robbie Harwood [this message]
2023-04-28 13:43 ` Daniel Kiper
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=jlgr0s697se.fsf@redhat.com \
--to=rharwood@redhat.com \
--cc=chris.coulson@canonical.com \
--cc=daniel.kiper@oracle.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.