Pegasos2 with RadeonHD/RX via bridge

Thank you @kas1e and @hans !

Thumbs up \ò/

I have an old R5 230 it will work ?

@Mabo
Quote:
Dunno, there is list of supported ones:

From readme of RadeonHD driver:



From aeon/amigakit's wiki:

@kas1e
R5 230 is included in https://www.acube-systems.biz/compatibility/compatibility_41.php as
not supported by AmigaOS 4.1 itself, but reported to be working with additional drivers.

@all
We a bit stuck with, maybe anyone have a clue where to look next.

Our problems currently are:
- Reading the graphics card's BAR registers always returns 0, even after we've written new value to them

- Possibly related, reading from the card's secondary function (i.e,. the audio sub-device) configuration register returns 0xFFFFFFFFF, including for its vendor/device ID.

Any ideas ?:)

@all

To clarify, the Pegasos II's firmware clearly managed to read the configuration registers properly, because the card appears in the PCI device tree. However, attempting to access the card's PCI configuration registers fails when the OS tries to do it (using OpenFirmware's PCI configuration access API). Clearly something went wrong between the firmware's PCI device scan, and the OS starting up...

Hans

@Hans
Is this with QEMU or on real machine with a bridge? If on QEMU is it using pegasos2.rom or with bboot? Can you boot Linux and check what that sees from the device? The lspci command has some options to dump the config regs so you can check with that what it sees. If this is through a bridge you may need to do something differently to access the other bus behind the bridge otherwise you may try to read device on the host bus not the bridge's bus so you'd get non-existing device that would return 0xff when you read it (which may be interpreted as 0 for BARs, I'm not sure). Maybe check some docs on how to handle PCI buses behind a bridge and check if the AmigaOS kernel does that correctly.

@balaton

Sorry, this is with a real machine. After the success with getting a RadeonRX working with QEMU + passthrough, kas1e wanted to see if we could get it working on a real Pegasos II.

We've kind of hit a brick wall. The OS & driver need to be able to access the PCI configuration registers, but they're not responding...

Quote:

The OS is using OpenFirmware's own callback function to access configuration registers. You tell it which domain, bus, & device you want to access, and it does it for you. That function is working with all other devices, but not with the graphics card behind the PCI to PCIe bridge. It reads zeros from the GPU's configuration registers, and 0xFFFFFFFF from the card's audio sub-device.

Hans