Considering the RageMem results copying with simple CPU loop should not be slow as that's compiled to host code.

The DMA engine of the 460EX is just a memcpy or memmove in the optimised case or line by line copy if the region is not continuous.

I don't know what code path copy from VRAM goes through in QEMU

You shouldn't really need a SWAP partition. AmigaOS can only address 2GB RAM,

U-Boot 2010.06.05 (Jul 08 2018 - 22:45:33)

Remember to put them to the original values when done:

> NVSetVar stdin usbkbd
> NVSetVar stdout serial

First, the driver doesn't use GART on older systems like the pegasos-2, A1-XE, & Sam460 due to lack of memory coherency. I tried manual cache flushing/invalidation, but simply couldn't get it to work reliably. So, all commands are written to VRAM. Therefore, slow VRAM access means slower command submission.

Second, AmigaOS does a lot of CPU-based rendering. Far too much. This includes things such as drawing text and lines (other than horizontal or vertical). This will frequently involve both reading from and writing to VRAM.

Ouch! Those VRAM access stats are horrifically bad ...

(Just because compose.task shows up using CPU in your screen shot but I don't know what that does ot if it's related.)

I haven't tried the R5 230 card because I would think it's even weaker than the 5450

It is true, that a real PegasosII does not have a PCIe slot. Only PCI. My Radeon GPU is plugged into a PCIe slot because my motherboard is relatively new, so it does not have a PCI slot. I don't know if this contributes to the slow performance.

- RadeonHD cards may work but likely need the machine firmware to init the graphics card ...

- RadeonRX cards that have AtomBIOS but the guest firmware cannot run it may work with just -kernel bboot without -bios machine firmware, because the AmigaOS driver may be able to parse AromBIOS and init the card but this may not always or fully work ...

- R5 230 (I'll ignore this one. It was bought to try MOS. That didn't work and it's a very low performance card anyway that I don't think is supported by OS4)

BUT, is it not the case that I would need the V5 HD drivers for this Southern Islands based card?

Oland chipsets (HD R7 240/240D, HD R7 250) require the newer RadeonHD drivers (v1.20, v2.21 or v3.6) exclusively available from the Enhancer Software

An emulated graphics card or a driver for a real video card (PCI passthrough) is always missing.

Regarding SDI, looks like it was a bit too late for the 80's, being dated from this century.

But what does SDI mean? I read through that project years ago and unless I missed the obvious it doesn't say what it is. I think an acronym is rather pointless if it isn't explained on the first line of the readme.

That's still too complicated. Given a library call is like this without needing to think about it.

So it certainly could have been programmed in.

int32 hookFunc(struct Hook *hook, APTR object, APTR message)

The 68K ABI convention is also the same way as the native ABI also uses registers in API calls,

Quote:
But even on m68k most people didn't use that anymore but something like

Except in that case but it can be compiler specific.

int c_Write(void *handle, void *buf, int len)
{
int rc;
rc = fwrite(buf, 1, len, handle);
return (rc);
}