mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com
To: <linux-kernel@vger.kernel.org>
Date: Sat, 30 Mar 2002 18:33:07 -0700	[thread overview]
Message-ID: <200203310133.SAA12760@frodo.biederman.org> (raw)

Subject: Re: [CFT][RFC] Linux/i386 boot protocol version 2.04
In-Reply-To: <m1d6xmuipv.fsf@frodo.biederman.org>
From: ebiederm@xmission.com (Eric W. Biederman)
Date: 30 Mar 2002 18:33:07 -0700
In-Reply-To: <m1d6xmuipv.fsf@frodo.biederman.org>
Message-ID: <m14rixv7vw.fsf@frodo.biederman.org>
Lines: 29
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

ebiederm@xmission.com (Eric W. Biederman) writes:

> I have been doing some very weird things with booting the Linux kernel
> for a long time.  
>   - Entering the kernel in 32bit mode to avoid 16bit BIOS calls.  
>   - Converting bzImage into static ELF executables.  
>   - Hard coding a kernel command-line
>   - Going back to 16bit mode to make BIOS calls if necessary.
> 
> This version of the boot protocol should be fully backwards compatible
> but has new capabilities so I can do all of the above cleanly.
> 
> The current plan is to send this to Linus in the next couple of days
> as soon as he gets back.
> 
> 
> The patch series is at:
> ftp://download.lnxi.com/pub/src/linux-kernel-patches/boot/
> 
> The overall patch is:
> ftp://download.lnxi.com/pub/src/linux-kernel-patches/boot/linux-2.5.7.boot.diff
> 
> Anyway please tell me what you think.

For those having trouble getting in an alternative address is:
http://www.xmission.com/~ebiederm/files/boot/linux-2.5.7.boot.diff


Eric

             reply	other threads:[~2002-03-31  1:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-31  1:33 ebiederm [this message]
2002-04-07  6:59 ` /proc enhancement George Kola

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=200203310133.SAA12760@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --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

all inboxes | Powered by JetHome®