* multiboot2: kernel->GRUB communication
@ 2006-11-14 22:13 Hollis Blanchard
2006-11-15 8:36 ` tgingold
0 siblings, 1 reply; 3+ messages in thread
From: Hollis Blanchard @ 2006-11-14 22:13 UTC (permalink / raw)
To: The development of GRUB 2
Right now the multiboot2 spec calls for bits to be set in the kernel
image to indicate to GRUB that various features are required or
requested.
I'm trying to come up with a cleaner way. I find all these bits very
confusing, actually, and I think it would be more clear if we had
something like this instead:
[... multiboot header ...]
.ascii "header_addr: 0xf00"
.ascii "load_addr: 0x0"
.ascii ...
(Actually, is it even worth supporting a.out at this point? This
particular example may be obsolete.)
Video mode information:
.ascii "vga_mode: text"
.ascii "columns: 80"
.ascii "rows: 24"
Thoughts?
-Hollis
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: multiboot2: kernel->GRUB communication
2006-11-14 22:13 multiboot2: kernel->GRUB communication Hollis Blanchard
@ 2006-11-15 8:36 ` tgingold
2006-11-15 18:23 ` Hollis Blanchard
0 siblings, 1 reply; 3+ messages in thread
From: tgingold @ 2006-11-15 8:36 UTC (permalink / raw)
To: The development of GRUB 2
Quoting Hollis Blanchard <hollis@penguinppc.org>:
> Right now the multiboot2 spec calls for bits to be set in the kernel
> image to indicate to GRUB that various features are required or
> requested.
>
> I'm trying to come up with a cleaner way. I find all these bits very
> confusing, actually, and I think it would be more clear if we had
> something like this instead:
>
> [... multiboot header ...]
> .ascii "header_addr: 0xf00"
> .ascii "load_addr: 0x0"
> .ascii ...
> (Actually, is it even worth supporting a.out at this point? This
> particular example may be obsolete.)
I am not a big fan of having ascii addresses because it is difficult to
generate them from as and almost impossible from ld.
> Video mode information:
> .ascii "vga_mode: text"
> .ascii "columns: 80"
> .ascii "rows: 24"
Less problematic.
Tristan.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: multiboot2: kernel->GRUB communication
2006-11-15 8:36 ` tgingold
@ 2006-11-15 18:23 ` Hollis Blanchard
0 siblings, 0 replies; 3+ messages in thread
From: Hollis Blanchard @ 2006-11-15 18:23 UTC (permalink / raw)
To: The development of GRUB 2
On Wed, 2006-11-15 at 09:36 +0100, tgingold@free.fr wrote:
> Quoting Hollis Blanchard <hollis@penguinppc.org>:
>
> > Right now the multiboot2 spec calls for bits to be set in the kernel
> > image to indicate to GRUB that various features are required or
> > requested.
> >
> > I'm trying to come up with a cleaner way. I find all these bits very
> > confusing, actually, and I think it would be more clear if we had
> > something like this instead:
> >
> > [... multiboot header ...]
> > .ascii "header_addr: 0xf00"
> > .ascii "load_addr: 0x0"
> > .ascii ...
> > (Actually, is it even worth supporting a.out at this point? This
> > particular example may be obsolete.)
> I am not a big fan of having ascii addresses because it is difficult to
> generate them from as and almost impossible from ld.
OK, good point.
-Hollis
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-11-15 18:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-11-14 22:13 multiboot2: kernel->GRUB communication Hollis Blanchard
2006-11-15 8:36 ` tgingold
2006-11-15 18:23 ` Hollis Blanchard
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.