From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: multiboot2: make multiboot header optional
Date: Sat, 02 Dec 2006 17:18:10 +0100 [thread overview]
Message-ID: <877ixa2rwd.fsf@xs4all.nl> (raw)
In-Reply-To: <200611250525.00823.okuji@enbug.org> (Yoshinori K. Okuji's message of "Sat, 25 Nov 2006 05:25:00 +0100")
"Yoshinori K. Okuji" <okuji@enbug.org> writes:
> On Saturday 25 November 2006 04:35, Hollis Blanchard wrote:
>> > I don't like it very much. My first draft was exactly like this. But,
>> > after some discussion in the IRC, I decided to revert my idea, because
>> > specifying so many parameters by hand really sucks. It is too
>> > error-prone.
>>
>> Bits are less error-prone?
>
> Less typing is less error-prone.
What is the problem with typing? I do not think this is really
complex? And this is just in the initial stage of the implementation
of an operating system. I don't think this is a problem, I think
something that is clear from the context, which is the case in Hollis'
proposal will prevent such errors.
>> How about this:
>> MB_START_TAGS()
>> MB_LOADADDR(0x1234)
>> MB_ENTRYADDR(0x1234)
>> MB_END_TAGS()
>
> How to abbreviate information does not matter. When one implements an OS, she
> must put the definition at somewhere anyway. Even if we provide a sample
> implementation, not all people won't use it, because there are various
> assemblers and compilers. For example, if our example is for GNU as, nasm
> users won't use it. So the spec must be simple.
Can't this be done with nasm?
--
Marco
next prev parent reply other threads:[~2006-12-02 16:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 22:58 multiboot2: make multiboot header optional Hollis Blanchard
2006-11-15 8:57 ` Johan Rydberg
2006-11-15 18:42 ` Hollis Blanchard
2006-11-15 20:42 ` Yoshinori K. Okuji
2006-11-15 21:39 ` Hollis Blanchard
2006-11-15 23:38 ` tgingold
2006-11-25 2:59 ` Yoshinori K. Okuji
2006-11-25 3:35 ` Hollis Blanchard
2006-11-25 4:25 ` Yoshinori K. Okuji
2006-12-02 16:18 ` Marco Gerards [this message]
2006-12-02 17:27 ` Yoshinori K. Okuji
2006-12-04 16:43 ` Hollis Blanchard
2006-12-05 20:23 ` Yoshinori K. Okuji
2006-12-07 23:07 ` multiboot2: using tags in the multiboot header Hollis Blanchard
2006-12-12 22:23 ` Yoshinori K. Okuji
2006-12-04 20:35 ` multiboot2: make multiboot header optional Marco Gerards
2006-12-05 19:09 ` Hollis Blanchard
2006-12-05 20:04 ` Yoshinori K. Okuji
2006-12-07 22:39 ` Hollis Blanchard
2006-12-12 22:08 ` Yoshinori K. Okuji
2006-12-13 4:18 ` Hollis Blanchard
2006-12-13 20:56 ` Yoshinori K. Okuji
2006-12-13 12:28 ` Marco Gerards
2006-12-02 16:15 ` Marco Gerards
2006-12-02 17:19 ` Yoshinori K. Okuji
2006-11-15 20:37 ` Yoshinori K. Okuji
2006-11-15 23:41 ` tgingold
2006-11-21 16:18 ` Hollis Blanchard
2006-11-21 17:35 ` tgingold
2006-11-25 3:05 ` Yoshinori K. Okuji
2006-11-25 3:00 ` Yoshinori K. Okuji
2006-11-25 6:12 ` Tristan Gingold
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=877ixa2rwd.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--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.