From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: Re: multiple separate pci bridges ...
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Reply-To: benh@kernel.crashing.org
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
In-Reply-To: <20040104210335.GA858@iliana>
References: <20040101181145.GA27294@iliana>
	 <1073016223.1502.179.camel@gaston> <20040102074049.GA2032@iliana>
	 <1073029796.1501.228.camel@gaston>  <20040104210335.GA858@iliana>
Content-Type: text/plain
Message-Id: <1073252724.780.5.camel@gaston>
Mime-Version: 1.0
Date: Mon, 05 Jan 2004 08:45:24 +1100
Sender: owner-linuxppc-dev@lists.linuxppc.org
List-Id: <linuxppc-dev@lists.linuxppc.org>


> PCI: Probing PCI hardware
> Scanning bus 00
> Found 00:00 [11ab/6460] 000600 00
> Found 00:08 [1106/3044] 000c00 00
> Found 00:28 [1000/0001] 000100 00
> Found 00:60 [1106/8231] 000601 00
> Found 00:61 [1106/0571] 000101 00
> Found 00:62 [1106/3038] 000c03 00
> Found 00:63 [1106/3038] 000c03 00
> Found 00:64 [1106/8235] 000000 00
> Found 00:65 [1106/3058] 000401 00
> Found 00:66 [1106/3068] 000780 00
> Found 00:68 [1106/3065] 000200 00
> Fixups for bus 00
> Bus scan for 00 returning with max=00
> Scanning bus 10
> Fixups for bus 10
> Bus scan for 10 returning with max=10
> PCI: Cannot allocate resource region 4 of device 00:00.0
>
> So, the 0x10 incrementation is fine, but the agp bus is not working
> correctly, and thus the agp graphic card not recognized (and thus no
> radeonfb).
>
> That said, i believe the 00:00.0 (should that not be 10:00.0 because of
> the renumbering) is the Marvell Discovery II pci controller, and the
> actual agp card should be found just behind.

What video card is this ?

It's possible that your config ops for the AGP don't work properly. Make
sure you are really generating type 0 config cycles.

Also, this "cannot allocate resource region" smells bad. Can
you check what the BARs of the host bridge are supposed to mean ?

I hope it's not yet another brain dead bridge that puts the system memory
in a BAR... in which case we'll have to "hide" it from linux PCI subsystem.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/