From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1JnKM2-0008Le-KK for mharc-grub-devel@gnu.org; Sat, 19 Apr 2008 17:12:14 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JnKM0-0008KS-T8 for grub-devel@gnu.org; Sat, 19 Apr 2008 17:12:12 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JnKLw-0008HP-Tf for grub-devel@gnu.org; Sat, 19 Apr 2008 17:12:12 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JnKLw-0008HB-Mo for grub-devel@gnu.org; Sat, 19 Apr 2008 17:12:08 -0400 Received: from idcmail-mo1so.shaw.ca ([24.71.223.10] helo=pd2mo3so.prod.shaw.ca) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JnKLw-000794-MW for grub-devel@gnu.org; Sat, 19 Apr 2008 17:12:08 -0400 Received: from pd3mr5so.prod.shaw.ca (pd3mr5so-qfe3.prod.shaw.ca [10.0.141.12]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0JZL00LY7C7LLZ60@l-daemon> for grub-devel@gnu.org; Sat, 19 Apr 2008 15:11:45 -0600 (MDT) Received: from pn2ml10so.prod.shaw.ca ([10.0.121.80]) by pd3mr5so.prod.shaw.ca (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0JZL00JBIC7LUP00@pd3mr5so.prod.shaw.ca> for grub-devel@gnu.org; Sat, 19 Apr 2008 15:11:46 -0600 (MDT) Received: from JerryPC ([68.144.163.175]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0JZL005ACC7K9Q00@l-daemon> for grub-devel@gnu.org; Sat, 19 Apr 2008 15:11:44 -0600 (MDT) Date: Sat, 19 Apr 2008 15:11:43 -0600 From: Julian Salazar To: grub-devel@gnu.org Message-id: <9749AF5472B1456697B81669920AE810@JerryPC> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.0.6001.18000 X-Mailer: Microsoft Office Outlook 11 Content-type: multipart/alternative; boundary="----=_NextPart_000_0000_01C8A22F.AD7A86B0" Thread-index: AciiYfe61iS2soQRS8aPgaBn1Ff5cA== X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. Subject: [PATCH] GRUB2 does not provide Multiboot Legacy memory map 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: Sat, 19 Apr 2008 21:12:13 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0000_01C8A22F.AD7A86B0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, I'm developing a small kernel and I've been using GRUB2 with the Legacy Multiboot Specification for some time now. I've noticed that it does not provide some of the things in the Multiboot Information structure that GRUB Legacy does, like the memory map. So I've created a small patch which works in QEMU and real hardware so that GRUB2 will pass the memory map to my kernel or any multiboot-compliant kernel for the i386-pc. Since I've never actually contributed code to a GNU project before, are there certain rules and regulations of some sort that I have to comply with before I can send my patch here? Thanks. ------=_NextPart_000_0000_01C8A22F.AD7A86B0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

I’m developing a small kernel and I’ve = been using GRUB2 with the Legacy Multiboot Specification for some time now. = I’ve noticed that it does not provide some of the things in the Multiboot Information structure that GRUB Legacy does, like the memory map. So = I’ve created a small patch which works in QEMU and real hardware so that = GRUB2 will pass the memory map to my kernel or any multiboot-compliant kernel for = the i386-pc.

Since I’ve never actually contributed code to a = GNU project before, are there certain rules and regulations of some sort = that I have to comply with before I can send my patch = here?

Thanks.

------=_NextPart_000_0000_01C8A22F.AD7A86B0--