WinUAE QEMU PPC - Page 21

Toni Wilen · 23 January 2018, 18:02

Quote:

Originally Posted by bernd roesch

does the quemu PPC run in a own thread same way it is design in cyberstorm PPC ?. if this use a own thread then it can speedup to use PPC code version because 68k side can do other.

for the logfile, 2 lines before above post stand this. can see JIT is disable and 68060 is used
39-584 [588 001-000]: CPU=68060, FPU=68060 (host), MMU=0, JIT=0. fast
39-585 [588 114-326]: pull overflow! 2288 1968 3936

PPC always runs in a separate thread.

Quote:

Originally Posted by bernd roesch

Unassigned mem read 00000000fff00100

This should not cause problems. But it may mean there should be something at this address (which is strangely close to Z3 config space), Amiga PPC hardware public documentation does not exist.

But "fatal" message means something went badly wrong. I don't remember what it means..

Address error means something caused CPU to jump in odd address which is always illegal.

AMIGASYSTEM · 23 January 2018, 18:35

Quote:

Originally Posted by bernd roesch

when i add quemu files winuae crash as soon i start a program(non PPC too). crash seem happen in warp.library. if i remove this lib then ppc resource etc... are in no crash happen

You receive your Runtime error if you enable "Direct" in CPU Config

AMIGASYSTEM · 23 January 2018, 18:39

Quote:

Originally Posted by bernd roesch

many thanks for info, so i know AFA should work too.

Not everything works su AFA OS PPC, on some applications I have error "Memory protection violation - Access to 00000000 Task name: 'ramlib_PPC'"

On AFA OS 060/JIT (No-PPC) Warp3D works perfectly, see video

[ Show youtube player ]

I'm sorry Bernd, there will be news in the future for AFA OS

Hedeon · 23 January 2018, 21:00

Quote:

Originally Posted by Toni Wilen

PPC always runs in a separate thread.

This should not cause problems. But it may mean there should be something at this address (which is strangely close to Z3 config space), Amiga PPC hardware public documentation does not exist.

0xfff00100 is the hard-wired start vector of the early PPCs. Startup code should be at this address. Later (after a kernel is running) this should become the reset exception vector.

Toni Wilen · 23 January 2018, 21:26

Quote:

Originally Posted by Hedeon

0xfff00100 is the hard-wired start vector of the early PPCs. Startup code should be at this address. Later (after a kernel is running) this should become the reset exception vector.

Right, it has been too long since I did PPC stuff. Recent JIT support causes this memory disappear if JIT direct is enabled which of course also breaks PPC, it causes that fail message because PPC boot vector was missing..

Previously JIT direct was disabled which really makes more sense because CSPPC + JIT direct becomes PPC incompatible..

JIT really hates having address mirrors.

bernd roesch · 23 January 2018, 22:16

I have use indirect mode and disable the JIT and get this crash. maybe somebody can upload a config that work. I upload my config i use. before test i disable the JIT

AMIGASYSTEM · 23 January 2018, 22:32

I attach my config

bernd roesch · 24 January 2018, 12:37

thanks i notice some problems to get your config working but your config let work ppc with chipset screen and sysspeed show mips and mem access speed. so my AOS install have no problem. i need search what other problem is. i choose the screenmode after boot in chipset so a wrong screenid seem not possible. maybe know wy invalid render mode info happen. this is without JIT

Code:

