Continuing the discussion from here: https://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&topic_id=43330&forum=16&start=600&viewmode=flat&order=0#881001

@Hammer

Quote:

Hammer wrote: @ppcamiga1 Quote: ppcamiga1 wrote: if you using pistorm you are idiot because you may have the some for zero euro just use winuae on pc FYI, there are plans for PPC emulation with Emu68 since it has unused CPU cores.

You don't need an extra core only for it. Even with the PowerPC acceleration cards for Amigas, only a single CPU is used at the same time (the 68k was put on hold when the PowerPC was running).

Extra cores can be used for additional tasks (e.g.: offloading tasks to the host system, or optimizing code hot spots), but certainly not for emulating multiple CPUs in parallel (at least for the Emu68 scope / how it workds).
Quote:

AArch64's big-endian mode and 32 GPR programming model have less translation overhead when compared to little-endian/16 GPR X86-64's PPC emulation. AArch64 can match PPC on arithmetic operations and the discrete load-store RISC instruction model.

I doubt that the MOVBE instruction is used on (Win)UAE JIT, and here a good performance boost can come.

Besides that, x86-64 has other advantages compared to AArch64: load-op, op-store, rep instructions, and especially large immediates support. So, the CISC way -> it's easier to mimick the 68k code execution, and it's also more efficient (less pipeline stalls due to depending, less instructions executed).

@cdimauro

Well, since we're talking 68K emulation, I'll just leave this here: https://github.com/0xABADCAFE/68PHPhousand

_________________
Doing stupid things for fun...

@cdimauro

Quote:

You don't need an extra core only for it. Even with the PowerPC acceleration cards for Amigas, only a single CPU is used at the same time (the 68k was put on hold when the PowerPC was running).

Go argue with Emu68's author.

Using another CPU core has its own L1 cache and register storage. It's unwise to add extra workload on the 68K role CPU core's L1 cache and register storage.

Are you arguing for unloading 68K instructions from the primary CPU's L1 cache/registers with PPC instructions?

Emu68's speed is about single-tasking without being disturbed by other workloads from a hosted Linux OS. Context switching has a cost.

Current Emu68 is using two CPU cores i.e. one for 68K translation and one for I/O. Debug uses another CPU core.

Last edited by Hammer on 08-Sep-2025 at 06:45 PM.
Last edited by Hammer on 08-Sep-2025 at 06:42 PM.
Last edited by Hammer on 08-Sep-2025 at 06:39 PM.
Last edited by Hammer on 08-Sep-2025 at 06:36 PM.
Last edited by Hammer on 08-Sep-2025 at 06:32 PM.
Last edited by Hammer on 08-Sep-2025 at 06:25 PM.

_________________

@Hammer

could use a third core for chipset emulation too if he added that

_________________

Quote:

Mobileconnect wrote: could use a third core for chipset emulation too if he added that

That would be more than a 68k emulation.

But I like the idea of having a chipset emulation on a free CPU core, maybe someone can offload some GFX operations to a free core.

@cdimauro

Quote:

I doubt that the MOVBE instruction is used on (Win)UAE JIT, and here a good performance boost can come. Besides that, x86-64 has other advantages compared to AArch64: load-op, op-store, rep instructions, and especially large immediates support. So, the CISC way -> it's easier to mimick the 68k code execution, and it's also more efficient (less pipeline stalls due to depending, less instructions executed).

I already know about x86-64's fused memory + ALU operations advantage for 68K emulation, but my comment is about the PPC plan for AArch64-based Emu68.

I already have an AmigaOS 4.1 FE license.

_________________

forget about emu something
install linux and qemu on rpi

@Karlos

Quote:

Karlos wrote: @cdimauro Well, since we're talking 68K emulation, I'll just leave this here: https://github.com/0xABADCAFE/68PHPhousand

Well, definitely not LOL.

But it looks strange to see PHP used for it.

@Hammer

Quote:

Hammer wrote: @cdimauro Quote: You don't need an extra core only for it. Even with the PowerPC acceleration cards for Amigas, only a single CPU is used at the same time (the 68k was put on hold when the PowerPC was running). Go argue with Emu68's author.

Michal is an active user of this forum, so I expect that he shows up, but likely you misunderstand something.
Quote:

Using another CPU core has its own L1 cache and register storage. It's unwise to add extra workload on the 68K role CPU core's L1 cache and register storage. Are you arguing for unloading 68K instructions from the primary CPU's L1 cache/registers with PPC instructions?

No. I'm simply telling that Amiga's PowerPC accelerator boards froze the 68k CPU in the system, and took full control.

Since the 68k CPU is frozen, you do NOT need, at all, to emulate / take care of is, and definitely you don't need to use & reserved a (completely idle) core just for it.
Quote:

