All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gnu.org>
To: Julian Salazar <julian.salazar@shaw.ca>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH] GRUB2 does not provide Multiboot Legacy memory map
Date: Sat, 19 Apr 2008 23:32:17 +0200	[thread overview]
Message-ID: <20080419213217.GG28507@fencepost.gnu.org> (raw)
In-Reply-To: <9749AF5472B1456697B81669920AE810@JerryPC>

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

Hello!

On Sat, Apr 19, 2008 at 03:11:43PM -0600, Julian Salazar wrote:
> 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.

Now this is interesting as I've just today seen an incompatibility
between booting a multiboot kernel with GRUB legacy and GRUB2.  It might
actually be the same issue, but I didn't fully investigate yet.
Therefore I'm quite interested in seeing your patch.


> Since I've never actually contributed code to a GNU project before, are

Welcome!

> there certain rules and regulations of some sort that I have to comply with

Your guessed right: sure there are :-).  See, for example, (parts of) the
GNU Coding Standards, <http://www.gnu.org/prep/standards/html_node/>.
Not everything is relevant in your case, though.

> before I can send my patch here?

Feel free to simply send it here and we'll tell you what needs to be
changed.


Regards,
 Thomas

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-19 21:11 [PATCH] GRUB2 does not provide Multiboot Legacy memory map Julian Salazar
2008-04-19 21:32 ` Thomas Schwinge [this message]
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=20080419213217.GG28507@fencepost.gnu.org \
    --to=tschwinge@gnu.org \
    --cc=grub-devel@gnu.org \
    --cc=julian.salazar@shaw.ca \
    /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.