Amiga OS launchbar11/22/2023 Compiling from QEMU master has latest patches that may improve FPU a little but may need the disable dbus option if you get an error related to that.įor the network it may depend on your QEMU command line. One may try to enable even more compiler optimisations with -extra-cflags=-O3 but not sure if that helps. The -enable-lto option enables Link Time Optimisation which is a compiler optimisation that will take more time to compile and may be faster or break depending on compiler version. Adding -enable-slirp menas it will give error and fail when no slirp is detected instead of building without -netdev user so you can make sure that way tho config will be what you want. The dbus and slirp options should be auto detected so if you have libslirp-dev (or what is's called on your distro) package installed then user network will be built. If you can verify the correct functioning of Amicicygnix on your configuration.Ī thousand can use -enable/-disable options with Linux as well they are not specific to macOS. While it should reply that the file is in use and cannot be deleted. While instead with the active connection I can delete the file configure -target-list=ppc-softmmu -disable-dbus-display -enable-slirp -enable-ltoīecause I can't figure out if the command above is specific for "MAC" systems or is it also valid for Ryzen systemsĪlso I would like to know if anyone works AmiCygnixĪlso in the light of the functioning of the real Voodoo proven.īecause I am convinced that RTL8139 is currently unable to get an external IP for some reason.Īnd it actually always adopts 10.0.2.15 whatever configuration is chosen via "TunTap" tooīecause in theory I shouldn't be able to delete the configuration in use in DEVS/NETINTERFACES/RTL8139 With the Ryzen the commands for compiling qemu are standard Used the following command have a question a : error adding symbols : archive has no index run ranlib to add oneĬlang : error : linker command failed with exit code 1 (use - v to see invocation )īut at least its builds with -enable-lto so - lm / usr / lib / x86_64 - linux - gnu / libpixman - 1.so - lgmodule - 2.0 - lglib - 2.0 - Wl ,- end - group so - pthread - lgmodule - 2.0 - lglib - 2.0 / usr / lib / x86_64 - linux - gnu / libgnutls. so / usr / lib / x86_64 - linux - gnu / libglib - 2.0. so / usr / lib / x86_64 - linux - gnu / libgobject - 2.0. fa - lcap - ng - lnuma / usr / lib / x86_64 - linux - gnu / libgio - 2.0. a subprojects / libvhost - user / libvhost - user. a subprojects / libvhost - user / libvhost - user - glib. fa - Wl ,- no - whole - archive - fstack - protector - strong - Wl ,- z, relro - Wl ,- z, now - Wl ,- warn - common libqemuutil. o - flto - Wl ,-as- needed - Wl ,- no - undefined - pie - Wl ,- whole - archive - Wl ,- start - group libevent - loop - base. Linking target fsdev / virtfs - proxy - helperĬlang - 12 - m64 - mcx16 - o fsdev / virtfs - proxy - helper fsdev / virtfs - proxy - helper. I think I put this aside for now and do something else. I'll need to check because I forgot how I implemented it back then. Maybe there are different ways to access registers but in QEMU they end up in the same place. Is this bit only supposed to swap some regs but not others or how does this work. Update: I've tried to implement byte swapping now which makes most of the register values show up correctly but now some regs are wrong such as 0x50 CRTC_GEN_CNTL, 0xf8 CNFG_MEMSIZE, 0x108 CONFIG_APER_SIZE that are now byre swapped. That should at least get better results with ati-vga and AmigaOS but does not explain why did not get it work with passed through card bceause I assume this bit should work there. (Or we could just do the swap in the handler functions if the bit is set which may be the simple route for now for testing.) I'll ask on the QEMU list unless I can find it out. If we can't change memory region endienness on the fly then we need two of them and swap them on this bit. There's no further info on that but I guess this should flip register aperture endianness to big endian which is definitely not done in QEMU and I'll have to find out how this could be emulated.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |