From: Russell King <rmk@arm.linux.org.uk>
To: Gerald Britton <gbritton@alum.mit.edu>
Cc: 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 18:44:21 +0100 [thread overview]
Message-ID: <20030708184421.A13083@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030708132417.B10882@light-brigade.mit.edu>; from gbritton@alum.mit.edu on Tue, Jul 08, 2003 at 01:24:17PM -0400
On Tue, Jul 08, 2003 at 01:24:17PM -0400, Gerald Britton wrote:
> On Tue, Jul 08, 2003 at 04:42:30PM +0100, Alan Cox wrote:
> > Interesting. I wonder why our fixup would have failed - its not something
> > I've seen but we should fixup cardbus resource blocks (2.4 isnt smart
> > enough to handle multidevice cardbus but Rmk has 2.5 code that is), but
> > for the normal case it ought to have worked.
The x86 pci setup stuff is something I'm not completely certain about
since it is handled in a different way from the "normal" (from my point
of view at least) PCI code.
However, I do have some outstanding patches which clean up the init and
resource stuff but unfortunately break it on x86. For everything to
work as expected, I'd like x86 and whatever other architectures either
handle this in the core pci code, or the architecture specific code.
I see this as a quirk of x86 platforms.
(Architectures which do a full setup of the bus in the kernel set the
cardbus bridge up as part of their normal setup.)
> Is it smart enough to handle a case like this:
>
> [device resource 00-01]
> [bridge resource 01-04]
> [device resource 01-02]
> [cardbus bridge no resources]
> [cardbus bridge no resources]
> [device resource 02-04]
> [bridge resoruce 04-06]
> [device resource 04-06]
> [device resource 06-07]
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?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-07-08 17:29 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 [this message]
2003-07-08 20:58 ` Jamie Lokier
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=20030708184421.A13083@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--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
all inboxes | Powered by JetHome®