Amiga PPC emulation

@broadblues

I wouldn't imagine very fast right now as jit isn't enabled yet.

guys no one as been advance the winuae autor to use the sheepshaver core because it is jit in the x86 version?

He's using the Generic PearPC core at the moment, he can just change to the JIT one (PearPC has different cores it can use). I suspect PearPC is a lot more supported than the Sheepshaver one.

@Spirantho

I dont know about pearpc cores , i remember good of much pearpc was slow with old MacOs X on my PC.
Last version of SheepShaver is from 2014

@Spirantho

Quote:

PearPC cpu core was easy to integrate into WinUAE.
There for it was best choice while testing and trying this out.

Quote:

Does not have MMU support, so its useless.

Simply good news: Having on the same pc(I.e. Notebook) aros, os4.1 (and eventually mos). Developing for three amigoid systems could be accelerated by this.

@AmigaBlitter
Perfect to test the projects in MOS and OS4!

Hi! If i compile an app on os4.1 (sam) is it compatible with classic and vice versa?
Thx

In general, if you compile a program using the OS4 SDK, it will be compatible with any OS4 system (Classic / X1000 / Pegasos / Sam, etc.). Exceptions are programs/games that might need a certain amount of RAM, graphics memory or a fast enough CPU. I think OS4.1 is required to use shared object libraries (.so), but if you link statically, then it will run on OS4.0 too (unless it requires features only OS4.1 has).

@Templario

Quote:

Not really, Sam440/460/AmigaONE's does not have classic chipsets, so thing that works on CyberstormPPC/BizzardPPC does not guarantee it works on any other AmigaOS4 compatible hardware.

They can bang the hardware almost as bad as they do on AmigaOS3.x, on the other hand they will need to write code that is compatible with AmigaOS4.1 memory protection and libraries and so on, they might end up writing better software, I hope.

@LiveForIt

I wouldn't think there would be much point in specifically writing a PPC os4.1 app and then proceeding to hit the AGA chipset. May as well just write for 3.x in that case if that's what you want to do. I don't reckon that will be an issue.

@Steady

One day why not Euae Jit + PPC native (virtualized) we will have Morphos 1.4 in a window of AmigaOs ;) or AmigaOs Classic in a window of amigaos :P

@Steady

Quote:

Well as AmigaOS3.x programs also run on AmigaOS4.x, I'm afraid that developers who has written programs for OS3.x, will use WinUAE to confirm that there software works or not AmigaOS4.x.
But even if there software work on CyberStormPPC/BlizzardPPC it does not make there software hardware independent.

Quote:

There is not mutch point under 3.x, but people do for number of reasons anyway.

* Because they use development tools that are old and does not support new graphic cards, or because they think they can only make some effects on AGA. They do not wont to learn C/C++/AmigaE.

* Besides some people like to hit the hardware to take control over the hardware not because they need to, but because they think its fun to control the hardware them self.

* Because its some times easier do a one instruction bit test on the joystick ports for a mouse click then check intuition events or to implement propper joystick handling for lowlevel.library or other API's alike.

* Because AHI eat CPU cycles they do not have on 68020, and Paula hardware being so easy to program anyway so they just ignore AHI.

* Because they are used to doing it one way, and have become lazy, and just reuse old code, not looking up Autodocs, because they think they know already what they can do and can not do.

* Because users of Amiga1200/4000 does not make demands, and ask for support for there sound cards and graphic cards (Cyerbvison/BizzardVison/PCI graphic cards/Zorro graphic cards), so developers write code to the lowest standards (AGA) to support “every one”, in the simplest way possible.

@LiveForIt

Fair points, but I still think (and hope) that apart from a few potential demos, it is unlikely.

The two things that do stick out to me are the mouse/joystick button tests and accessing Paula directly. Those might be just a bit too tempting.

Anyway, that could happen today with developers who already own OS4.1 Classic.

WinUAE 2.9.0 b15 is now out using the QEMU core.