public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Alexander van Heukelum <heukelum@mailshack.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	Linus Torvalds <torvalds@osdl.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	John Coffman <johninsd@san.rr.com>
Subject: Re: [PATCH] Remove lilo-loads-only-five-sectors-of-zImage-fixup from setup.S
Date: Wed, 11 Oct 2006 11:38:09 -0700	[thread overview]
Message-ID: <452D3A11.5020100@zytor.com> (raw)
In-Reply-To: <20061011163356.GA2022@mailshack.com>

Alexander van Heukelum wrote:
> Hi!
> 
> The real-mode kernel (on i386 and x86_64) checks if the bootloader
> loaded it correctly. Apparantly, very old versions of LILO disregarded
> the setupsects field in the bootsector and always just loaded the first
> five sectors. If the kernel is compiled as a zImage, the real-mode
> kernel is able to rectify the situation. At least it was, until the code
> to do so was moved to the eighth sector in order to make space for more
> E820 entries (commit: f9ba70535dc12d9eb57d466a2ecd749e16eca866). This
> occured on 1 May 2005 and as far as I know, noone has complained yet.
> This patch removes the checks for the signature and the fixup code
> completely.
> 
> Comments? Which bootloaders are still in use? Kill zImage?
> 

Andrew asked me to comment on this...

This removes support for boot loaders that did not understand boot 
loader protocol version 2.00 or later.  This probably includes very 
early versions of LILO as well as the long-since obsolete Bootlin and 
Shoelace.  Those loaders were unable to load bzImages as well.

I have been urging that we kill zImage for a long time.  It is virtually 
impossible to build a kernel today that will fit inside the zImage 512K 
compressed limitation.

It would be useful for setup.S to halt with a message if such an early 
bootloader is detected, however.  This would have to be parked in the 
first 2K of the setup area, and can simply be detected by looking for 
zero in type_of_loader.

	-hpa


  reply	other threads:[~2006-10-11 18:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11 16:33 [PATCH] Remove lilo-loads-only-five-sectors-of-zImage-fixup from setup.S Alexander van Heukelum
2006-10-11 18:38 ` H. Peter Anvin [this message]
2006-10-11 19:43   ` Alexander van Heukelum
2006-10-11 19:43     ` H. Peter Anvin
2006-10-12 16:57     ` John Coffman
2006-10-12 17:04       ` H. Peter Anvin
2006-10-12 18:15         ` Alexander van Heukelum
2006-10-12 17:43       ` looking for explanation of spontaneous reset/reboot on Opteron Edward Goggin
2006-10-12 21:06         ` Randy Dunlap

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=452D3A11.5020100@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=heukelum@mailshack.com \
    --cc=johninsd@san.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=venkatesh.pallipadi@intel.com \
    /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