Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
111 user(s) are online (72 user(s) are browsing Forums)

Members: 0
Guests: 111

more...

Support us!

Headlines

 
  Register To Post  

(1) 2 3 4 ... 10 »
Pegasos2 with RadeonHD/RX via bridge
Home away from home
Home away from home


See User information
@All
Because balaton who works on QEMU create alternative boot loader instead of amigaos.of, allowing more control, output and necessary fixes so OS4 pegasos2's kernel will be happy with modern cards, i give it a go to try it all on real pegasos2.

So, i ordered 2 different PCI to PCIe bridges, and the first one arrived today, the one with "PEX 8112" chip, named : "PCI/PCI Express X16 adapter PXE8112"

That how it looks like (1-minute short video):





When i attach this thing to the pegasos2 (without a graphics card firstly, just an adapter), then, bboot show me that:

BBoot 0.4 (24.7.2023)
/
pci@80000000io fe000000/10000 mem 80000000/40000000
/pci@80000000/host:     0:0.0   11ab:6460 60000 646011ab 0100 6
/pci@80000000/firewire0:1.0   1106:3044 c0010 30441106 0109 0
  2000810        0 80010000         0      800  
80010000
  1000814        0 fe001080         0       80  
| 00001081
/
pci@80000000/pci:      0:6.0   10b5:8112 60400 811210b5 0100 7
Truncated 64 bit BAR 43003010
 42003010        0 80000000         0    10000  
8000000c
/pci@80000000/isa:      0:c.0   1106:8231 60100 82311106 0000 7
/pci@80000000/ide:      0:c.1   1106:0571 1018f 05711106 010e 7
  1006110        0 fe001000         0        8  
00001001
  1006114        0 fe00100c         0        4  
0000100d
  1006118        0 fe001010         0        8  
00001011
  100611c        0 fe00101c         0        4  
0000101d
  1006120        0 fe001020         0       10  
00001021
/pci@80000000/usb:      0:c.2   1106:3038 c0300 30381106 0409 7
  1006220        0 fe001040         0       20  
00001041
/pci@80000000/usb:      0:c.3   1106:3038 c0300 30381106 0409 7
  1006320        0 fe001060         0       20  
00001061
/pci@80000000/other:    0:c.4   1106:8235 68000 82351106 0000 0
/pci@80000000/sound:    0:c.5   1106:3058 40100 30581106 0309 0
  1006510        0 fe001100         0      100  
00001101
  1006514        0 fe001030         0        4  
00001031
  1006518        0 fe001034         0        4  
00001035
/pci@80000000/pci1106,3068:     0:c.6   1106:3068 78000 30681106 0309 0
  1006610        0 fe001200         0      100  
00001201
/pci@c0000000io f8000000/10000 mem c0000000/20000000
/pci@c0000000/host:     0:0.0   11ab:6460 60000 646011ab 0100 7
/pci@c0000000/display:  0:8.0   1002:5960 30000 ffffffff ffff ffff
 42004010        0 c0000000         0  8000000  
ffffffff
  1004014        0 f8001000         0      100  
ffffffff
  2004018        0 c8000000         0    10000  
ffffffff
  2004030        0 c8020000         0    20000  
ffffffff
/pci@c0000000/display:  0:8.1   1002:5940 38000 ffffffff ffff ffff
 42004110        0 d0000000         0  8000000  
ffffffff
  2004114        0 c8010000         0    10000  
ffffffff



As can be seen, the new things about this adapter are those:

/pci@80000000/pci:      0:6.0   10b5:8112 60400 811210b5 0100 7
Truncated 64 bit BAR 43003010
 42003010        0 80000000         0    10000  
8000000c


Dunno if "Truncated 64 bit BAR 43003010" are correct thing or not..

Also, what can be interesting is that firewire string change one address. I.e., without adapter we have:

/pci@80000000/firewire0:1.0   1106:3044 c0010 30441106 0109 0
  2000810        0 80000000         0      800  
80000000
  1000814        0 fe001080         0       80  
| 00001081


And when attach pci-2-pcie, then this changes on:

/pci@80000000/firewire0:1.0   1106:3044 c0010 30441106 0109 0
  2000810        0 80010000         0      800  
80010000
  1000814        0 fe001080         0       80  
| 00001081


See, 80000000 vs 80010000. But that probably just a relayout of memory map because of new things added.

In the Ranger, it showed as "PCI to PCI bridge" with such values:

ID Bus 0x00 Device : 0x06 Function 0x00
Class Base: 0x06 Sub: 0x04 IFae: 0x00 (PCI-to-PCI Bridge)
Device 0x8112 Rev: 0xAA (N/A)
Vendor 0x10B5 (N/A)
Header Type Bridge
Cacheline Size 0 bytes
Status CapList 66MHZ MedDevSel
Capabilities BusMaster intercard
Command IO Mem Master Int
Interrupt Line: 0x00 Pin: A Number: 16

Resource Ranges with Base/Psysical/Size/Flags all empty, the same as for all pegasos2's Bridges.

Next, i tried to put RadeonHD 270 in (the one which not require additional power).

The result of bboot are absolutely the same. I can't see anything new added, except of PCI2PCI bridge strings. But, what is interesting, when i run Ranger after booting, then, in the “Resource Ranges” it did have now :

Base: 0x80000000
Physical: 0x80000000
Size: 65536
Flags: PreFetch Mem

But no other device in the whole PCI Bus list.

Booting with default amigaboot.of , do not show anything in “resource ranges” , so bboot does something which at least show some more things when card is added.

Anyway.. the Fan of GFX card is spinning, so it definitely “works” from electricity side. But maybe as geennaam says before, I still need additional adapter to add more power to it, dunno.

I think one side is to made drivers for RadeonHD and kernel works, etc., but another one, is that in Ranger and in bboot output we probably should see something else when attach a GFX card to ?


Any ideas of how to go further are welcome !


Edited by kas1e on 2023/7/24 19:45:03
Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Quite a regular
Quite a regular


See User information
@kas1e
The change in firewire memory BAR address is because the PCI bridge memory BAR was mapped before it as you can see from the numbwers. This is OK, it just means the firmware found the bridge first and allocated space for it then went on with the other devices which then moved further up.

All this was done by the pegasos2 firmware, the only change bboot did was the "Truncated 64 bit BAR" and it also printes that it changed 43003010 that the firmware put there to 42003010 but now we don't change the register value which is 8000000c and still has the 64 bit type. This chnage was found to be needed at least for graphics cards to avoid the error about SS==3 because it looks like pegasos2 AmigaOS kernel can't handle 64bit bars but presenting them as 32 bit may work. Otherwise these did not show up in Ranger. You can test that by booting with amigaboot.of instead of bboot and see if the bridge is seen by AmigaOS then.

Now BBoot does not scan devices on PCI bus, only looks at what the firmware found so the firmware found the bridge but did not try to do anything with that. I think AmigaOS can handle some bridges but then you should enable debug logs and check what it says about this bridge. Maybe @Hans can tell more about what bridges should work or if it could work if we add a driver for the bridge in BBoot and enumerate devices from that. So far at least the first step seems to be sone that the brisge shows up in AmigaOS.

So check if booting with amigaboot.of is the same to see if BBoot is needed at all other than getting info from the devices and check in AmigaOS logs (maybe even using kernel.debug) to see if there are any more errors there.

By the way BBoot will skip this PCI part if p is missing from Acrions so if you use Ab instead of the default Apb then it's about the same as booting with amigaboot.of and nothing will change in PCI configs where the only change now is the 64 bit BAR identifier in device tree to avoid the kernel error and make the BAR apprear for AmigaOS.

Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Just can't stay away
Just can't stay away


See User information
@kas1e
Check https://www.amigaportal.cz/node/159407 with google translate, you probably have to add the same changes which are done in U-Boot on the AmigaOne XE in the SmartFirmare of the Pegasos2 to make it work.
They tested it with a P17C9X bridge (working) and a PEX8111 bridge (not working), no idea if using a PEX8112 instead of PEX8111 would have worked.

Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Home away from home
Home away from home


See User information
@balaton
Quote:

So check if booting with amigaboot.of is the same to see if BBoot is needed at all other than getting info from the devices and check in AmigaOS logs (maybe even using kernel.debug) to see if there are any more errors there.


So far all i see currently it's with bboot and amigaboot.of all the same: bridge can be seen, just with only differences that in Ranger tool after booting with bboot i do have some more info about memory layouts with attached gfx card. With amigaboot.of have nothing..

