From: ebiederm@xmission.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>,
Christian Koenig <ChristianK.@t-online.de>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
Otto Wyss <otto.wyss@bluewin.ch>,
Alexander Viro <viro@math.psu.edu>, antirez <antirez@invece.org>,
Andreas Dilger <adilger@turbolabs.com>,
"Grover, Andrew" <andrew.grover@intel.com>,
Craig Christophel <merlin@transgeek.com>
Subject: Re: Booting a modular kernel through a multiple streams file / Making Linux multiboot capable and grub loading kernel modules at boot time.
Date: 19 Dec 2001 08:57:02 -0700 [thread overview]
Message-ID: <m1zo4fursh.fsf@frodo.biederman.org> (raw)
In-Reply-To: <200112181605.KAA00820@tomcat.admin.navo.hpc.mil> <m1r8prwuv7.fsf@frodo.biederman.org> <3C204282.3000504@zytor.com> <m1itb3wsld.fsf@frodo.biederman.org> <3C2052C0.2010700@zytor.com> <m18zbzwp34.fsf@frodo.biederman.org> <3C205FBC.60307@zytor.com>
In-Reply-To: <3C205FBC.60307@zytor.com>
"H. Peter Anvin" <hpa@zytor.com> writes:
> Eric W. Biederman wrote:
> >
> >>From the 10,000 foot level it looks like I am pretty safe already
> > except for those BIOS functions that drive the hardware. For those I
> > need to setup the legacy PIC back to it's default setting, and
> > possibly a few other hardware things. I wonder just how sensitive
> > the an x86 BIOS really is to changing those things...
> >
>
> You never know, especially since part of the BIOS might be an external SCSI or
> network card BIOS...
Which just goes to show what a fragile firmware design it is, to have
firmware callbacks doing device I/O. I think the whole approach of
having firmware callbacks is fundamentally flawed but I'll do my best
to keep it working, for those things that care. If it works over 50%
of the time I'm happy...
The much more interesting challenge is to get the linux kernel drivers
to shutdown their hardware well enough that they can still drive the
hardware when linux restarts. And if the hardware can't do that it is
buggy...
Eric
next prev parent reply other threads:[~2001-12-19 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 16:05 Booting a modular kernel through a multiple streams file / Making Linux multiboot capable and grub loading kernel modules at boot time Jesse Pollard
[not found] ` <m1r8prwuv7.fsf@frodo.biederman.org>
[not found] ` <3C204282.3000504@zytor.com>
[not found] ` <m1itb3wsld.fsf@frodo.biederman.org>
[not found] ` <3C2052C0.2010700@zytor.com>
2001-12-19 9:12 ` Eric W. Biederman
2001-12-19 9:37 ` H. Peter Anvin
2001-12-19 15:57 ` Eric W. Biederman [this message]
2001-12-20 3:20 ` H. Peter Anvin
2001-12-20 6:31 ` Eric W. Biederman
2001-12-20 6:57 ` H. Peter Anvin
2001-12-20 16:39 ` Eric W. Biederman
2001-12-20 18:35 ` H. Peter Anvin
2001-12-21 16:57 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2001-12-17 22:10 Booting a modular kernel through a multiple streams file Grover, Andrew
2001-12-18 15:26 ` Booting a modular kernel through a multiple streams file / Making Linux multiboot capable and grub loading kernel modules at boot time Christian Koenig
2001-12-18 18:32 ` H. Peter Anvin
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=m1zo4fursh.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc="ChristianK."@t-online.de \
--cc=adilger@turbolabs.com \
--cc=andrew.grover@intel.com \
--cc=antirez@invece.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=merlin@transgeek.com \
--cc=otto.wyss@bluewin.ch \
--cc=pollard@tomcat.admin.navo.hpc.mil \
--cc=viro@math.psu.edu \
/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