04-472 [170 225-125]: Creating UAE bsdsocket.library 4.1
04-538 [173 226-271]: mmu_op F518 PC=0805D9EA
04-538 [173 226-271]: PFLUSH
04-591 [176 027-166]: mmu_op F518 PC=0805DA24
04-591 [176 027-166]: PFLUSH
04-592 [176 226-167]: mmu_op F518 PC=0805BC74
04-592 [176 226-167]: PFLUSH
04-592 [176 226-167]: mmu_op F518 PC=0805BC8E
04-592 [176 226-167]: PFLUSH
04-592 [176 226-170]: 68060 FPU state: enabled
05-332 [213 226-162]: RTG mode mask: 212
05-332 [213 226-162]: P96: Hardware sprite support disabled
05-332 [213 226-162]: uaegfx.card magic code: 00EF3800-00EF393E ABI=081AF37C
05-332 [213 226-162]:  1: 50001000  320x 200 UAE: 320x 200
05-333 [213 226-162]:  2: 50011000  320x 240 UAE: 320x 240
05-333 [213 226-162]:  3: 50091000  320x 256 UAE: 320x 256
05-333 [213 226-162]:  4: 50021000  640x 400 UAE: 640x 400
05-333 [213 226-162]:  5: 50031000  640x 480 UAE: 640x 480
05-333 [213 226-162]:  6: 500A1000  640x 512 UAE: 640x 512
05-333 [213 226-162]:  7: 50831000  720x 480 UAE: 720x 480
05-333 [213 226-162]:  8: 50841000  720x 576 UAE: 720x 576
05-333 [213 226-162]:  9: 50041000  800x 600 UAE: 800x 600
05-333 [213 226-162]: 10: 50051000 1024x 768 UAE:1024x 768
05-333 [213 226-162]: 11: 50061000 1152x 864 UAE:1152x 864
05-333 [213 226-162]: 12: 508E1000 1280x 720 UAE:1280x 720
05-333 [213 226-162]: 13: 508F1000 1280x 768 UAE:1280x 768
05-333 [213 226-162]: 14: 50901000 1280x 800 UAE:1280x 800
05-333 [213 226-162]: 15: 50921000 1280x 960 UAE:1280x 960
05-333 [213 226-162]: 16: 50071000 1280x1024 UAE:1280x1024
05-333 [213 226-162]: 17: 50A11000 1360x 768 UAE:1360x 768
05-333 [213 226-162]: 18: 50931000 1366x 768 UAE:1366x 768
05-333 [213 226-162]: 19: 50A31000 1400x1050 UAE:1400x1050
05-333 [213 226-162]: 20: 50941000 1440x 900 UAE:1440x 900
05-333 [213 226-162]: 21: 50AA1000 1600x 900 UAE:1600x 900
05-333 [213 226-162]: P96: Non-unique mode 1600x1024
05-333 [213 226-162]: 22: 50FF1000 1600x1024 UAE:1600x1024
05-333 [213 226-162]: 23: 50971000 1680x1050 UAE:1680x1050
05-333 [213 226-162]: 24: 50981000 1920x1080 UAE:1920x1080
07-241 [308 226-259]: Your Amiga program just did something terribly stupid 19000000 PC=00EF387A
07-241 [308 226-259]: 18FFFFE0  0000 0000 0000 0000 0000 0000 0000 0000
07-241 [308 226-259]: 18FFFFF0  0000 0000 0000 0000 0000 0000 0000 0000
07-242 [308 226-259]: 19000000  0000 0000 0000 0000 0000 0000 0000 0000
07-242 [308 226-259]: 19000010  0000 0000 0000 0000 0000 0000 0000 0000
07-242 [308 226-259]: 19000020  0000 0000 0000 0000 0000 0000 0000 0000
07-242 [308 226-259]: 00EF385A  0101 0101 0100 48E7 8000 A078 4A80 4CDF
07-242 [308 226-259]: 00EF386A  0001 6604 2F28 01BA 4E75 48E7 8000 A079
07-242 [308 226-259]: 00EF387A  4A80 4CDF 0001 6604 2F28 0182 4E75 48E7
07-242 [308 226-259]: 00EF388A  8000 A07A 4A80 4CDF 0001 6604 2F28 0192
07-242 [308 226-259]: 00EF389A  4E75 48E7 8000 A07B 4A80 4CDF 0001 6604
07-242 [308 226-259]: 00000000    8192K/1 =    8192K ID C32 Chip memory
07-242 [308 226-259]: 00800000    4032K/0 =    4032K -- F32 <none>
07-242 [308 226-259]: 00BF0000      64K/0 =      64K -- CIA CIA
07-242 [308 226-259]: 00C00000    1024K/0 =    1024K -- C32 Custom chipset
07-242 [308 226-259]: 00D00000     768K/0 =     768K -- C16 <none>
07-242 [308 226-259]: 00DC0000      64K/0 =      64K -- C16 Battery backed up clock (RF5C01A)
07-242 [308 226-259]: 00DD0000      64K/0 =      64K -- C16 A4000 IDE
07-242 [308 226-259]: 00DE0000      32K/0 =      32K -- C16 Motherboard Resources
07-242 [308 226-259]: 00DE8000      32K/0 =      32K -- C16 <none>
07-242 [308 226-259]: 00DF0000      64K/0 =      64K -- C16 Custom chipset
07-242 [308 226-259]: 00E00000     576K/0 =     576K -- F32 <none>
07-242 [308 226-259]: 00E90000      64K/1 =      64K -- F32 Filesystem autoconfig
07-242 [308 226-259]: 00EA0000     320K/0 =     320K -- F32 <none>
07-242 [308 226-259]: 00EF0000      64K/1 =      64K -- F32 UAE Boot ROM
07-243 [308 226-259]: 00F00000     256K/1 =     256K -- F32 CPUBoard F00000 (CBD3C034)
07-243 [308 226-259]: 00F40000       4K/0 =       4K -- F32 CyberStorm SCSI IO
07-243 [308 226-259]: 00F41000      60K/0 =      60K -- F32 CyberStorm SCSI RAM
07-243 [308 226-259]: 00F50000     128K/0 =     128K -- F32 CPUBoard IO
07-243 [308 226-259]: 00F70000      64K/0 =      64K -- F32 <none>
07-244 [308 226-259]: 00F80000     512K/1 =     512K ID F32 Kickstart ROM (4D1575A6)
07-244 [308 226-259]: 01000000     112M/0 =     112M -- F32 <none>
07-244 [308 226-259]: 08000000     128M/1 =     128M ID F32 RAMSEY memory (high)
07-244 [308 226-259]: 10000000      16M/0 =      16M -- F32 <none>
07-244 [308 226-259]: 11000000     128M/1 =     128M ID F32 Zorro III Fast RAM
07-244 [308 226-259]: 19000000    3680M/0 =    3680M -- F32 <none>
07-244 [308 226-259]: FF000000      64K/0 =      64K -- F32 Autoconfig Z3
07-244 [308 226-259]: FF010000   15296K/0 =   15296K -- F32 <none>
07-244 [308 226-259]: FFF00000     512K/1 =     512K -- F32 CPUBoard MAPROM
07-244 [308 226-259]: FFF80000     512K/0 =     512K -- F32 <none>
07-244 [308 226-259]: CPU halted: reason = 3 PC=00ef387a
07-244 [308 226-259]: ERROR - Invalid RenderInfo memory area...