But i can't see gfx card attached to it anyway, so will try first with power-risers , maybe this adapter just not powered enough to deal with radeonhd (even if my radeonhd not need external power).

Quote:

By the way BBoot will skip this PCI part if p is missing from Acrions so if you use Ab instead of the default Apb then it's about the same as booting with amigaboot.of and nothing will change in PCI configs where the only change now is the 64 bit BAR identifier in device tree to avoid the kernel error and make the BAR apprear for AmigaOS.


Currently i am on defaults, so to see how this bridge will react.

Quote:

Yeah, long ago on reading and re-reading it :) Sailor (author) there as well, he commented from time to time. The P17C9X one i will receive in the next 10 days only, so only PEX8112 for tests now ...

Quote:

you probably have to add the same changes which are done in U-Boot


You mean interrupt related ones ? Not sure if OF give ability to do so ?


Edited by kas1e on 2023/7/24 22:04:51
Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Not too shy to talk
Not too shy to talk


See User information
@kas1e
Some years ago I tested PCI-PCIe bridge Pex 8111 + PCIe graphics card + MorphOS with no success - i.e no graphics output.
I don't remember the details
Only that original PCI card HD4350 worked. No output from Open firmware, but after boot to MorphOS it worked. I have no AmigaOS this time.
In real this is no PCI gfx chip, but PCIe chip RV710 with PEX 8112 incorporated on card.

I don't remeber what PCIe cards I tested, but geennaam advice about power supply is reasonable - I am using such PCIe x1 - PCIe x16 powered adapter in Sam440ep-flex.

I have in plan check more modern graphics in Pegasos 2 too. But later - now I have in queue upgrade of Powermac G4 CPUs.
But if testing will be succesfull, I have another step:

PCI slots in Pegasos 2 are 33 MHz - i.e. slow. But Pegasos has also AGP connector. In real, it is not AGP bus, but PCI 66 MHz bus connected to AGP connector. So all card works here in PCI mode. (Marwel Discovery Northbridge has no AGP, but two PCI host bridges). So I will try this one:
Resized Image


this is AGP-PCI adapter, of course not works on real AGP bus, but on such "PCI mode" AGP like Pegasos has.

If you succesfully tested card in 33 MHz slot, here is link to adapter.
But have in mind, that it doesn't have to work - AGP connector mised LOCK signal, which some PCI cards needs. If PCI-PCIe bridge needs it, I don't know.

AmigaOS3: Amiga 1200
AmigaOS4: Micro A1-C, AmigaOne XE, Pegasos II, Sam440ep, Sam440ep-flex, AmigaOne X1000
MorphOS: Efika 5200b, Pegasos I, Pegasos II, Powerbook, Mac Mini, iMac, Powermac Quad
Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Not too shy to talk
Not too shy to talk


See User information
@kas1eQuote:
kas1e wrote:
Quote:

Yeah, long ago on reading and re-reading it :) Sailor (author) there as well, he commented from time to time. The P17C9X one i will receive in the next 10 days only, so only PEX8112 for tests now ...

yes, she is here

Quote:
Quote:

you probably have to add the same changes which are done in U-Boot

You mean interrupt related ones ? Not sure if OF give ability to do so ?


It concerns only AmigaOne firmware, there is not correct PCI space initialization. This was only minor correction of interrupt and cache values. In any case, firmware should recognize the card behind the bridge at first - without it no correction helps.

On Pegasos 2 you made more detailed examinations than me. So I looking forward to next investigations, and sorry, I can help until sometime around October.

AmigaOS3: Amiga 1200
AmigaOS4: Micro A1-C, AmigaOne XE, Pegasos II, Sam440ep, Sam440ep-flex, AmigaOne X1000
MorphOS: Efika 5200b, Pegasos I, Pegasos II, Powerbook, Mac Mini, iMac, Powermac Quad
Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Home away from home
Home away from home


See User information
@sailor
Quote:

I don't remeber what PCIe cards I tested, but geennaam advice about power supply is reasonable - I am using such PCIe x1 - PCIe x16 powered adapter in Sam440ep-flex.

Yep, just additional adapter , because its PCIe X1... But i already ordered those ones, will see how it will looks like from Ranger when i will attach those.. At least we will know if it the same for both bridges, or one will be ok and another one will not.

Maybe i should try "power supply riser" for PEX one too ?

