public inbox for grub-devel@gnu.org
 help / color / mirror / Atom feed
From: Yao Zi via Grub-devel <grub-devel@gnu.org>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Yao Zi <me@ziyao.cc>
Subject: Re: [question] CLion's autocorrect draws the GNU logo, is this a coincidence?
Date: Thu, 12 Mar 2026 09:21:06 +0000	[thread overview]
Message-ID: <abKFgjdG4WeAV2vM@pie> (raw)
In-Reply-To: <CAKtYDeMCPubPZ9NbfChj5BooNq0xA=Q4xSxAerhEVN5uEZ_sfg@mail.gmail.com>

On Wed, Mar 11, 2026 at 11:37:36PM +0300, Bardia Roshan Pajouh wrote:
> I was opening random grub files out of curiosity in CLion and came across a
> file named grub.chrp.in . The file is full of hex and

It isn't fully hex, it's in SGML format, and you could see tags like
<CHRP-BOOT> and <COMPATIBLE>. This is the bootinfo file defined by
PowerPC Microprocessor Common Hardware Reference Platform (CHRP) System
Binding to IEEE Std 1275‑1994[1], providing boot options information for
the firmware.

> CLions autocorrect
> highlights green under the hex in a way that it looks like the GNU logo. I
> was wondering if this was a coincidence or an easter egg. Sorry for wasting
> your time with this silly question.

The hex is enclosed by OS-BADGE-ICONS tag. Though isn't defined in the
CHRP specification, this seems to be an Apple extension (since it's used
by Apple's BootX, too[2]) for specifying icons for boot options. So I
don't think this is a coincidence.

Regards,
Yao Zi

[1]: https://stuff.mit.edu/afs/sipb/contrib/doc/specs/protocol/chrp/chrp1_7a.pd[2]: https://github.com/apple-oss-distributions/BootX/blob/814114e6a6cf10dfa512c520f5a1c1fb9c58a432/bootx.tproj/bootinfo.hdr#L8

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

           reply	other threads:[~2026-03-12 12:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAKtYDeMCPubPZ9NbfChj5BooNq0xA=Q4xSxAerhEVN5uEZ_sfg@mail.gmail.com>]

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=abKFgjdG4WeAV2vM@pie \
    --to=grub-devel@gnu.org \
    --cc=me@ziyao.cc \
    /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