public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@flint.arm.linux.org.uk>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] PCI updates - 32-bit IO support
Date: Tue, 18 Dec 2001 23:50:24 +0000	[thread overview]
Message-ID: <20011218235024.N13126@flint.arm.linux.org.uk> (raw)

I have here a system which requires 32-bit IO addressing on its PCI
busses.  Currently, Linux zeros the upper IO base/limit registers on
all PCI bridges, which prevents addresses being forwarded on this
system.

The following patch the upper IO base/limit registers to be set
appropriately by the PCI layer.

This patch is being sent for review, and is targetted solely at 2.5.

diff -ur orig/drivers/pci/setup-bus.c linux/drivers/pci/setup-bus.c
--- orig/drivers/pci/setup-bus.c	Sun Oct 14 20:53:14 2001
+++ linux/drivers/pci/setup-bus.c	Tue Dec 18 23:20:13 2001
@@ -148,7 +181,10 @@
 	pci_write_config_dword(bridge, PCI_IO_BASE, l);
 
 	/* Clear upper 16 bits of I/O base/limit. */
-	pci_write_config_dword(bridge, PCI_IO_BASE_UPPER16, 0);
+	pci_write_config_word(bridge, PCI_IO_BASE_UPPER16,
+			ranges.io_start >> 16);
+	pci_write_config_word(bridge, PCI_IO_LIMIT_UPPER16,
+			ranges.io_end >> 16);
 
 	/* Clear out the upper 32 bits of PREF base/limit. */
 	pci_write_config_dword(bridge, PCI_PREF_BASE_UPPER32, 0);


--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


             reply	other threads:[~2001-12-19 11:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-18 23:50 Russell King [this message]
2001-12-20  3:37 ` [PATCH] PCI updates - 32-bit IO support H. Peter Anvin
2001-12-20  5:30   ` David S. Miller
2001-12-20  5:57     ` H. Peter Anvin
2001-12-20  9:37     ` Russell King
2001-12-20 13:18       ` Ivan Kokshaysky

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=20011218235024.N13126@flint.arm.linux.org.uk \
    --to=rmk@flint.arm.linux.org.uk \
    --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