Quote:

this is AGP-PCI adapter, of course not works on real AGP bus, but on such "PCI mode" AGP like Pegasos has.

If you succesfully tested card in 33 MHz slot, here is link to adapter.


Yeah, that the one i want to test too, just wasn't able to find it on aliexpress. And yeah, this AGP on pegasos2 just PCI 66mhz, so, an adapter from AGP to PCI is pure "pin to pin" mostly, without any additional logic included.

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Quite a regular
Quite a regular


See User information
@kas1e

Years ago with the PEX 8112 and Sam440ep-flex, cards up to Radeon HD 6000 series worked. Could not get a Radeon HD7750 which was the lower end Radeon SI card to work .

By the way the PEX 8112 will work with one of the X5000's PCI slots to give an extra pciex1 slot if you can't get it to work with the Peg II.
Currently using mine on an X5000 with a pcix1 HD audio card.

Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Home away from home
Home away from home


See User information
@Spectre
Quote:

Years ago with the PEX 8112 and Sam440ep-flex, cards up to Radeon HD 6000 series worked.


But even with non-working cards, did you see them shower up in Ranger at all ? (i mean booting from other gfx card together with this one you test) ? Or you were use just single card, so if it show nothing on screen, then you mark it as non-working one ?

Also, did you use it with external power adapter to give more power to, or, as it ?


@all
I see there are risers for PCI1 to PCI16 everywhere, and the connector to the actual line is for PCI1 (a small one). Did i understand right, that i can use the same riser, and attach this small piece of PCI1 connector to the PCI16 ?

What i mean is that:
https://img.fruugo.com/product/5/90/232488905_max.jpg

Because my PEX8112 is PCIe16, not PCIe1, but i assume getting PCI1 to PCI16 will be ok and attach it like this, as all we need is 1 line, right ?


Edited by kas1e on 2023/7/24 22:06:57
Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Quite a regular
Quite a regular


See User information
BBoot would change an interrupt which is 0 or ff to 9 but only does that if it also assigned the addresses and won'f fix this for the case when running under pegasos2 firmware. I can change it to do that in that case too. But apart from that it seems we may also have a problem that if the pegaos2 firmware does not set up devices behind a bridge and AmigaOS only looks at devices that are set up by the firmware then it won't see the graphics card connected to the bridge unless BBoot would also do that. Is that the case or does AmigaOS try to drive the bridge and find devices behind it? I think @Hans said something about cards that have such bridge on them and the driver may work with it but maybe it's not the driver version indcluded in AmigaOS so I'm not sure what BBoot would have to do with these bridges. We need more data on what it looks like with current version with BBoot output, AmigaOS debug log and what can be seen in Ranger after boot and also if there's any info what the Driver needs the firmware (or in this case BBoot) to set up for it to be able to use tha card.

Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Quite a regular
Quite a regular


See User information
@kas1e

Was using a single card. so no display.
Serial Debug indicated an endless loop.
Power was as is . No external power .

Based on some later success of others with the P17C9X and external power one can probably narrow the issue down to either power or the PEX 8112 or both in the case of the Sam440ep.

Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Home away from home
Home away from home


See User information
@balaton
Quote:

But apart from that it seems we may also have a problem that if the pegaos2 firmware does not set up devices behind a bridge and AmigaOS only looks at devices that are set up by the firmware then it won't see the graphics card connected to the bridge unless BBoot would also do that. Is that the case or does AmigaOS try to drive the bridge and find devices behind it?


I think we will know for sure once i will test this PEX8112 based with power extender, and when i will test second adapter with PI7C9X111S chip in (with which most of ppls have success on SAM440 previously)

If everything still will be the same in all cases, be it PEX8112 with power adapter, or PI7C9X111S (with or without adapter), then we can think that this is something about firmware/hardware indeed.

Tomorrow i will receive power-riser, so at least we can check PEX8112 with it, and we can go further from this point..


EDIT: i also may try it in the X1000 or X5000 too, just to see how it configured (or not) via UBOOT, and how Ranger then looks like after i insert video card to it.

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Home away from home
Home away from home


See User information
@All
So i put this PEX8112 into X5000, to see how it will react: Firstly i put it without GFX card, then in Ranger i have a little more info to compare with the info i got from Pegasos2. That how it looks like in X5000:

