All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: multiboot2: make multiboot header optional
Date: Sat, 2 Dec 2006 18:27:31 +0100	[thread overview]
Message-ID: <200612021827.31945.okuji@enbug.org> (raw)
In-Reply-To: <877ixa2rwd.fsf@xs4all.nl>

On Saturday 02 December 2006 17:18, Marco Gerards wrote:
> What is the problem with typing?  I do not think this is really
> complex?

Weird. It was _you_ who pointed out that specifying tags would be annoying on 
the IRC...

> 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.

I do think it is a problem. Whether it is a small portion in OS development or 
not does not matter. If it is problematic, it is.

Reversely, I ask you a question. What is the real advantage in using tags in a 
Multiboot header?

From my point of view, it is not necessarily very extensible or flexible, as 
our experience shows that changes to the Multiboot header are rarely demanded 
(so far, only once, IIRC).

> > 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?

Don't take my words literaly. I just put nasm as an example. There are plenty 
of different languages, and would you like to provide sample code for _all_ 
languages in the world?

Okuji



  reply	other threads:[~2006-12-02 17:27 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
2006-12-02 17:27                   ` Yoshinori K. Okuji [this message]
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=200612021827.31945.okuji@enbug.org \
    --to=okuji@enbug.org \
    --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.