Re: AGP bogosities

[Bjorn Helgaas <bjorn.helgaas@hp.com>]

On Fri, 2005-03-11 at 08:39 -0800, Jesse Barnes wrote:
> On Thursday, March 10, 2005 8:30 pm, Benjamin Herrenschmidt wrote:
> > On Thu, 2005-03-10 at 20:02 -0800, Jesse Barnes wrote:
> > > On Thursday, March 10, 2005 6:38 pm, Benjamin Herrenschmidt wrote:
> > > > That one is even worse... from what I see in your lspci output, you
> > > > have no bridge with AGP capability at all, and the various AGP devices
> > > > are all siblings...
> > >
> > > Both of the video cards are sitting on agp busses in agp slots hooked up
> > > to host to agp bridges.
> > >
> > > > Are you sure there is any real AGP slot in there ?
> > >
> > > Yes :)
> >
> > Well, according to your lspci, none of the bridges exposes a device with
> > AGP capabilities...
> 
> There are no bridges listed in my lspci output, that's probably why. :)

HP ia64 and parisc boxes are similar.  The host bridges do not appear
as PCI devices.  We discover them via ACPI on ia64 and PDC on parisc.

> > It looks like you aren't exposing the host "self" 
> > device on the bus. Do you have an AGP driver ? If yes, it certainly
> > can't use any of the generic code anyway ...
> 
> Right, it's a special agp driver, sgi-agp.c.

Where's sgi-agp.c?  The HP (ia64-only at the moment) code is hp-agp.c.
It does make a fake PCI dev for the bridge because DRM still seemed to
want that.