From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MHGeB-0006mq-NG
	for qemu-devel@nongnu.org; Thu, 18 Jun 2009 08:23:15 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MHGe3-0006jq-Ep
	for qemu-devel@nongnu.org; Thu, 18 Jun 2009 08:23:11 -0400
Received: from [199.232.76.173] (port=52528 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MHGe3-0006ji-1M
	for qemu-devel@nongnu.org; Thu, 18 Jun 2009 08:23:07 -0400
Received: from cantor.suse.de ([195.135.220.2]:33619 helo=mx1.suse.de)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <agraf@suse.de>) id 1MHGe2-0003Oo-I9
	for qemu-devel@nongnu.org; Thu, 18 Jun 2009 08:23:06 -0400
Message-Id: <26A499CF-3400-4EC9-A0DA-8CC994FE423E@suse.de>
From: Alexander Graf <agraf@suse.de>
In-Reply-To: <2966333961-BeMail@laptop>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v935.3)
Subject: Re: [Qemu-devel] [PATCH 0/4] Add multiboot support (x86) v2
Date: Thu, 18 Jun 2009 14:23:00 +0200
References: <2966333961-BeMail@laptop>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?ISO-8859-1?Q?Fran=E7ois_Revol?= <revol@free.fr>
Cc: Kevin Wolf <kwolf@redhat.com>, rene@exactcode.de, qemu-devel@nongnu.org


On 18.06.2009, at 14:17, Fran=E7ois Revol wrote:

>> Fran=E7ois Revol schrieb:
>>>> 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?
>>>
>>> Because Haiku has its own second stage loader, which requires the
>>> BIOS
>>> to locate the kernel and module in a BFS partition which grub
>>> doesn't
>>> implement btw.
>>
>> That makes sense on real hardware, of course. But for -kernel you
>> don't
>> need a file system to read the kernel from.
>
> Except that wouldn't be the actual kernel passed but the 2nd stage.
> And having to pass the kernel in a tgz outside the BFS image makes it
> more complex to set up.

I don't see why you need a tgz file. Multiboot can pass multiple =20
modules. Just use -initrd foo,bar,xxx

Alex