From: Tim Hockin <thockin@hockin.org>
Message-Id: <200111200541.fAK5f9J28091@www.hockin.org>
Subject: Re: LOBOS (kexec)
To: ebiederm@xmission.com (Eric W. Biederman)
Date: Mon, 19 Nov 2001 21:41:08 -0800 (PST)
Cc: lm@bitmover.com (Larry McVoy),
        dervishd@jazzfree.com (RaXlNXXez de Arenas Coronado),
        linux-kernel@vger.kernel.org
In-Reply-To: <m1elmu6srj.fsf_-_@frodo.biederman.org> from "Eric W. Biederman" at Nov 19, 2001 08:11:28 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

> The hard part is not linux booting linux but the passing of the
> firmware/BIOS tables from one kernel to the next.  Especially those
> that can only be obtained by a 16bit query.  It is my assumption that
> after the OS runs you cannot return to the firmware, it's state is
> hopelessly mangled.  That may not be totally true but it is fairly
> close to the truth. 

It is unless you control the firmware.  Our (Cobalt) firmware reserves a
region of memory which the primary (in-flash) kernel is not made aware of.
The in-flash kernel can do all the fun things a kernel can do, and then
return to firmware.
-
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/