From: Jesse Barnes <jbarnes@engr.sgi.com>
To: "David S. Miller" <davem@davemloft.net>
Subject: Re: multi-domain PCI and sysfs
Date: Wed, 8 Sep 2004 11:32:28 -0700
User-Agent: KMail/1.7
Cc: jonsmirl@gmail.com, willy@debian.org, linux-kernel@vger.kernel.org
References: <9e4733910409041300139dabe0@mail.gmail.com> <200409080902.14640.jbarnes@engr.sgi.com> <20040908112027.545a6b2e.davem@davemloft.net>
In-Reply-To: <20040908112027.545a6b2e.davem@davemloft.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200409081132.29008.jbarnes@engr.sgi.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1081
Lines: 26

On Wednesday, September 8, 2004 11:20 am, David S. Miller wrote:
> On Wed, 8 Sep 2004 09:02:14 -0700
>
> Jesse Barnes <jbarnes@engr.sgi.com> wrote:
> > > Where is the PCI segment base address stored in the PCI driver
> > > structures? I'm still having trouble with the fact that the PCI driver
> > > does not have a clear structure representing a PCI segment.  Shouldn't
> > > there be a structure corresponding to a segment?
> >
> > That would be nice, maybe an extra resource or something?  I haven't
> > looked at the sparc code, but it probably deals with this (sn2 has
> > platform specific functions to get the base address for a bus).
>
> We store them directly in pci_resource_*(pdev,BAR_NUM) as physical
> addresses.

Oh, right, you have them stored in each bridge, right?  I should do the same 
thing for sn2...

Thanks,
Jesse
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/