Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: Jeff Baitis <baitisj@evolution.com>
Cc: linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: Au1500 PCI autoconfig issues with multiple PCI devices?
Date: Thu, 24 Apr 2003 12:11:40 -0700	[thread overview]
Message-ID: <20030424121140.G28275@mvista.com> (raw)
In-Reply-To: <20030424114832.O10148@luca.pas.lab>; from baitisj@evolution.com on Thu, Apr 24, 2003 at 11:48:32AM -0700

[-- Attachment #1: Type: text/plain, Size: 448 bytes --]



On Thu, Apr 24, 2003 at 11:48:32AM -0700, Jeff Baitis wrote:
> Hi ya'll:
> 
> This is the first time I've tried multiple PCI devices on the Au1500. I have a
> PCI->CardBus bridge and a 3Com ethernet plugged into the Au1500's PCI bus. I'm
> using the linux_2_4 branch.
>
<snip>

Try this patch and let me know the results.

BTW, I did not know Au1500 has a cardbus controller.  I was under impression
it is a PCMCIA controller.  Interesting.

Jun

[-- Attachment #2: junk --]
[-- Type: text/plain, Size: 596 bytes --]

diff -Nru link/arch/mips/kernel/pci_auto.c.orig link/arch/mips/kernel/pci_auto.c
--- link/arch/mips/kernel/pci_auto.c.orig	Thu Apr 10 14:13:57 2003
+++ link/arch/mips/kernel/pci_auto.c	Thu Apr 24 12:10:16 2003
@@ -354,8 +354,8 @@
 	 * configured by this routine to happily live behind a
 	 * P2P bridge in a system.
 	 */
-	pciauto_upper_memspc += 0x00400000;
-	pciauto_upper_iospc += 0x00004000;
+	pciauto_lower_memspc += 0x00400000;
+	pciauto_lower_iospc += 0x00004000;
 
 	/* Align memory and I/O to 4KB and 4 byte boundaries. */
 	pciauto_lower_memspc = (pciauto_lower_memspc + (0x1000 - 1))

  reply	other threads:[~2003-04-24 19:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24 18:48 Au1500 PCI autoconfig issues with multiple PCI devices? Jeff Baitis
2003-04-24 19:11 ` Jun Sun [this message]
2003-04-24 19:46   ` Pete Popov
2003-04-24 20:04   ` Jeff Baitis
2003-04-24 20:12     ` Pete Popov
2003-04-25  1:48       ` Jun Sun
2003-04-25  1:54         ` Pete Popov
2003-04-25  1:58           ` Jun Sun

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=20030424121140.G28275@mvista.com \
    --to=jsun@mvista.com \
    --cc=baitisj@evolution.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