From: Jamie Lokier <jamie@shareable.org>
To: Gerald Britton <gbritton@alum.mit.edu>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
emperor@EmperorLinux.com, LKML <linux-kernel@vger.kernel.org>,
EmperorLinux Research <research@EmperorLinux.com>,
"Theodore Ts'o" <tytso@mit.edu>
Subject: Re: Linux and IBM : "unauthorized" mini-PCI : Cisco mpi350 _way_ sub-optimal
Date: Tue, 8 Jul 2003 21:58:09 +0100 [thread overview]
Message-ID: <20030708205809.GA18307@mail.jlokier.co.uk> (raw)
In-Reply-To: <20030708184421.A13083@flint.arm.linux.org.uk>
Russell King wrote:
> Definitely not yet, since x86 has a policy of not reallocating anything
> at all. I suspect getting it to handle it will open a huge live mine
> field, full of SMI ports. 8(
>
> Any x86 PCI gurus got any ideas?
You may be able to identify devices which are very unlikely to be
touched by the SMI handler, and just allow those to be moved.
E.g. video cards, USB, IDE, "system", ISA bridge etc. may all be
touched by the SMI (for power management), but the sound, modem and
network are much less unlikely.
Ok, it's flailing a bit...
-- Jamie
next prev parent reply other threads:[~2003-07-08 20:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 16:49 Linux and IBM : "unauthorized" mini-PCI : TCPA updates Lincoln Durey
2003-06-03 16:34 ` Alan Cox
2003-06-03 18:29 ` Josh Litherland
2003-06-03 17:04 ` Michael Frank
2003-06-03 17:42 ` Timothy Miller
2003-06-04 12:39 ` Derek Fawcus
2003-06-06 22:59 ` Martin List-Petersen
2003-06-09 12:57 ` Dana Lacoste
2003-06-09 16:56 ` Martin List-Petersen
2003-06-10 23:35 ` Theodore Ts'o
2003-07-07 18:12 ` Linux and IBM : "unauthorized" mini-PCI : Cisco mpi350 _way_ sub-optimal Lincoln D. Durey
2003-07-08 14:02 ` Alan Cox
2003-07-08 15:20 ` Gerald Britton
2003-07-08 15:42 ` Alan Cox
2003-07-08 17:24 ` Gerald Britton
2003-07-08 17:44 ` Russell King
2003-07-08 20:58 ` Jamie Lokier [this message]
2003-07-09 22:35 ` Gerald Britton
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=20030708205809.GA18307@mail.jlokier.co.uk \
--to=jamie@shareable.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=emperor@EmperorLinux.com \
--cc=gbritton@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=research@EmperorLinux.com \
--cc=tytso@mit.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;
as well as URLs for NNTP newsgroup(s).