All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] NetBSD mmap support
Date: Wed, 26 Aug 2009 02:21:58 +0200	[thread overview]
Message-ID: <20090826002158.GB25183@thorin> (raw)
In-Reply-To: <d7ead6de0908251617m62bb8ca3hb65bdf112efe5452@mail.gmail.com>

On Wed, Aug 26, 2009 at 01:17:07AM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Wed, Aug 26, 2009 at 1:13 AM, Robert Millan<rmh@aybabtu.com> wrote:
> > On Wed, Aug 26, 2009 at 12:52:47AM +0200, Vladimir 'phcoder' Serbinenko wrote:
> >>  2009-08-25  Vladimir Serbinenko  <phcoder@gmail.com>
> >>
> >> +     NetBSD memory map support.
> >> +
> >> +     * include/grub/i386/bsd.h (NETBSD_BTINFO_MEMMAP): New definition.
> >> +     (grub_netbsd_btinfo_mmap_header): New structure.
> >> +     (grub_netbsd_btinfo_mmap_entry): Likewise.
> >> +     * loader/i386/bsd.c (grub_netbsd_boot): Pass memory map.
> >
> > Didn't NetBSD move to Multiboot?  I thought our NetBSD loader was only for
> > legacy versions.
> >
> NetBSD32 supports both multiboot and own protocol. NetBSD64 supports
> only own protocol. Our NetBSD loader handles both NetBSD32 and
> NetBSD64

Ok.  Please go ahead with your patch then.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



      reply	other threads:[~2009-08-26  0:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25 22:52 [PATCH] NetBSD mmap support Vladimir 'phcoder' Serbinenko
2009-08-25 23:13 ` Robert Millan
2009-08-25 23:17   ` Vladimir 'phcoder' Serbinenko
2009-08-26  0:21     ` Robert Millan [this message]

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=20090826002158.GB25183@thorin \
    --to=rmh@aybabtu.com \
    --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.