[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: multiboot2: make multiboot header optional

From: Marco Gerards
Subject: Re: multiboot2: make multiboot header optional
Date: Mon, 04 Dec 2006 21:35:38 +0100
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)

"Yoshinori K. Okuji" <address@hidden> writes:

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

I am all for something that is simple.  Initially it looked like
Hollis' proposal was more complex, but IIRC he mentioned he wanted to
work on making this easier to use.  Isn't this what he did?  Or did I
misunderstand something?  If someone (Hollis in this case) thinks I am
wrong and comes with a good argumentation, I am always willing to
change my opinion.

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

Actually, Hollis tried to proof we do not need a header at all.  I
personally find this an interesting option to discuss.

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

No, but in that other case the header can't be generated and it will
be harder.  But I think we have to optimize for the common case.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]