Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: Pete Popov <ppopov@mvista.com>
Cc: baitisj@evolution.com,
	Linux MIPS mailing list <linux-mips@linux-mips.org>,
	jsun@mvista.com
Subject: Re: Au1500 PCI autoconfig issues with multiple PCI devices?
Date: Thu, 24 Apr 2003 18:48:17 -0700	[thread overview]
Message-ID: <20030424184817.B29809@mvista.com> (raw)
In-Reply-To: <1051215131.511.659.camel@zeus.mvista.com>; from ppopov@mvista.com on Thu, Apr 24, 2003 at 01:12:11PM -0700

On Thu, Apr 24, 2003 at 01:12:11PM -0700, Pete Popov wrote:
> 
> > Here's another question:
> 
> > What are the goals of the AU1500 PCI auto config? Is it supposed to be a full
> > implementation, or just enough to work with a PCI card? The reason I ask is
> > that the DBAu1500 has only one PCI slot, so a simple implementation would
> > normally suffice.
> > 
> > Restated: I don't know if the PCI auto config code was designed to work with
> > all sorts of wacky PCI devices. I don't know if the intention of the code is to
> > support the single PCI slot present on the DbAu1500 development board, or if it
> > is supposed to be more flexible (and complicated). 
> 
> The MIPS pci auto should work fine with a single PCI bus and it _should_
> be a full implementation. The code was ported from PPC some time ago,
> but sub busses were not tested.  

That is not true.  pciauto has been working P2P bridges pretty much since day one.

Usually sub-bus not working is due to type 1 configuration not supported
in pci ops, which is board-dependent code.

I took a brief look of au1x00 pci_ops and it appears it does not support type
1 configuration access.  See arch/mips/ddb5xxx/ddb5477/pci_ops.c for one
example on how type 1 configuration being supported.

Jun

  reply	other threads:[~2003-04-25  1:48 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
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 [this message]
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=20030424184817.B29809@mvista.com \
    --to=jsun@mvista.com \
    --cc=baitisj@evolution.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ppopov@mvista.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