Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Andrew Isaacson" <adi@broadcom.com>
To: linux-mips@linux-mips.org
Subject: [PATCH 12/12] pci-expmem-hack
Date: Wed, 19 Oct 2005 23:59:46 -0700	[thread overview]
Message-ID: <20051020065946.GL23899@broadcom.com> (raw)
In-Reply-To: <20051020065320.GA23857@broadcom.com>

CFE 1.2.5 and earlier fails to turn on the ExpMemEn bit in the
PCIFeatureControl register, which means that DMA does not work
beyond physical address 01_0000_0000, ergo to DRAM beyond 1GB.

With ExpMemEn turned on, 01_0000_0000-0f_ffff_ffff is mapped,
so DMA works for up to 61 GB of DRAM.

Will be fixed in CFE 1.2.6 (yet to be released).

Signed-Off-By: Andy Isaacson <adi@broadcom.com>

 arch/mips/pci/pci-bcm1480.c |    8 ++++++++
 1 files changed, 8 insertions(+)

Index: lmo/arch/mips/pci/pci-bcm1480.c
===================================================================
--- lmo.orig/arch/mips/pci/pci-bcm1480.c	2005-10-19 22:34:13.000000000 -0700
+++ lmo/arch/mips/pci/pci-bcm1480.c	2005-10-19 22:34:13.000000000 -0700
@@ -232,6 +232,14 @@
 		bcm1480_bus_status |= PCI_BUS_ENABLED;
 	}
 
+	/* turn on ExpMemEn */
+	cmdreg = READCFG32(CFGOFFSET(0, PCI_DEVFN(PCI_BRIDGE_DEVICE, 0), 0x40));
+	printk("PCIFeatureCtrl = %x\n", cmdreg);
+	WRITECFG32(CFGOFFSET(0, PCI_DEVFN(PCI_BRIDGE_DEVICE, 0), 0x40),
+			cmdreg | 0x10);
+	cmdreg = READCFG32(CFGOFFSET(0, PCI_DEVFN(PCI_BRIDGE_DEVICE, 0), 0x40));
+	printk("PCIFeatureCtrl = %x\n", cmdreg);
+
 	/*
 	 * Establish mappings in KSEG2 (kernel virtual) to PCI I/O
 	 * space.  Use "match bytes" policy to make everything look

      parent reply	other threads:[~2005-10-20  7:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-20  6:53 [PATCH 0/12] bcm1480 support Andrew Isaacson
2005-10-20  6:54 ` [PATCH 1/12] sibyte-fixes Andrew Isaacson
2005-10-20  6:55 ` [PATCH 2/12] 1480-headers Andrew Isaacson
2005-10-20  6:55 ` [PATCH 3/12] sibyte-header-cleanup Andrew Isaacson
2005-10-20  6:56 ` [PATCH 4/12] sb1a-support Andrew Isaacson
2005-10-20  6:56 ` [PATCH 5/12] 1480-support Andrew Isaacson
2005-10-20  6:57 ` [PATCH 6/12] bigsur-support Andrew Isaacson
2005-10-20  6:57 ` [PATCH 7/12] sb1-cache-exc-handling Andrew Isaacson
2005-10-20  6:57 ` [PATCH 8/12] cerr-printk-not-prom-printf Andrew Isaacson
2005-10-20 10:49   ` Ralf Baechle
2005-10-20 11:02     ` Dominic Sweetman
2005-10-20 11:17       ` Ralf Baechle
2005-10-20  6:58 ` [PATCH 9/12] sbmac-fixes Andrew Isaacson
2005-10-20  6:58 ` [PATCH 10/12] 1480-pci-support Andrew Isaacson
2005-10-20  6:59 ` [PATCH 11/12] 1480-ht-support Andrew Isaacson
2005-10-20  6:59 ` Andrew Isaacson [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=20051020065946.GL23899@broadcom.com \
    --to=adi@broadcom.com \
    --cc=linux-mips@linux-mips.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