From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1GeDdj-0005lF-4M for mharc-grub-devel@gnu.org; Sun, 29 Oct 2006 11:36:03 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GeDdh-0005l1-C6 for grub-devel@gnu.org; Sun, 29 Oct 2006 11:36:01 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GeDdg-0005kH-5H for grub-devel@gnu.org; Sun, 29 Oct 2006 11:36:01 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GeDdf-0005kE-Tr for grub-devel@gnu.org; Sun, 29 Oct 2006 11:35:59 -0500 Received: from [212.27.42.28] (helo=smtp2-g19.free.fr) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GeDdf-0006fC-Tj for grub-devel@gnu.org; Sun, 29 Oct 2006 11:36:00 -0500 Received: from saphi (boi78-1-82-232-198-173.fbx.proxad.net [82.232.198.173]) by smtp2-g19.free.fr (Postfix) with ESMTP id 95CDB75ED8 for ; Sun, 29 Oct 2006 17:35:58 +0100 (CET) Received: from gingold by saphi with local (Exim 3.36 #1 (Debian)) id 1GeDfz-0000eE-00 for ; Sun, 29 Oct 2006 17:38:23 +0100 Date: Sun, 29 Oct 2006 17:38:23 +0100 To: The development of GRUB 2 Message-ID: <20061029163823.GA2484@saphi> References: <1161892715.17811.33.camel@basalt.austin.ibm.com> <20061027040907.GA2485@saphi> <1161927455.10997.2.camel@diesel> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1161927455.10997.2.camel@diesel> User-Agent: Mutt/1.5.6+20040907i From: Tristan Gingold Subject: Re: some multiboot2 comments X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2006 16:36:01 -0000 On Fri, Oct 27, 2006 at 12:37:35AM -0500, Hollis Blanchard wrote: > On Fri, 2006-10-27 at 06:09 +0200, Tristan Gingold wrote: > > On Thu, Oct 26, 2006 at 02:58:35PM -0500, Hollis Blanchard wrote: > > > http://grub.enbug.org/MultibootDraft > > > > > > I'm looking at implementing this now. > > > > > > Module: > > > Because of the 'length' field in the tag header, the 'reserved' field > > > isn't actually needed. The 'length' field makes every one of these tag > > > structures inherently variably sized. Any data added later to this tag > > > will be skipped over by the reader. > > Yes. > > BTW, why not adding a type field for module tag. The type (which should be > > an UUID IMHO) should indicate the type of the module. > > One usage could be for Xen. On Xen you can load 3 modules: the linux kernel, > > the linux ramdisk and an ACM configuration. Xen relies on order and on some > > magic checks to find the module type. > > The command syntax could be: > > module [-type TYPE] file [cmdline] > > What do you mean by UUID? I certainly would not like to see large magic > numbers required in grub.cfg... grub should be aware of the main module types. For these TYPE is a keyword such as ramdisk, kernel, xen-acm... For not yet known types, TYPE can be an UUID. UUID doesn't require a central administration. I think this is a real advantage. > > > Memory Map: > > > I'm not sure if we need this. The OS can get this information from > > > firmware (e.g. BIOS e820 map or Open Firmware) as easily as we can, > > > right? In general, I don't think we should convert firmware information > > > into the multiboot structure. > > Some platform may need it. On EFI the OS can't get the memmap from EFI because > > it is too late. > > OK. In that case we're still keeping with the philosophy of only passing > information to the kernel that it can't obtain itself. Yes. Tristan.