same hardfile boot with myconfig work and output this in log

Code:

46-049 [179 224-276]: clipboard task init: 4003c708
46-049 [179 226-286]: Creating UAE bsdsocket.library 4.1
46-052 [180 194-028]: clipboard process init: 4003c708
46-115 [183 225-139]: mmu_op F518 PC=400666A2
46-115 [183 225-139]: PFLUSH
46-115 [183 224-148]: PCI Config Space LONG READ fffc0000 PC=40066894
46-128 [184 216-030]: mmu_op F518 PC=400666DC
46-128 [184 216-030]: PFLUSH
46-128 [184 226-035]: mmu_op F518 PC=4006492C
46-128 [184 226-035]: PFLUSH
46-128 [184 048-036]: mmu_op F518 PC=40064946
46-128 [184 048-036]: PFLUSH
46-128 [184 224-040]: 68060 FPU state: enabled
46-776 [216 226-147]: RTG mode mask: 212
46-776 [216 226-147]: P96: Hardware sprite support disabled
46-776 [216 226-147]: uaegfx.card magic code: 00EF3800-00EF393E ABI=4022904C
46-776 [216 226-147]:  1: 50001000  320x 200 UAE: 320x 200
46-776 [216 226-147]:  2: 50011000  320x 240 UAE: 320x 240
46-776 [216 226-147]:  3: 50091000  320x 256 UAE: 320x 256
46-776 [216 226-147]:  4: 50021000  640x 400 UAE: 640x 400
46-776 [216 226-147]:  5: 50031000  640x 480 UAE: 640x 480
46-776 [216 226-147]:  6: 500A1000  640x 512 UAE: 640x 512
46-776 [216 226-147]:  7: 50831000  720x 480 UAE: 720x 480
46-776 [216 226-147]:  8: 50841000  720x 576 UAE: 720x 576
46-776 [216 226-147]:  9: 50041000  800x 600 UAE: 800x 600
46-776 [216 226-147]: 10: 50051000 1024x 768 UAE:1024x 768
46-776 [216 226-147]: 11: 50061000 1152x 864 UAE:1152x 864
46-776 [216 226-147]: 12: 508E1000 1280x 720 UAE:1280x 720
46-776 [216 226-147]: 13: 508F1000 1280x 768 UAE:1280x 768
46-776 [216 226-147]: 14: 50901000 1280x 800 UAE:1280x 800
46-776 [216 226-147]: 15: 50921000 1280x 960 UAE:1280x 960
46-776 [216 226-147]: 16: 50071000 1280x1024 UAE:1280x1024
46-776 [216 226-147]: 17: 50A11000 1360x 768 UAE:1360x 768
46-776 [216 226-147]: 18: 50931000 1366x 768 UAE:1366x 768
46-776 [216 226-147]: 19: 50A31000 1400x1050 UAE:1400x1050
46-776 [216 226-147]: 20: 50941000 1440x 900 UAE:1440x 900
46-776 [216 226-147]: 21: 50AA1000 1600x 900 UAE:1600x 900
46-777 [216 226-147]: P96: Non-unique mode 1600x1024
46-777 [216 226-147]: 22: 50FF1000 1600x1024 UAE:1600x1024
46-777 [216 226-147]: 23: 50971000 1680x1050 UAE:1680x1050
46-777 [216 226-147]: 24: 50981000 1920x1080 UAE:1920x1080
47-745 [264 226-266]: GetDiskFreeSpaceEx('D:\') failed err=21
47-772 [266 224-034]: RTG conversion: Depth=4 HostRGBF=9 P96RGBF=9 Mode=4
47-772 [266 080-048]: SetSwitch() - Picasso96 1920x1080x32 (1920x1080x32)

Toni Wilen · 24 January 2018, 12:42

Quote:

Originally Posted by bernd roesch

thanks i notice some problems to get your config working but your config let work ppc with chipset screen and sysspeed show mips and mem access speed. so my AOS install have no problem. i need search what other problem is. i choose the screenmode after boot in chipset so a wrong screenid seem not possible. maybe know wy invalid render mode info happen. this is without JIT

Something caused whole RTG board to disappear from memory map but UAE still thought the board was there... Attach complete winuaelog.txt.

bernd roesch · 24 January 2018, 13:57

I see now option that cause winuae crash with runtime requester. it happen when cyberstorm ppc memory is set to 1 MB or none. Does PPC only work in this 128 mb memory and not in z3 ?

winuae crash also when use A1200 ROM(which work without PPC in my config ok).so its important to have A4000 roms for A4000 cyberstormppc

the logfile with his config that let not work p96 with my hardfile is attached

Toni Wilen · 24 January 2018, 14:21

Quote:

Originally Posted by bernd roesch

I see now option that cause winuae crash with runtime requester. it happen when cyberstorm ppc memory is set to 1 MB or none. Does PPC only work in this 128 mb memory and not in z3 ?

I think real CSPPC requires at least 4M or more RAM (4x1M SIMMs is minimum) but I allowed smaller and if it is 1M or smaller, mirrors are disabled. (Mirrors that are needed for PPC to work)

I guess I should add correct limit

Quote:

the logfile with his config that let not work p96 with my hardfile is attached

For some reason autoconfig is not working. (E80000 still has unconfigured uae boot rom board)

Attach also config.

bernd roesch · 24 January 2018, 15:33

I notice also this requester when JIT direct is enable. maybe it is possible to bring a warning that JIT direct can not enable and cyberstormppc memory need best set to 128 mb and other mem to 0. I notice when i set cybppc mem to 16 MB start sysspeed on my install do a hang. only when i set cybppc mem to 32 MB syspeed start. so seem to use PPC there can only use cybppc mem.

Edit: the config with the not working P96 is same as amigasystem post. i only choose my rom file and add my hardfile.

Quote:

Originally Posted by AMIGASYSTEM

Not everything works su AFA OS PPC, on some applications I have error "Memory protection violation - Access to 00000000 Task name: 'ramlib_PPC'"

On AFA OS 060/JIT (No-PPC) Warp3D works perfectly, see video

[ Show youtube player ]

I'm sorry Bernd, there will be news in the future for AFA OS

I get now cybppc working ok with AFA MCP and all other. I use always in my startup sequence stackattack addstack 30000.maybe should add earlier but as this work ok
afa_os_loader ;ALWAYSAFA ;LOG ;MOUSESTART
c:MCP;_1.48
tools/stackattack/stackattack addstack 30000
c/iprefs

maybe its a stack problem because afa and ppc need more stack. I test with wipeout memory boundchecker and i get no hits when i use the warpup demos. The PPC need more memory align, you can also test if memtrailer with size 16 help. amikit have this always install, but it slow down because more cache miss happen
voxelspace do in 800x600 around 16-20 fps. i think my real cybppc was not so fast. maybe more a gfx card limit on original hardware.

Toni Wilen · 24 January 2018, 15:43

Quote:

Originally Posted by bernd roesch

I notice also this requester when JIT direct is enable. maybe it is possible to bring a warning that JIT direct can not enable and cyberstormppc memory need best set to 128 mb and other mem to 0. I notice when i set cybppc mem to 16 MB start sysspeed on my install do a hang. only when i set cybppc mem to 32 MB syspeed start. so seem to use PPC there can only use cybppc mem.

I won't ever add any warning dialogs. They are only annoying. It is user's problem to set config that makes sense. It is by design to allow crazy configs.

You also probably should at least set Z3 mapping to real to make it look more like real hardware, especially when using non-common configs, some drivers may assume real Z3 mapping.

Quote:

Edit: the config with the not working P96 is same as amigasystem post. i only choose my rom file and add my hardfile.

Your ROM is not standard. What it is? It probably explains the autoconfig issue.

bernd roesch · 24 January 2018, 17:58

ah i see in log now it is A1200 Rom too, but it work ok on my config with cybterstorm PPC. The option that let P96 fail is chipset -> Chipset Extra A4000. My setting have chipset extra generic this work with the A1200 roms and cyberstorm ppc. I try with my real A4000 rom i read out, and notice then in Extra chipset A4000 work. i have only some rom to test for incompatibilities.

Toni Wilen · 24 January 2018, 18:00

Quote:

Originally Posted by bernd roesch

ah i see in log now it is A1200 Rom too, but it work ok on my config with cybterstorm PPC. The option that let P96 fail is chipset -> Chipset Extra A4000. My setting have chipset extra generic this work with the A1200 roms and cyberstorm ppc. I try with my real A4000 rom i read out, and notice then in Extra chipset A4000 work. i have only some rom to test for incompatibilities.

A4000 chipset extra allows Z3 boards to use Z3 config space which A1200 ROM does not support. (Technically you shouldn't even have Z3 boards in A1200 but as I said, I won't prevent anything and they usually work anyway)

Or untick the option in advanced chipset.

AMIGASYSTEM · 24 January 2018, 18:59

Quote:

Originally Posted by bernd roesch

afa_os_loader ;ALWAYSAFA ;LOG ;MOUSESTART
c:MCP;_1.48
tools/stackattack/stackattack addstack 30000
c/iprefs
.

the PPC system seems to work well, but the RAM problem does not resolve,
I attach AFA OS PPC video with RAM error.

bernd roesch · 24 January 2018, 20:45

Quote:

Originally Posted by AMIGASYSTEM

the PPC system seems to work well, but the RAM problem does not resolve,
I attach AFA OS PPC video with RAM error.

I get always this error and ramlib error. on 68k warp3d run only with hardware 3d cards. or do you use a warp3d soft cpu emulation ?

AMIGASYSTEM · 24 January 2018, 21:52

I did not understand what you said, the only library that works on AFA OS PPC is "Wazp3D.library-full".

On AFA OS 68k standard works well "Wazp3D.library-winuae" and "Wazp3D.library-full"

bernd roesch · 25 January 2018, 12:12

I have notice with this asm test program that context switch from 68k to PPC and back is very slow. around 40 calls on my 4*2.8 GHZ system. original PPC HW reach 3000 context switches /sec with this amiblitz program. source can work too with a 68k assembler. i reduce loop size to 100 so it take not too long for the attached binary. wy is this so slow ?. on real PPC it is slow because caches of PPC and 68k need flush this cost lots time. I attach shell prog to test.

source is this

Code:

WBStartup
JSR OPENPOWERPC
MOVE.l #100,d7
loop
LEA ppcprog,a1
JSR RUNPOWERPC
;JSR WAITFORPPC
;CMP.l #$dff180,d0
;BNE illeg
SUBQ.l #1,d7
BNE loop
End
Even4
ppcprog:
;Dc.l $00000000
Dc.l $3C6000DF
Dc.l $6063F180
Dc.l $B0030000
Dc.l $4E800020
illeg:ILLEGAL
           #PP_CODE    = 0     ;Ptr to PPC code
           #PP_OFFSET  = 4     ;Offset to PP_CODE
           #PP_FLAGS   = 8    ;flags (see below)
           #PP_STACKPTR = 12    ;stack pointer
           #PP_STACKSIZE = 16   ;stack size
           #PP_REGS = 20   ;15 registers (d0-a6)
           #PP_FREGS = 80   ;8 registers (fp0-fp7)
           #PP_SIZE = 150

RUNPOWERPC
                LEA     -$90(a7),a7
                MOVE.l  d0,PP_REGS(a7)
                MOVE.l  d1,PP_REGS+1*4(a7)
                MOVE.l  a0,PP_REGS+8*4(a7)
                MOVE.l  a1,PP_REGS+9*4(a7)
                MOVE.l  a4,PP_REGS+12*4(a7)
                MOVE.l  a7,a0
                        MOVE.l  a1,PP_CODE(a0)
                        CLR.l   PP_OFFSET(a0)
                        MOVE.l #0,PP_FLAGS(a0)    ;1=asynchron
                        CLR.l   PP_STACKPTR(a0)
                        CLR.l   PP_STACKSIZE(a0)
                MOVE.l  _PowerPCBase,a6
                JSR     -30(a6)                 ;RunPPC
                LEA     $90(a7),a7
                RTS
WAITFORPPC
                LEA     -$90(a7),a7
                MOVE.l a7,a0
                MOVE.l  _PowerPCBase,a6
                JSR     -36(a6)                ;waitppc
                MOVE.l  PP_REGS(a7),d0
                LEA     $90(a7),a7
                RTS
WAITQUICKPPC:    MOVEM.L D1-D7/A0-A6,-(A7)
MOVEA.L $34(A6),A4
MOVEA.L $2E(A4),A4
MOVEA.L $3B48(A4),A6
MOVE.l $114(a6),d0
MOVE.L  D0,D2
MOVEQ   #0,D0
LEA     $3C0C(A4),A1
MOVEA.L $3B48(A4),A6
JSR     -$84(A6)
MOVEA.L 0(A1),A1
MOVE.L  0(A1),D1
BEQ     'l1
'l3:CMP.L   $16(A1),D2
BNE     'l2
MOVE.L  A1,D3
MOVEA.L (A1)+,A0
MOVEA.L (A1),A1
MOVE.L  A1,4(A0)
MOVE.L  A0,(A1)
LEA     $3C0C(A4),A0
MOVEA.L D3,A1
MOVE.L  (A0),D0
MOVE.L  A1,(A0)
MOVEM.L D0/A0,(A1)
MOVEA.L D0,A0
MOVE.L  A1,4(A0)
MOVE.L  D3,D0
BEQ 'l1:
MOVE.l d0,a1
MOVE.l #1,$12(a1)
MOVE.l $e(a1),a2
BRA   'l1:
'l2:MOVEA.L D1,A1
MOVE.L  0(A1),D1
BNE     'l3
'l1:

'l11:;MOVE.l $1a(a0),d0
JSR -$27c(a6)
MOVE.l PP_REGS(a2),d0
CMP.l #$dff180,d0
BNE 'l11
;BCLR #30,$1a(a0)
;JSR -$27c(a6)
MOVE.l PP_REGS(a2),d0
MOVEA.L $3B48(A4),A6
MOVE.l $114(a6),a0
JSR     -$8A(A6)

MOVEM.L (A7)+,D1-D7/A0-A6
RTS
OPENPOWERPC
                MOVEM.l d0/d1/a0/a1/a6,-(a7)
                MOVE.l  #7,d0
                LEA     powerpcname,a1
                MOVE.l  $4,a6
                JSR     -552(a6)
                MOVE.l  d0,_PowerPCBase
                TST.l d0
                BEQ no
                MOVEM.l (a7)+,d0/d1/a0/a1/a6
                RTS
no:              ILLEGAL
CLOSEPOWERPC
                MOVEM.l d0/d1/a0/a1/a6,-(a7)
                MOVE.l  $4,a6
                MOVE.l  _PowerPCBase,d0
                BEQ.b   'noclose
                MOVE.l  d0,a1
                JSR     -414(a6)
'noclose
                MOVEM.l (a7)+,d0/d1/a0/a1/a6
                RTS
_PowerPCBase: Dc.l 0
powerpcname:     Dc.b    "powerpc.library",0

Toni Wilen · 25 January 2018, 20:57

Probably because practically no one has reported anything really useful about PPC emulation. (=simple test programs, not some huge useless test cases with dozens of library dependencies)

For me it is "it runs". I don't care about PPC or its speed -> perfect reports are required. (and someone else to merge latest QEMU changes..)

23 January 2018, 22:32	#407
AMIGASYSTEM Registered User Join Date: Aug 2014 Location: Brindisi (Italy) Age: 70 Posts: 8,252	I attach my config Last edited by AMIGASYSTEM; 16 February 2018 at 00:27.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
QEMU TCG as JIT replacement?	KillaByte	request.UAE Wishlist	21	30 January 2018 16:05
PPC emulation for winuae	marauder	request.UAE Wishlist	25	04 November 2014 06:13
WinUAE PPC thread	B14ck W01f	support.WinUAE	301	10 September 2014 16:34
WinUAE ppc support?	blasterreal	support.WinUAE	8	29 September 2010 00:51
PPC on WinUAE ?	glue	request.UAE Wishlist	4	28 January 2007 12:04

24 January 2018, 17:58	#414
bernd roesch Registered User Join Date: Apr 2012 Location: germany Posts: 139	ah i see in log now it is A1200 Rom too, but it work ok on my config with cybterstorm PPC. The option that let P96 fail is chipset -> Chipset Extra A4000. My setting have chipset extra generic this work with the A1200 roms and cyberstorm ppc. I try with my real A4000 rom i read out, and notice then in Extra chipset A4000 work. i have only some rom to test for incompatibilities.

24 January 2018, 21:52	#418
AMIGASYSTEM Registered User Join Date: Aug 2014 Location: Brindisi (Italy) Age: 70 Posts: 8,252	I did not understand what you said, the only library that works on AFA OS PPC is "Wazp3D.library-full". On AFA OS 68k standard works well "Wazp3D.library-winuae" and "Wazp3D.library-full"

25 January 2018, 20:57	#420
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,517	Probably because practically no one has reported anything really useful about PPC emulation. (=simple test programs, not some huge useless test cases with dozens of library dependencies) For me it is "it runs". I don't care about PPC or its speed -> perfect reports are required. (and someone else to merge latest QEMU changes..)

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