WinUAE QEMU PPC

[Toni Wilen]

winuaelog.txt is required. bootlog contains only uae startup/init information.

[mingle]

Sorry, wrong log-file added!

Here's the correct one.

I booted into Amiga OS 4.1, then opened DH0 > Prefs > ScreenMode. Then quit WinUAE.

[Toni Wilen]

Switch off Z3 fast or set it to 32M or larger. (This is bug that is fixed in 3.1 betas)

[mingle]

Thanks Toni, that did the trick.

Cheers,

Mike.

[mikettl]

Just a rookie question:

is it still required to use the plugin lib qemu-uae.dll with official WinUAE 3.1? I'm asking because I got the AmigaOS 4.1 Final Edition and like to configure it :-). Before I run into avoidable issues...

Many thanks.

Best regards
Mike

[Toni Wilen]

PPC support has not changed from 3.0 to 3.1. (Newer QEMU release versions also don't have any PPC updates = no need to update the DLL)

[mikettl]

great, thx, Toni

[Toni Wilen]

I now have designed different kind of directory filesystem support that should also work with OS4 (and m68k AOS too, of course). It will be alternative and less flexible method. Original method isn't going to disappear. It probably will appear as another "UAE"-like HD controller in GUI.

This is not going to directly help with any other UAE device support but I assume OS4 compatible host OS file sharing is the most wanted feature. It is also not going to help with UAEGFX (It needs very different interface) but it may be also possible later.

But first I am going (for the first time ever) require a bounty before any code gets written. This is OS4-only feature and it does not emulate any existing hardware (It can't).

Who wants to organize it? (I only know http://www.power2people.org/ which handled AROS m68k bounties and others) EDIT: Change of plans, no need for bounty after all, at least for directory filesystem part. More information later..

Very first version is going to be simple:

- Amiga-side UAE-specific filesystem handler file is needed to be copied in L: (This still needs confirming but I assume m68k filesystem handlers will work on OS4, it probably will be written in C so a PPC port can be done if really needed)
- mountlist entry is needed, mostly filled with dummy values (like CDFS).
- host OS independent (of course)

Any kind of advanced feature like automount will be done later, if it is possible.

[Romanujan]

Originally Posted by Toni Wilen

Very first version is going to be simple:

- Amiga-side UAE-specific filesystem handler file is needed to be copied in L: (This still needs confirming but I assume m68k filesystem handlers will work on OS4, it probably will be written in C so a PPC port can be done if really needed)
- mountlist entry is needed, mostly filled with dummy values (like CDFS).
- host OS independent (of course)

Similar tools already exist, like http://aminet.net/search?query=ftpmount - you just need to launch FTP server somewhere. Yes, you could have Amiga-like file attributes, it would probably be faster, but... I am not sure if it is worth the effort.

Unless we would be able to boot OS4 from such a filesystem somehow - this would allow to have easy accessible Startup-Sequence and other important files, and we wouldn't suffer from low HD performance while using Blizzard PPC (256 MB RAM) instead of Cyberstorm PPC (fast HD, but only 128 MB RAM...)

[themamboman]

Originally Posted by Toni Wilen

I now have designed different kind of directory filesystem support that should also work with OS4 (and m68k AOS too, of course). It will be alternative and less flexible method. Original method isn't going to disappear. It probably will appear as another "UAE"-like HD controller in GUI.

So, this would mean we could use directories on the host side instead of HDF files for OS4?

Is so, VERY COOL!

[Toni Wilen]

It will be "pure" hardware emulated device, it can be made autoboot capable and does not depend on type of CPU emulator but I don't know if OS4 supports normal m68k autoboot method or if it needs some PPC driver code (=not my problem)

Different method to create emulated "network filesystem", same result, host directory appears as a harddrive.

[strim]

Originally Posted by Toni Wilen

It will be "pure" hardware emulated device, it can be made autoboot capable.

So, NetBSD support could be added?

[Toni Wilen]

Originally Posted by strim

So, NetBSD support could be added?

If you also implement Amiga filesystem packet emulator in NetBSD

[strim]

Originally Posted by Toni Wilen

If you also implement Amiga filesystem packet emulator in NetBSD

Hmm, well, that shouldn't be too difficult. Probably. NetBSD already supports Amiga FFS (read only though). And as usual with UNIX-likes, filesystem operations are split into separate VFS filesystem driver that handles operations on all the fs structures, and block device driver that handles read/writes to actual hardware device.

What do you exactly understand as "packet" here?

[Toni Wilen]

Originally Posted by strim

Hmm, well, that shouldn't be too difficult. Probably. NetBSD already supports Amiga FFS (read only though). And as usual with UNIX-likes, filesystem operations are split into separate VFS filesystem driver that handles operations on all the fs structures, and block device driver that handles read/writes to actual hardware device.

What do you exactly understand as "packet" here?

DOS filesystem packet. (ACTION_INPUT and friends).

Normal UAE directory filesystem: very little m68k side code, all packets are nearly always 1:1 passed to native UAE code. UAE code accesses Amiga-side addresses directly.

Alternate method that works even if CPU is not UAE m68k and physical address does not necessarily equal logical address: packet handling is in Amiga-side, it parses packets and sends commands to UAE side.

For example when ACTION_FINDINPUT comes, path string is copied to autoconfig device's io space (which is UAE-side memory), open mode and lock "cookie" is stored in other IO addreses, then UAE command code is written to another command IO "register", poll/wait for interrupt, emulation does UAE-side stuff (check if file exists, open it, return file "cookie", set command done flag/interrupt), Amiga-side updates struct FileHandle, replies packet.

All Amiga packets needs to be separated in two parts: Amiga-side and UAE-side and parameter passing is via autoconfig IO space. (It is guaranteed to have physical == logical and it is not cached)

Very boring task.. And not very useful for non-AmigaOS operating systems.

[Romanujan]

This sounds good to me. I have successfully used PFS in OS4.1 Classic (not for the boot partition, though) - so IMHO there is a chance it will work.

[FOL]

@Toni

Is there any guide / info on setting up the new menu's etc.
As I have been trying for hours to setup a fresh PPC config without luck.
If not, I will upload all logs of the different random crashes on start.

[Toni Wilen]

Originally Posted by FOL

@Toni

Is there any guide / info on setting up the new menu's etc.
As I have been trying for hours to setup a fresh PPC config without luck.
If not, I will upload all logs of the different random crashes on start.

Simple rule is: Don't ask me for guides

What are you trying to do? There are multiple PPC configs in real world. What crashes? logs and config will always help

[FOL]

Originally Posted by Toni Wilen

Simple rule is: Don't ask me for guides

What are you trying to do? There are multiple PPC configs in real world. What crashes? logs and config will always help

Here's one set, if I keep trying same config. It gives same error, but not always the same amount. Sometimes, it gives error over and over.

[Toni Wilen]

Originally Posted by FOL

Here's one set, if I keep trying same config. It gives same error, but not always the same amount. Sometimes, it gives error over and over.

Switch off JIT first and try again. m68 JIT is useless when emulating OS4.
Also always start with basic setup, when it works, only then add extra hardware, easier to find out what causes the problem.

Problem is probably is caused by address space limits (Mediator uses huge amounts of Z3 space). Swiching off JIT should help a bit.

G-REX is the best option if you want to save Z3 space (It is not autoconfig board and uses normally unused address sapce). Check the read me in OS41FE install CD, you need to add extra parameter to enable OS4 G-REX support.