Re: Problems with devices that use PCI shared memory on 2nd PCI bus (6 slot powermac)

Re: Problems with devices that use PCI shared memory on 2nd PCI bus (6 slot powermac)

[Bob Brose]

Ben Wrote:
> On Wed, 2007-01-10 at 15:05 +0000, Bob Brose wrote:
> > Since Ben fixed the irq routing on 32 bit powermacs with changes to pci_32.c
> > and prom_parse.c I've been able to use all 6 slots with interrupt
> > driven devices however there appears to be a problem with devices that use
> > memory mapping. (this is on a S900 w/ 21052 second PCI controller)
> >
> > A couple of examples:
> > When using a 21143 tulip ethernet card on the second PCI bus and with the
> > "Use PCI shared mem for NIC registers" option turned on the driver
> > fails with incorrect status register reads. If I compile a kernel without
> > this option it works fine.
> >
> > Also, if I put a rage 128 video board in one of the slots on the
> > second bus it cannot do DRM. If I turn DRM off it works ok or if I move the
> > card to the first bus it works fine with DRM.
> 
> In lspci -vv, do you see the BusMaster bit enabled on the PCI-2-PCI
> bridge ?
> 
> Ben.

Yes. Here is the lspci -vv for the 21052:

00:0f.0 PCI bridge: Digital Equipment Corporation DECchip 21052 (rev 01) (prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32, Cache Line Size: 32 bytes
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 00001000-00001fff
        Memory behind bridge: 80800000-808fffff
        Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR+
        BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-


Bob

Problems with devices that use PCI shared memory on 2nd PCI bus (6 slot powermac)

[Bob Brose]

Since Ben fixed the irq routing on 32 bit powermacs with changes to pci_32.c
and prom_parse.c I've been able to use all 6 slots with interrupt
driven devices however there appears to be a problem with devices that use
memory mapping. (this is on a S900 w/ 21052 second PCI controller)

A couple of examples:
When using a 21143 tulip ethernet card on the second PCI bus and with the 
"Use PCI shared mem for NIC registers" option turned on the driver
fails with incorrect status register reads. If I compile a kernel without
this option it works fine.

Also, if I put a rage 128 video board in one of the slots on the
second bus it cannot do DRM. If I turn DRM off it works ok or if I move the
card to the first bus it works fine with DRM.

drmOpenByBusid: Searching for BusID pci:0000:01:0f.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: drmOpenMinor returns 9
drmOpenByBusid: drmGetBusid reports pci:0000:01:0f.0
.
.
(EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025
(EE) R128(0): Idle timed out, resetting engine...
(II) AIGLX: Suspending AIGLX clients for VT switch
(EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025
(EE) R128(0): Idle timed out, resetting engine...
(II) Generic Mouse: ps2EnableDataReporting: succeeded
(II) R128(0): [drm] removed 1 reserved context for kernel
(II) R128(0): [drm] unmapping 8192 bytes of SAREA 0xe6107000 at 0x30020000

Bob

Re: Problems with devices that use PCI shared memory on 2nd PCI bus (6 slot powermac)

[Benjamin Herrenschmidt]

On Wed, 2007-01-10 at 15:05 +0000, Bob Brose wrote:
> Since Ben fixed the irq routing on 32 bit powermacs with changes to pci_32.c
> and prom_parse.c I've been able to use all 6 slots with interrupt
> driven devices however there appears to be a problem with devices that use
> memory mapping. (this is on a S900 w/ 21052 second PCI controller)
> 
> A couple of examples:
> When using a 21143 tulip ethernet card on the second PCI bus and with the 
> "Use PCI shared mem for NIC registers" option turned on the driver
> fails with incorrect status register reads. If I compile a kernel without
> this option it works fine.
> 
> Also, if I put a rage 128 video board in one of the slots on the
> second bus it cannot do DRM. If I turn DRM off it works ok or if I move the
> card to the first bus it works fine with DRM.

In lspci -vv, do you see the BusMaster bit enabled on the PCI-2-PCI
bridge ?

Ben.