From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MHDdh-0008HG-JO for qemu-devel@nongnu.org; Thu, 18 Jun 2009 05:10:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MHDdb-0008DP-7Z for qemu-devel@nongnu.org; Thu, 18 Jun 2009 05:10:31 -0400 Received: from [199.232.76.173] (port=37915 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MHDdb-0008DM-2s for qemu-devel@nongnu.org; Thu, 18 Jun 2009 05:10:27 -0400 Received: from mx2.redhat.com ([66.187.237.31]:48156) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MHDda-00039Z-Ke for qemu-devel@nongnu.org; Thu, 18 Jun 2009 05:10:26 -0400 Message-ID: <4A3A0436.3070708@redhat.com> Date: Thu, 18 Jun 2009 11:09:10 +0200 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/4] Add multiboot support (x86) v2 References: <1971664413-BeMail@laptop> In-Reply-To: <1971664413-BeMail@laptop> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?B?RnJhbsOnb2lzIFJldm9s?= Cc: rene@exactcode.de, agraf@suse.de, qemu-devel@nongnu.org Fran=C3=A7ois Revol schrieb: >> Fran=C3=A7ois Revol wrote: >>>> This patch implements support for Multiboot on x86 for -kernel. >>>> Multiboot is a "new" approach to get rid of different bootloaders,=20 >>>> providing >>>> a unified interface for the kernel. It supports command line=20 >>>> options=20 >>>> and >>>> kernel modules. >>>> >>>> The two probably best known projects using multiboot are Xen and=20 >>>> GNU=20 >>>> Hurd. >>>> =20 >>> While Haiku doesn't use it (yet, but it will probably never be able=20 >>> to=20 >>> load without a BIOS except with the gzipped kernel trick used on a=20 >>> floppy image for CD booting), it'd be nice to have the -append=20 >>> option=20 >>> args forwarded by the BIOS so one could still use -append=20 >>> regardless=20 >>> the boot method used to pass options to the OS, in which case I'd=20 >>> add=20 >>> support for them in the Haiku loader. >>> =20 >> How can the BIOS pass such information? >> >> The BIOS boot specification doesn't have any notion of command line=20 >> AFAIK. >=20 > Indeed, at least not the PC BIOS. > OF has the concept OTH... and QEMU does pass it through IIRC, and Haiku= =20 > should be able to get it AFAIR. >=20 > 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=20 > 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