public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Etienne Lorrain <etienne_lorrain@yahoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Gujin graphical bootloader 0.4
Date: Tue, 14 Aug 2001 00:29:50 +1000	[thread overview]
Message-ID: <15667.997712990@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 13 Aug 2001 14:05:05 +0200." <20010813120505.97748.qmail@web11808.mail.yahoo.com>

On Mon, 13 Aug 2001 14:05:05 +0200 (CEST), 
Etienne Lorrain <etienne_lorrain@yahoo.fr> wrote:
> A good solution would be to have the kernel being two (or three) GZIP
> files concatenated, the first would be the real-mode code to setup
> the structure only, the second would be the protected-mode code of the
> kernel (and the third the initrd). The first part would be a position
> independant function getting some parameters (address/max size of the
> structure to fill in) and returning information like microprocessor
> minimum requirement, video mode supported (number of BPP, or text only),
> address the kernel has been linked (to load a kernel at 16 Mb), ...

Before you go too far, there is already an standard for boot loading,
EFI (Extensible Firmware Interface).  Originally from Intel but it is
open.  http://developer.intel.com/technology/efi.  IA64 uses this and
nothing but this, it already loads kernels in ELF format.  There is no
point in inventing yet another boot interface, unless you cannot do
what you want in EFI.


  reply	other threads:[~2001-08-13 14:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13 12:05 [ANNOUNCE] Gujin graphical bootloader 0.4 Etienne Lorrain
2001-08-13 14:29 ` Keith Owens [this message]
2001-08-14  7:36   ` Eric W. Biederman
2001-08-14  7:53 ` Eric W. Biederman
2001-08-14 11:06   ` Etienne Lorrain
2001-08-14 15:46     ` Eric W. Biederman
     [not found] <fa.mdu6dgv.m10d9i@ifi.uio.no>
2001-08-10 13:02 ` Giacomo Catenazzi
2001-08-10 14:06   ` Etienne Lorrain
  -- strict thread matches above, loose matches on Subject: below --
2001-08-10 12:24 Etienne Lorrain
2001-08-06 10:15 Etienne Lorrain
2001-08-09 11:26 ` Matthias Andree
2001-08-09 13:38   ` Etienne Lorrain
2001-08-09 17:48 ` H. Peter Anvin
2001-08-11  7:17   ` Eric W. Biederman
2001-08-11  8:10     ` H. Peter Anvin
2001-08-14  7:27       ` Eric W. Biederman
2001-08-14 16:42         ` H. Peter Anvin
2001-08-15 16:40           ` Eric W. Biederman

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=15667.997712990@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=etienne_lorrain@yahoo.fr \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox