From: ebiederm@xmission.com (Eric W. Biederman)
To: Tim Hockin <thockin@hockin.org>
Cc: dervishd@jazzfree.com (RaXlNXXez de Arenas Coronado),
linux-kernel@vger.kernel.org
Subject: Re: LOBOS (kexec)
Date: 19 Nov 2001 23:52:07 -0700 [thread overview]
Message-ID: <m1r8qu53zc.fsf@frodo.biederman.org> (raw)
In-Reply-To: <200111200541.fAK5f9J28091@www.hockin.org>
In-Reply-To: <200111200541.fAK5f9J28091@www.hockin.org>
Tim Hockin <thockin@hockin.org> writes:
> > 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.
Hmm. I might have to check it out. Comparing notes with what you do on
the Cobalt with what I'm doing in linuxBIOS. Do you happen to have
a url?
But as I want a general solution I don't intend to pick a solution
that depends on the firmware.
Eric
next prev parent reply other threads:[~2001-11-20 7:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 0:04 LOBOS RaúlNúñez de Arenas Coronado
2001-11-20 2:17 ` LOBOS Larry McVoy
2001-11-20 2:03 ` LOBOS Tim Hockin
2001-11-20 2:42 ` LOBOS Erik Andersen
2001-11-20 3:11 ` LOBOS (kexec) Eric W. Biederman
2001-11-20 5:41 ` Tim Hockin
2001-11-20 6:52 ` Eric W. Biederman [this message]
2001-11-20 23:56 ` Werner Almesberger
2001-11-21 2:53 ` Eric W. Biederman
2001-11-21 17:11 ` Randy.Dunlap
2001-11-22 6:37 ` Eric W. Biederman
2001-11-20 2:19 ` LOBOS victor
-- strict thread matches above, loose matches on Subject: below --
2001-11-20 12:22 LOBOS (kexec) RaúlNúñez de Arenas Coronado
2001-11-20 13:40 ` Eric W. Biederman
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=m1r8qu53zc.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=dervishd@jazzfree.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@hockin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.