From: ebiederm@xmission.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Q: Linux rebooting directly into linux.
Date: 11 Nov 2000 23:31:20 -0700 [thread overview]
Message-ID: <m1y9ypbt1j.fsf@frodo.biederman.org> (raw)
In-Reply-To: <m17l6deey7.fsf@frodo.biederman.org> <20001109113524.C14133@animx.eu.org> <m1g0kycm0x.fsf@frodo.biederman.org> <8ukaeb$eh6$1@cesium.transmeta.com> <m13dgycaqh.fsf@frodo.biederman.org> <3A0DE517.3EAF1099@transmeta.com>
In-Reply-To: "H. Peter Anvin"'s message of "Sat, 11 Nov 2000 16:32:23 -0800"
"H. Peter Anvin" <hpa@transmeta.com> writes:
> "Eric W. Biederman" wrote:
> >
> > Hmm. You must mean similiar to milo.
> >
> > Have fun. With linuxBIOS I'm working exactly the other way. Killing
> > off the BIOS. And letting the initial firmware be just a boot loader.
> > The reduction is complexity should make it more reliable.
> >
>
> ... except that you have to handle every single motherboard architecture
> out there now.
Agreed that is a bit of a risk. Mostly you just have to handle
the chipset of the boards and there are a finite number of them.
Only time will tell if this is truly feasible. I think it is certainly
work a try.
And I don't have to handle every single one just all of the ones
I need it to run on :)
With the my kexec patch I'm just getting the infrastructure ready, and that
is functionality that can be used independently of linuxBIOS. If
booting linux from linux would help with what you are doing I love to
work together on that.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-12 7:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 8:18 Q: Linux rebooting directly into linux Eric W. Biederman
[not found] ` <3A0ABB0C.99075A61@holly-springs.nc.us>
2000-11-11 19:46 ` Eric W. Biederman
2000-11-11 22:46 ` Adam Lazur
2000-11-12 0:06 ` Eric W. Biederman
[not found] ` <20001109113524.C14133@animx.eu.org>
2000-11-11 20:05 ` Eric W. Biederman
2000-11-11 20:33 ` H. Peter Anvin
2000-11-12 0:09 ` Eric W. Biederman
2000-11-12 0:32 ` H. Peter Anvin
2000-11-12 6:31 ` Eric W. Biederman [this message]
2000-11-11 22:11 ` Adam Lazur
2000-11-12 0:00 ` Eric W. Biederman
2000-11-14 14:49 ` Werner Almesberger
2000-11-16 17:33 ` Eric W. Biederman
2000-11-19 2:24 ` Werner Almesberger
2000-11-19 7:20 ` Eric W. Biederman
2000-11-19 13:25 ` Werner Almesberger
2000-11-19 20:14 ` Eric W. Biederman
2001-01-18 16:18 ` Eric W. Biederman
2000-11-14 8:13 ` Erik Andersen
2000-11-14 14:59 ` Eric W. Biederman
2000-11-15 23:30 ` Erik Andersen
2000-11-16 6:19 ` 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=m1y9ypbt1j.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=hpa@transmeta.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