Pistorm32 showcase thread

[Mr-Z]

Originally Posted by Kin Hell

Isn't it just & really....

With a CM4 Module @ 2.3Ghz & running almost 2000 times fater than a Stock A1200, do you really need more?

Yes

[Kin Hell]

Originally Posted by Kin Hell

<snip>
With a CM4 Module @ 2.3Ghz & running almost 2000 times fater than a Stock A1200, do you really need more?

Originally Posted by Mr-Z

Yes

....of course of course!

More P O W E R !

[Karlos]

What we need is a way to expose the SIMD capabilities for things like datatpes, codecs and the like. Forget 2000 times faster....

[tomcat666]

Originally Posted by Karlos

What we need is a way to expose the SIMD capabilities for things like datatpes, codecs and the like. Forget 2000 times faster....

I think everything is already exposed... i.e. the actual RTG P96 display driver, the SD card driver, ... are already written completely in 68k code and use pi's hardware resources. Michal can explain it better

[VladR]

Do I understand this correctly that under Emu68k's RTG there is no CPU-vs-DMA interleaving issue (as there is no Amiga chipset being emulated) ?

Meaning the 68040 code runs at full possible speed of the single core of Cortex A-72 ?

Because that would make it an RTG monster...

Are all typical color depths (8,16,24,32) and RTG resolutions working there under P96 (800x600,1024x768,1280x1024,1600x1200) ?

[Dunny]

Originally Posted by VladR

Do I understand this correctly that under Emu68k's RTG there is no CPU-vs-DMA interleaving issue (as there is no Amiga chipset being emulated) ?

Correct, as far as I understand it. There is some issue with Chip RAM read speeds - it's too fast so has to be slowed down a touch in certain situations.

Meaning the 68040 code runs at full possible speed of the single core of Cortex A-72 ?

Correct. It's not a 68040 though, it just identifies as one.

Because that would make it an RTG monster...

Are all typical color depths (8,16,24,32) and RTG resolutions working there under P96 (800x600,1024x768,1280x1024,1600x1200) ?

Yes it is an RTG monster. I run my WB at 1920x1080x32 for example.

[VladR]

Originally Posted by Dunny

Correct, as far as I understand it. There is some issue with Chip RAM read speeds - it's too fast so has to be slowed down a touch in certain situations.

I reckon that only applies to legacy SW that wasn't written with 2500 MIPS in mind, right ?
ChipRam latency/bandwidth has certainly been a consideration (e.g. framebuffer/bitplane writes) on the poor old legacy HW, but goes out the window with Cortex A-72.

Originally Posted by Dunny

Correct. It's not a 68040 though, it just identifies as one.

Well, I've read recently that they just fixed some FPU-related bugs, so it leads me to believe it implements FPU instructions (maybe just a most-used subset, perhaps?) from 68040, right ?

Since a lot of older demos using FPU run fine already (especially after recent paraj's work), then Emu68k must be able to interleave Integer and FPU ops in parallel (just like regular 68040), correct ?

Do you perhaps mean that some parts of 040 instructions remain currently unimplemented (say, MMU, and some rarely-used ops, etc.) ?

[Dunny]

Originally Posted by VladR

Do you perhaps mean that some parts of 040 instructions remain currently unimplemented (say, MMU, and some rarely-used ops, etc.) ?

I'm no expert but I believe that's so.

[tomcat666]

Another milestone reached by Paraj... this time TBL - Eon demo perfectly working on pistorm32 ... 2500 MIPS 2.2Ghz amiga He even went so far to completely fix the cube part which was only ever meant to work on non-AGA amigas.

[ Show youtube player ]

[Angus]

Very cool.

[mahen]

Wow !

[specfreak]

Great stuff @tomcat666 @Dunny, looking forward to testing stuff on my recently purchased PiStorm/rpi3a+ (after my BPPC failed :-(). Has anyone tried any of the later RTG demos yet? Has anyone tested Pi/FPU against say the TF1230/60 that don't have FPU using SoftFPU vs a real FPU?

Also, it'll be interesting to see how it deals with the Speccy emulators. I can't remember if any need MMU, I'll soon find out. Can't remember if the Amiga port of x128 was 68k or PPC. I'm sure it was 68k tested on my 060 for Paul Hill back in the day.

My A1200 T Power Tower is canny yellow now mind ya.

[Mr-Z]

Just about anything should work also later demos that use RTG (ran a bunch of them) but demos that use WOS will obviously not work.

Do yourself a favor go for a pi4b/CM4 setup the speed difference is massive!
At 2.2 Ghz overclock you'll almost get 3 times the performance of a pi3 setup.

Sorry to hear about your BPPC, still a nice card to have.

[klx300r]

Originally Posted by Mr-Z

...
Do yourself a favor go for a pi4b/CM4 setup the speed difference is massive!
At 2.2 Ghz overclock you'll almost get 3 times the performance of a pi3 setup.
.

Just curious if you already have a PiStorm32 setup with Pi3A+ loading OS3.2 directly off the onboard miniSD on the Pi is it possible to just swap the miniSD into the Pi4B/CM4 and upgrade firmware on the PC side?

[specfreak]

Originally Posted by Mr-Z

Just about anything should work also later demos that use RTG (ran a bunch of them) but demos that use WOS will obviously not work.

Do yourself a favor go for a pi4b/CM4 setup the speed difference is massive!
At 2.2 Ghz overclock you'll almost get 3 times the performance of a pi3 setup.

Sorry to hear about your BPPC, still a nice card to have.

I've tried some today, but not many if any worked correctly. It's probably cos I'm RTGing on my Mediator to a Voodoo 3/3000 16MB card rather than the Pi's RTG. Mental by Push Entertainment, just shows a small split screen that's one side flickers. I tried all the trueaga.libraries and they all do the same.

I'll spin up CaffeineOS and see what that does, or make another setup, but use the Pi's RTG rather than my Voodoo.

[Dunny]

Originally Posted by klx300r

Just curious if you already have a PiStorm32 setup with Pi3A+ loading OS3.2 directly off the onboard miniSD on the Pi is it possible to just swap the miniSD into the Pi4B/CM4 and upgrade firmware on the PC side?

It might, but bear in mind that Pi3A uses brcm-sdhc.device for the uSD card and the Pi4 uses brcm-emmc.device which may slow you down.