ID Bus 0x06 Device : 0x04 Function 0x00
Class Base: 0x06 Sub: 0x04 IFace: 0x00 (PCI-to-PCI Bridge)
Device 0x8112 Rev: 0xAA (PEX81212x1 Lane PCI Express-to-PCI Bridge)
Vendor 0x10B5 (PLX Tecnology. Inc)
Header Type Bridge
Cacheline Size 32 bytes
Status CapList 66MHZ MedDevSel
Capabilities BusMaster intercard Bridge
Command IO Mem Master Int
Interrupt Line 0x05 Pin: A Number: 16

See, we have more info in Device, then Cacheline Size 32bytes and not 0 and Capabilities have an also "Bridge" word. Minor things probably, but still.

The “resource ranges” also empty.

Next, i attach RadeonHD to it (btw had to comment hda.device loading, as it crashes in this combo).

And it didn't showups inside of that bridge tab, but instead in the defaults bridges of X5000, which is:

ID Bus 0x04 Device : 0x03 Function 0x00
Class Base: 0x06 Sub: 0x04 IFace: 0x00 (PCI-to-PCI Bridge)
Device 0x8092 Rev: 0x02 (N/A)
Vendor 0x111D (Integrated Device Technology. Inc[IDT])
Header Type Bridge
Cacheline Size 32 bytes
Status CapList FastDevSel
Capabilities BusMaster intercard Bridge
Command IO Mem Master Int
Interrupt Line 0x00 Pin: None, Number: N/A

And in this tab i do have both VGA Controller + Audio Device of my card. That without external power-riser, but then, this is X5000 with it's PCIs and not Pegasos2 , as well as this is UBOOT and not OF.

Will try on X1000 as well: It didn't have UBOOT, but SmartFirmware, maybe will give some more light on.

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Just can't stay away
Just can't stay away


See User information
@kas1e
Quote:
See, we have more info in Device
vendor and device names? That's just from the pci.ids file.
You probably have an older one, or none, on the Pegasos2.
You can download the current version from https://pci-ids.ucw.cz/

Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Home away from home
Home away from home


See User information
@joerg
Quote:

vendor and device names? That's just from the pci.ids file.
You probably have an older one, or none, on the Pegasos2.
You can download the current version from https://pci-ids.ucw.cz/

Updated pci.ids on peg2 to the latest one, and even copy the same version of Ranger binary as on x5000 : and after reboot, it still shows the same "N/A" things.

I tried SysMon tool, and this one reads all correctly on Peg2. So it can be Ranger's general issue (or some os4 components)

@All
Interesting that when i go to the OF, and type:

cd /pci@80000000/pci@6
.properties


I had:

vendor-id             0x10B5 (4277)
device-id             0x8112 (33042)
revision-id           0xAA (170)
class-
code            0x60400 (394240)
subsystem-id          0x0 (0)
subsystem-vendor-id   0x0 (0)
.
vendor-name          "PLX"
.class                "Bridge Device"
.subclass             "PCI/PCI"
interrupts            0x1 (1)
devsel-speed          0x1 (1)
66mhz-capable
device_type           
"pci"
#address-cells        0x3 (3)
#size-cells           0x2 (2)
clock-frequency       0x1FCA055 (33333333)
name                  "pci"
reg                   6:0
                      xp6
,0,10,0:10000
assigned
-addresses    xp6,0,10,80000000:10000
bus
-range             1:1
ranges


Even OF know that vendor name is PLX :)

And that i have when i put RadeonHD in:

ok cd /pci@80000000/pci@6
ok 
.properties
vendor
-id             0x10B5 (4277)
device-id             0x8112 (33042)
revision-id           0xAA (170)
class-
code            0x60400 (394240)
subsystem-id          0x0 (0)
subsystem-vendor-id   0x0 (0)
.
vendor-name          "PLX"
.class                "Bridge Device"
.subclass             "PCI/PCI"
interrupts            0x1 (1)
devsel-speed          0x1 (1)
66mhz-capable
device_type           
"pci"
#address-cells        0x3 (3)
#size-cells           0x2 (2)
clock-frequency       0x1FCA055 (33333333)
name                  "pci"
reg                   6:0
                      xp6
