From: Jun Sun <jsun@mvista.com>
To: linux-mips-kernel@lists.sourceforge.net, linux-mips@oss.sgi.com,
ralf@oss.sgi.com
Subject: Re: [PATCH] pci_auto handles better when no IO/MEM behind P2P bridge
Date: Thu, 06 Dec 2001 18:27:31 -0800 [thread overview]
Message-ID: <3C102913.EDBD2EB@mvista.com> (raw)
In-Reply-To: 3C1024A2.F3603F6A@mvista.com
[-- Attachment #1: Type: text/plain, Size: 129 bytes --]
Perhaps this one is better.
It wastes a little PCI space, but looks more elegant... Is elegance still
worth anything? :-)
Jun
[-- Attachment #2: pci-auto-p2p-bridge-noiomem.011205.011206.b.patch --]
[-- Type: text/plain, Size: 641 bytes --]
diff -Nru linux-2.4.16/arch/mips/kernel/pci_auto.c.orig linux-2.4.16/arch/mips/kernel/pci_auto.c
--- linux-2.4.16/arch/mips/kernel/pci_auto.c.orig Mon Nov 26 18:22:58 2001
+++ linux-2.4.16/arch/mips/kernel/pci_auto.c Thu Dec 6 18:24:00 2001
@@ -256,6 +256,14 @@
{
u32 temp;
+ /*
+ * [jsun] we always bump up baselines a little, so that if there
+ * nothing behind P2P bridge, we don't wind up overlapping IO/MEM
+ * spaces.
+ */
+ pciauto_lower_memspc += 1;
+ pciauto_lower_iospc += 1;
+
/* Configure bus number registers */
early_write_config_byte(hose, top_bus, current_bus, pci_devfn,
PCI_SUBORDINATE_BUS, sub_bus);
prev parent reply other threads:[~2001-12-07 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 2:08 [PATCH] pci_auto handles better when no IO/MEM behind P2P bridge Jun Sun
2001-12-07 2:27 ` Jun Sun [this message]
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=3C102913.EDBD2EB@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips-kernel@lists.sourceforge.net \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.com \
/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