Date: Mon, 10 Oct 2005 21:21:30 +0200
From: Pavel Machek <pavel@suse.cz>
To: Etienne Lorrain <etienne.lorrain@masroudeau.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Gujin linux.kgz boot format
Message-ID: <20051010192130.GB2204@elf.ucw.cz>
References: <2031.192.168.201.6.1128591983.squirrel@pc300> <20051007144631.GA1294@elf.ucw.cz> <2520.192.168.201.6.1128943428.squirrel@pc300> <20051010115641.GA2983@elf.ucw.cz> <3125.192.168.201.6.1128949772.squirrel@pc300> <20051010131925.GA19256@atrey.karlin.mff.cuni.cz> <3768.192.168.201.6.1128954688.squirrel@pc300>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3768.192.168.201.6.1128954688.squirrel@pc300>
User-Agent: Mutt/1.5.9i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 950
Lines: 25

Hi!

> >> > may be good goal...
> >>
> >>   At least that is a way which does not involve modifying assembler
> >>  files. Slowly everybody switches to the C version which continue
> >>  to evolve (i.e. removing old BIOS calls), then the tree under
> >>  arch/i386/boot is removed and we can begin to rearrange the mapping
> >>  of "struct linux_param".
> >
> > Will your C version work with lilo and grub?
> 
>   Tricky question. In short no, it cannot.

I do not see a point, then. We have bad assembly bootup code. Adding
good C bootup code, that is incompatible with lilo/grub does nothing
to clean the mess up.
								Pavel
-- 
if you have sharp zaurus hardware you don't need... you know my address
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/