,0,10,0:10000
assigned
-addresses    xp6,0,10,80000000:10000
bus
-range             1:1
ranges                
[0x40 bytes]
        [
00001000000 00000000 FE002000 01000000
        
[01000000000 FE002000 00000000 00001000
        
[02002000000 00000000 80100000 02000000
        
[03000000000 80100000 00000000 1FF00000

ok


So we can see that when video card added, the ranges surely added, so bridge do see that things inserted.


Edited by kas1e on 2023/7/25 8:22:16
Edited by kas1e on 2023/7/25 8:32:30
Edited by kas1e on 2023/7/25 16:51:36
Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Quite a regular
Quite a regular


See User information
@kas1e
I wanted to ask you to send .properties of that bridge to check its ranges property but you did that above already. What if you cd to /pci/pci and do ls? Does a display device node appear there? Then you can also get .properties of that to see how the firmware sees this. You could get all info from SmartFirmware with dump-all but that's too long to post here, maybe send it to me or upload somewhere. There's also a dump-pciconfig word in SmartFirmware but I don't know what that does but sounds like it can get some info from a card.

BBoot currently only lists devices attached to the internal PCI buses of Pegasos2, it won't go down in bridges. I'll need to change that but don't know yet how to access devices behind the bridge on pegasos2 so I'll also have to read some docs on these bridges. At least now I have the device node for the bridge so I can see if there's some info on this there.

Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Not too shy to talk
Not too shy to talk


See User information
@kas1e
Every PCI-PCIe bridge is in real PCIe x1.
Even if it has ×16 mechanical connector, electrically it is only x1. So you can connect x1 extender to x16 bridge connector with no slowdown.

And powered PCIe x1 - PCIe x16 adapter ( for minig rigs as geennam suggested ) is simple serial lines extension, totally passive. You not see it in Ranger.

AmigaOS3: Amiga 1200
AmigaOS4: Micro A1-C, AmigaOne XE, Pegasos II, Sam440ep, Sam440ep-flex, AmigaOne X1000
MorphOS: Efika 5200b, Pegasos I, Pegasos II, Powerbook, Mac Mini, iMac, Powermac Quad
Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Home away from home
Home away from home


See User information
@balaton
Quote:

What if you cd to /pci/pci and do ls? Does a display device node appear there?


ok cd /pci/pci
ok ls
display
@0
pci1002
,AAB0@0,1
ok


/pci/pci there is the same as /pci@80000000/pci@6
I just before forget to do "ls" inside as well, so didn't see display@0 and pci1002,AAB0@0,1


Then you can also get .properties of that to see how the firmware sees this:

for display@0:

ok cd display@0
ok 
.properties
vendor
-id             0x1002 (4098)
device-id             0x682B (26667)
revision-id           0x87 (135)
class-
code            0x30000 (196608)
subsystem-id          0x1043 (4163)
subsystem-vendor-id   0x7250 (29264)
.
vendor-name          "ATI"
.class                "Display Controller"
.subclass             "PC Compatible"
interrupts            0x1 (1)
devsel-speed          0x0 (0)
min-grant             0x0 (0)
max-latency           0x0 (0)
rom                   [0x20000 bytes]
        [
000FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[010FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[020FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[030FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[040FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[050FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[060FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[070FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[080] FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[090] FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[0A0FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[0B0FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[0C0FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[0D0FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[0E0FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[0F0FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[100FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[110FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[120FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[130FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[140FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[150FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[160FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[170FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[180FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[190FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[1A0FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[1B0FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[1C0FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[1D0FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[1E0FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
        
[1F0FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
[skipped]

name                  "display"
reg                   0:0
                      xp0
,0,10,0:10000000
                      x0
,0,18,0:40000
                      i0
,0,20,0:100
                      m0
,0,30,0:20000
assigned
-addresses    xp0,0,10,90000000:10000000
                      x0
,0,18,80100000:40000
                      i0
,0,20,FE002000:100
                      m0
,0,30,80140000:20000
ok



For pci1002,AAB0@0,1:

ok cd pci1002,AAB0@0,1
ok 
.properties
vendor
-id             0x1002 (4098)
device-id             0xAAB0 (43696)
revision-id           0x0 (0)
class-
code            0x40300 (262912)
subsystem-id          0x1043 (4163)
subsystem-vendor-id   0xAAB0 (43696)
.
vendor-name          "ATI"
interrupts            0x2 (2)
devsel-speed          0x0 (0)
min-grant             0x0 (0)
max-latency           0x0 (0)
name                  "pci1002,AAB0"
reg                   0,1:0
                      x0
,1,10,0:4000
assigned
-addresses    x0,1,10,80160000:4000
ok



Quote:

You could get all info from SmartFirmware with dump-all but that's too long to post here, maybe send it to me or upload somewhere.


full dump-all with bridge + inserted RadeonHD:
https://kas1e.mikendezign.com/pegasos2 ... h_bridge_and_radeonhd.txt


Quote:

There's also a dump-pciconfig word in SmartFirmware but I don't know what that does but sounds like it can get some info from a card.


It's like same like .properties looks like, you shoud inter to the directory to be able to have output from, so that the outputs:

/pci/pci:

ok cd /pci/pci
ok dump
-pciconfig
Package 0xFC5A818
        host bridge 
0
        bus 
0
        device 
6
        
function = 0
        header type 
1
        
class code 060400
        revision id 
AA
        vendor id 
10B5
        device id 
8112
        subsystem vendor id 
0000
        subsystem device id 
0000
        command 
0007
        status 
0230 [MED M66 CAP MASTE MEME IOE]
        
latency 00
        BIST 
01
        cache 
00
        BAR 0 
8000000C
        BAR 1 
00000000
        primary bus 
00
        secondary bus 
01
        subordinate bus 
01
        secondary latency 
00
        i
/o base 20
        i
/o limit 20
        secondary status 
2000
        memory base 
8010
        memory limit 
9FF0
        prefetch base 
FFF0
        prefetch limit 
FFE0
        prefetch64 base 
00000000
        prefetch64 limit 
00000000
        i
/o 32 base 0000
        i
/o 32 limit 0000
        boot ROM 
00000000
        interrupt line 
00
        interrupt pin 
01
        bridge control 
0000
ok



/pci/pci/display@0:

ok cd display@0
ok dump
-pciconfig
Package 0xFC5B3D0
        host bridge 
0
        bus 
1
        device 
0
        
function = 0
        header type 
0
        
class code 030000
        revision id 
87
        vendor id 
1002
        device id 
682B
        subsystem vendor id 
1043
        subsystem device id 
7250
        command 
0000
        status 
0010 [FAST CAP]
        
latency 00
        BIST 
80
        cache 
00
        BAR 0 
9000000C
        BAR 1 
00000000
        BAR 2 
80100004
        BAR 3 
00000000
        BAR 4 
00002001
        BAR 5 
00000000
        CIS 
00000000
        boot ROM 
80140000
        reserved 
@34 = 00000048
        
reserved @38 00000000
        interrupt 
= 00000109
ok


and /pci/pci/pci1002,AAB0@0,1:

ok cd pci1002,AAB0@0,1
ok dump
-pciconfig
Package 0xFC5B6F8
        host bridge 
0
        bus 
1
        device 
0
        
function = 1
        header type 
0
        
class code 040300
        revision id 
00
        vendor id 
1002
        device id 
AAB0
        subsystem vendor id 
1043
        subsystem device id 
AAB0
        command 
0000
        status 
0010 [FAST CAP]
        
latency 00
        BIST 
80
        cache 
00
        BAR 0 
80160004
        BAR 1 
00000000
        BAR 2 
00000000
        BAR 3 
00000000
        BAR 4 
00000000
        BAR 5 
00000000
        CIS 
00000000
        boot ROM 
00000000
        reserved 
@34 = 00000048
        
reserved @38 00000000
        interrupt 
= 00000209
ok

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Quite a regular
Quite a regular


See User information
@kas1e

In case you didn't know: 1002,AAB0 is the hdaudio soundcard endpoint for audio over HDMI or DP.

Go to top
Re: Pegasos2 with RadeonHD/RX via bridge
Home away from home
Home away from home


See User information
@balaton,geennaam
So, takin into account latest pciconfigs and what geennam says we do have pci bridge seen on pci@6 and radeonhd card witb hdaudio visibly too.

Question is : why os4 apps such as ranger and sysmon didnt see card ? I assume if it issues with BARs we still should see it as hardware with wrong memory regions,etc, right ? Or issues with bars can be resulted with os4 not see card as hardware at all ?

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top

  Register To Post
(1) 2 3 4 ... 10 »

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project