From: Paul Lalonde <paul.a.lalonde@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Nix/regen: multiboot flags
Date: Tue, 28 Jan 2025 07:45:02 -0800 [thread overview]
Message-ID: <CA+POUVhhB5x2s-1ZOhHFBADfWQDRgM_ExPzN7jzSTbW32rqd1g@mail.gmail.com> (raw)
In-Reply-To: <Z5jCA24aLYrGtSpW@kergis.com>
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
The multiboot specification says: If bit 16 in the ‘flags’ word is set,
then the fields at offsets 12-28 in the Multiboot header are valid, and the
boot loader should use them instead of the fields in the actual executable
header to calculate where to load the OS image.
I believe they are valid in this case. These include the load address for
the kernel and the bit depth of the display, found at l32p.s:37,44
Paul
On Tue, Jan 28, 2025 at 6:09 AM <tlaronde@kergis.com> wrote:
> In l32p.s, the multiboot flags in the the mbi are set as
>
> $0x00010007
>
> but I don't find flags definitions relative to the higher word,
> neither in the multiboot v1 spec, nor in the enum in multiboot.c. They
> are all limited to the two lowest bytes.
>
> What is the purpose of the:
>
> $0x00010007
> ^
>
> Typo?
> --
> Thierry Laronde <tlaronde +AT+ kergis +dot+ com>
> http://www.kergis.com/
> http://kertex.kergis.com/
> Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T57431cc6930f8b70-Mf34572c05f19207ae4ccc210
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2969 bytes --]
next prev parent reply other threads:[~2025-01-28 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 11:39 tlaronde
2025-01-28 15:30 ` Ron Minnich
2025-01-28 15:45 ` Paul Lalonde [this message]
2025-01-28 17:08 ` tlaronde
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=CA+POUVhhB5x2s-1ZOhHFBADfWQDRgM_ExPzN7jzSTbW32rqd1g@mail.gmail.com \
--to=paul.a.lalonde@gmail.com \
--cc=9fans@9fans.net \
/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).