From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 25 Apr 2003 02:58:33 +0100 (BST) Received: from gateway-1237.mvista.com ([IPv6:::ffff:12.44.186.158]:59125 "EHLO orion.mvista.com") by linux-mips.org with ESMTP id ; Fri, 25 Apr 2003 02:58:32 +0100 Received: (from jsun@localhost) by orion.mvista.com (8.11.6/8.11.6) id h3P1wT429947; Thu, 24 Apr 2003 18:58:29 -0700 Date: Thu, 24 Apr 2003 18:58:29 -0700 From: Jun Sun To: Pete Popov Cc: baitisj@evolution.com, Linux MIPS mailing list , jsun@mvista.com Subject: Re: Au1500 PCI autoconfig issues with multiple PCI devices? Message-ID: <20030424185829.C29809@mvista.com> References: <20030424114832.O10148@luca.pas.lab> <20030424121140.G28275@mvista.com> <20030424130459.P10148@luca.pas.lab> <1051215131.511.659.camel@zeus.mvista.com> <20030424184817.B29809@mvista.com> <1051235666.29988.20.camel@adsl.pacbell.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1051235666.29988.20.camel@adsl.pacbell.net>; from ppopov@mvista.com on Thu, Apr 24, 2003 at 06:54:26PM -0700 Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 2189 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: jsun@mvista.com Precedence: bulk X-list: linux-mips On Thu, Apr 24, 2003 at 06:54:26PM -0700, Pete Popov wrote: > On Thu, 2003-04-24 at 18:48, Jun Sun wrote: > > 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. > > There is support for type 1 accesses in > arch/mips/au1000/common/pci_ops.c. Maybe you were looking at the pb1000 > pci routine which had limited pci bus support in an fpga. Ahh, yes. That is the first config access routine I saw in the file and thus draw the conclusion. :) Jun