From: Kevin Wolf <kwolf@redhat.com>
To: "François Revol" <revol@free.fr>
Cc: rene@exactcode.de, agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] Add multiboot support (x86) v2
Date: Thu, 18 Jun 2009 11:09:10 +0200 [thread overview]
Message-ID: <4A3A0436.3070708@redhat.com> (raw)
In-Reply-To: <1971664413-BeMail@laptop>
François Revol schrieb:
>> François Revol wrote:
>>>> This patch implements support for Multiboot on x86 for -kernel.
>>>> Multiboot is a "new" approach to get rid of different bootloaders,
>>>> providing
>>>> a unified interface for the kernel. It supports command line
>>>> options
>>>> and
>>>> kernel modules.
>>>>
>>>> The two probably best known projects using multiboot are Xen and
>>>> GNU
>>>> Hurd.
>>>>
>>> While Haiku doesn't use it (yet, but it will probably never be able
>>> to
>>> load without a BIOS except with the gzipped kernel trick used on a
>>> floppy image for CD booting), it'd be nice to have the -append
>>> option
>>> args forwarded by the BIOS so one could still use -append
>>> regardless
>>> the boot method used to pass options to the OS, in which case I'd
>>> add
>>> support for them in the Haiku loader.
>>>
>> How can the BIOS pass such information?
>>
>> The BIOS boot specification doesn't have any notion of command line
>> AFAIK.
>
> Indeed, at least not the PC BIOS.
> OF has the concept OTH... and QEMU does pass it through IIRC, and Haiku
> should be able to get it AFAIR.
>
> The idea would be to have it pass it anyway through a multiboot frame.
> It would them behave just as if the OS was booted by grub and args had
> been typed at boot time, as well as select the boot resolution.
Why would an OS want to parse multiboot structures but not implement
proper multiboot support? I mean, this really isn't anything
complicated. When you have enabled it to understand multiboot structures
you are only missing a handful of bytes for the multiboot header.
What is it that you need to do differently for Haiku?
Kevin
next prev parent reply other threads:[~2009-06-18 9:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 16:41 [Qemu-devel] [PATCH 0/4] Add multiboot support (x86) v2 Alexander Graf
2009-06-17 16:41 ` [Qemu-devel] [PATCH 1/4] Change bochs bios init order Alexander Graf
2009-06-17 16:41 ` [Qemu-devel] [PATCH 2/4] Expose fw_cfg v2 Alexander Graf
2009-06-17 16:41 ` [Qemu-devel] [PATCH 3/4] Multiboot support v2 Alexander Graf
2009-06-17 16:41 ` [Qemu-devel] [PATCH 4/4] Multiboot build system Alexander Graf
2009-06-18 9:56 ` [Qemu-devel] [PATCH 3/4] Multiboot support v2 Avi Kivity
2009-06-18 10:22 ` Alexander Graf
2009-06-18 11:19 ` Avi Kivity
2009-06-17 17:10 ` [Qemu-devel] [PATCH 0/4] Add multiboot support (x86) v2 François Revol
2009-06-17 17:59 ` Anthony Liguori
2009-06-18 8:25 ` François Revol
2009-06-18 9:09 ` Kevin Wolf [this message]
2009-06-18 11:44 ` François Revol
2009-06-18 11:55 ` Alexander Graf
2009-06-18 12:13 ` François Revol
2009-06-18 12:01 ` Kevin Wolf
2009-06-18 12:17 ` François Revol
2009-06-18 12:23 ` Alexander Graf
2009-06-18 12:34 ` François Revol
2009-06-18 12:29 ` Kevin Wolf
2009-06-18 12:35 ` François Revol
2009-06-18 11:15 ` Gleb Natapov
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=4A3A0436.3070708@redhat.com \
--to=kwolf@redhat.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=rene@exactcode.de \
--cc=revol@free.fr \
/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).