All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Salazar <julian.salazar@shaw.ca>
To: grub-devel@gnu.org
Subject: [PATCH] GRUB2 does not provide Multiboot Legacy memory map
Date: Sat, 19 Apr 2008 15:11:43 -0600	[thread overview]
Message-ID: <9749AF5472B1456697B81669920AE810@JerryPC> (raw)

[-- Attachment #1: Type: text/plain, Size: 632 bytes --]

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.


[-- Attachment #2: Type: text/html, Size: 2528 bytes --]

             reply	other threads:[~2008-04-19 21:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-19 21:11 Julian Salazar [this message]
2008-04-19 21:32 ` [PATCH] GRUB2 does not provide Multiboot Legacy memory map Thomas Schwinge
2008-04-19 22:09   ` Julian Salazar
2008-04-20 10:12     ` Robert Millan

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=9749AF5472B1456697B81669920AE810@JerryPC \
    --to=julian.salazar@shaw.ca \
    --cc=grub-devel@gnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.