All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] general-usage real-mode loader
Date: Sun, 07 Sep 2008 14:38:26 +0300	[thread overview]
Message-ID: <48C3BD32.5050109@nic.fi> (raw)
In-Reply-To: <48C3B666.1060605@gmail.com>

phcoder wrote:
> Well sometimes it's similar but most of the time isn't because your code
> runs a code in RM but with hope returning back to PM and normal grub
> operation. And it also loads to quite fixed place. My code would load a
> kernel, that means that it will not return and so code can be loaded to
> any place not needed by kernel.

Do you mind replying inline...?

It is true that code is withing grub's i386 kernel. But other than that
same mechanism can be used to load kernel. After all kernel will take
over the computer after it has started and it is not returning back
anymore (eg. stack is not anymore there to be restored).

I would prefer that if we are going to give custom register
configurations for kernel then they all should use same structures for
storing registers.

But anyway... Did you have some good examples where this functionaly
would be needed :) ? For now we have specialized loaders that prepare
system for any special OSes that needs to be supported. Especially how
do you know what registers to fill or better yet, how user will provide
this information so OS can be loaded.

If there is a need for specialized loader please provide some details
where those are needed and what is required from GRUB in order to
support that. If there is possibility to use multiboot then that would
supersede need for specialized loader.

Thanks,
Vesa Jääskeläinen



  reply	other threads:[~2008-09-07 11:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05 17:27 [RFC] general-usage real-mode loader phcoder
2008-09-05 17:41 ` phcoder
2008-09-06 11:20 ` Robert Millan
2008-09-07  0:25   ` phcoder
2008-09-07  7:25     ` Vesa Jääskeläinen
2008-09-07 11:09       ` phcoder
2008-09-07 11:38         ` Vesa Jääskeläinen [this message]
2008-09-07 12:22           ` phcoder
2008-09-07 15:55             ` 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=48C3BD32.5050109@nic.fi \
    --to=chaac@nic.fi \
    --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.