Emu68's speed is about single-tasking without being disturbed by other workloads from a hosted Linux OS. Context switching has a cost.

Emu68 is bare metal, so there's no Linux neither any other OS, and it fully owns / takes care of all resources in the system.
Quote:

Current Emu68 is using two CPU cores i.e. one for 68K translation and one for I/O. Debug uses another CPU core.

That's not a problem and it's welcome, so that the emulation core can be fully busy with its own task.

@OneTimer1

Quote:

OneTimer1 wrote: Quote: Mobileconnect wrote: could use a third core for chipset emulation too if he added that That would be more than a 68k emulation. But I like the idea of having a chipset emulation on a free CPU core, maybe someone can offload some GFX operations to a free core.

Like WinUAE.

However, emulating the entire chipset is a completely different thing, and will make totally useless (and not needed) the Amiga in the PiStorm (so, effectively going in the Hamster direction / thesis).

Quote:

cdimauro wrote: ... emulating the entire chipset is a completely different thing, and will make totally useless (and not needed) the Amiga in the PiStorm ...

It doesn't matter where but an emulation needing the original hardware, is doomed in the long run.

@cdimauro

Unlike WinUAE, the 68k can communicate directly with the PiStorm hardware. In both cases, AmigaOS still provides audio, graphics, and internet, but through different means.

_________________
Indigo 3D Lounge, my second home.
The Illusion of Choice | Am*ga

@pixie

WinUAE supports SCSI emulation, you access HD directly.
I believe Warp3D emulation also provided some native x86 routines.
BSDSocket emulation provided transparent layer to the host TCP/IP stack.

Last edited by NutsAboutAmiga on 10-Sep-2025 at 07:48 PM.
Last edited by NutsAboutAmiga on 10-Sep-2025 at 07:47 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@cdimauro

Quote:

cdimauro wrote: @Karlos Quote: Karlos wrote: @cdimauro Well, since we're talking 68K emulation, I'll just leave this here: https://github.com/0xABADCAFE/68PHPhousand Well, definitely not LOL. But it looks strange to see PHP used for it.

Yeah, it was a bit of a "why not" moment.

_________________
Doing stupid things for fun...

@NutsAboutAmiga

Indeed, but these seem to be accessed through an abstraction layer, that's what I meant by other means.

_________________
Indigo 3D Lounge, my second home.
The Illusion of Choice | Am*ga

@ppcamiga1

Quote:

ppcamiga1 wrote: forget about emu something install linux and qemu on rpi

Why would I want to do that? I want to use my physical Amiga itself.

_________________
Live Long and keep Amigaing!

A1200, Power Tower, TF1260 128MB RAM, 68060 Rev 6, OS3.9 BB2, HD-Floppy, Mediator TX+ PCI, Voodoo 3 3000, Soundblaster 4.1, TV Card, Spider USB, 100MBit Ethernet, 16GB CF HD, 52xCDRom.

it is no longer amiga.
pistorm changes your amiga into keyboard interface for rpi.

if you using pistorm you are idiot because you may have the some for zero euro
just use winuae on pc

Last edited by ppcamiga1 on 11-Sep-2025 at 01:31 PM.

@ppcamiga1

You are just a LIAR.

@ppcamiga1

Quote:

ppcamiga1 wrote: it is no longer amiga. pistorm changes your amiga into keyboard interface for rpi. if you using pistorm you are idiot because you may have the some for zero euro just use winuae on pc

Again I ask you to show good faith that you are not a troll by backing up your assertions with evidence.

Please explain to me how a piStorm/Emu68 does what you are saying (without just repeating the same sentences, actually explain it). Your obvious dodging of the question on the few occasions I have asked would appear to indicate you are either lying, trolling, completely misunderstanding or a combination of these regards piStorm & Emu68.

_________________
Live Long and keep Amigaing!

A1200, Power Tower, TF1260 128MB RAM, 68060 Rev 6, OS3.9 BB2, HD-Floppy, Mediator TX+ PCI, Voodoo 3 3000, Soundblaster 4.1, TV Card, Spider USB, 100MBit Ethernet, 16GB CF HD, 52xCDRom.

@ppcamiga1

Quote:

ppcamiga1 wrote: it is no longer amiga. pistorm changes your amiga into keyboard interface for rpi.

I have a PiStorm in my A1000.
I still use it with an 1084 monitor attached to the RGB output.
I still use the floppy drives.
I still use the parallel port.
I still use the serial port.
I still use original keyboard, mouse and joysticks.
I still have the 512kB chipram limitation.

However, it is now a much more useful system, since it has a lot more ram and much faster CPU.

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC