All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: multiboot on EFI
Date: Sat, 28 Mar 2009 23:31:14 +0900	[thread overview]
Message-ID: <200903282331.14645.okuji@enbug.org> (raw)
In-Reply-To: <20090328131306.GB8493@thorin>

On Saturday 28 March 2009 22:13:06 Robert Millan wrote:
> Do we need the memory map to be sorted?  AFAIK loadees can cope with
> unsorted maps fine;  is there an exception?

As I wrote in the draft, a boot loader should sort the memory map. An OS image 
must deal with an unsorted memory map, because the wording is "should", but 
it is still user-friendly (especially for debugging).

> > +#ifdef GRUB_MACHINE_PCBIOS
> > +  grub_stop_floppy ();
> > +#endif
>
> grub_stop_floppy() doesn't do any BIOS-specific stuff.  Wouldn't __i386__
> be more appropiate?

This should be moved to an arch-specific finalization function. Honestly, I 
prefer that this is done by disk drivers automatically when unloading, but 
some people seem to like giving up unloading modules.

Regards,
Okuji



  reply	other threads:[~2009-03-28 14:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23 12:29 multiboot on EFI phcoder
2009-03-23 21:16 ` uzer cheg
2009-03-23 22:14   ` phcoder
2009-03-23 22:33     ` phcoder
2009-03-24 10:31     ` uzer cheg
2009-03-24 10:54       ` phcoder
2009-03-24 10:58         ` uzer cheg
2009-03-26 19:25           ` Vladimir Serbinenko
2009-03-28 13:13 ` Robert Millan
2009-03-28 14:31   ` Yoshinori K. Okuji [this message]
2009-04-01 12:57     ` Robert Millan
2009-04-01 13:58       ` Yoshinori K. Okuji
2009-03-28 22:33   ` phcoder
2009-04-04 16:28     ` phcoder
2009-04-04 16:51       ` phcoder

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=200903282331.14645.okuji@enbug.org \
    --to=okuji@enbug.org \
    --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.