From: Denis Vlasenko <vda@ilport.com.ua>
To: etienne.lorrain@masroudeau.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Gujin linux.kgz boot format
Date: Tue, 11 Oct 2005 16:56:30 +0300 [thread overview]
Message-ID: <200510111656.30403.vda@ilport.com.ua> (raw)
In-Reply-To: <2031.192.168.201.6.1128591983.squirrel@pc300>
On Thursday 06 October 2005 12:46, Etienne Lorrain wrote:
> Hello,
>
> This is following that set of patch:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=112557274910448&w=4
> to get a simpler structure of the vmlinux boot file, named like:
> /boot/linux-2.6.14.kgz
>
> This linux-*.kgz format is the "native" format of the Gujin
> bootloader which can be found here:
> http://gujin.org
/me looking at the site
Wow. Isn't this overdesigned by wide margin?
> The main change of this set of patch is the rewrite of nearly all
> the ia16/ia32 assembler of Linux into a C file named "realmode.c",
> and its include "realmode.h". The mapping of the 4 Kbytes memory
> page exchanged in between real mode and protected mode is exactly
> the same, but is described in a C structure - a lot cleaner.
> Another big change is that the GZIP compressed file produced during
> Linux compilation now contains a comment describing some important
> information: which processor this kernel has been compiled for (so
> no invalid instruction crash when running a Athlon compiled kernel
> on a Pentium - but a nice error message from the bootloader), which
> video mode the kernel support (VGA text or VESA, and which VESA)...
>
> If you apply this set of patch, you still can use the old method
> to boot a kernel with LILO, Loadlin, Grub or SYSLINUX, and this
> patch will not modify any assembler instruction executed on this
> boot path when you use "make bzImage" or the like.
> To produce the new format you just have to apply at least the
> first two patch and type "make /boot/linux-gujin.kgz ROOT=auto",
> or apply the 3rd patch to get root autodetection (based on the
> partition/directory of the linux*.kgz file loaded) and type
> "make /boot/linux-gujin.kgz". (also see "make help")
Apart from shaving a few kb's from kernel image (which are discarded
anyway after boot, IIRC), what advantages does this bring?
Do they outweigh effort needed to maintain it?
--
vda
next prev parent reply other threads:[~2005-10-11 13:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 9:46 [PATCH 1/3] Gujin linux.kgz boot format Etienne Lorrain
2005-10-07 14:46 ` Pavel Machek
2005-10-10 11:23 ` Etienne Lorrain
2005-10-10 11:56 ` Pavel Machek
2005-10-10 13:09 ` Etienne Lorrain
2005-10-10 13:19 ` Pavel Machek
2005-10-10 14:31 ` Etienne Lorrain
2005-10-10 19:21 ` Pavel Machek
2005-10-10 19:35 ` Kalin KOZHUHAROV
2005-10-11 13:56 ` Denis Vlasenko [this message]
2005-10-11 15:23 ` Etienne Lorrain
-- strict thread matches above, loose matches on Subject: below --
2005-10-06 13:39 Etienne Lorrain
2005-10-11 13:16 Etienne Lorrain
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=200510111656.30403.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=etienne.lorrain@masroudeau.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