Forums - All Posts - The Amigans website

Forum Index

Board index » All Posts (joerg)

Bottom

« 1 ... 6 7 8 (9) 10 11 12 ... 86 »

joerg

Re: SDL1 open issues

Posted on: 2023/11/8 17:28 #161

Just can't stay away

@balaton
Quote:

or firmware (but the firmware is not really involved in graphics either so not likely to have a role in it either)

The firmware is executing the x86 BIOS ROM of gfx cards.
If the (emulated) SM502 has a x86 BIOS ROM it could be that it's BIOS code changes some endian mode and only works correctly with the SciTech x86emu used by U-Boot, but not with the x86 emulator of the Pegasos2 SmartFirmware?

Topic | Forum

joerg

Re: What the fastest possible x64 emulation way of OS4 today ?

Posted on: 2023/11/5 15:05 #162

Just can't stay away

@smarkusg
Use much more buffers, at least 1000 instead of only 64. Change it with MediaTooBox in the partition details.

DiskSpeed isn't really usable for such tests, using for example ScsiSpeed would be better.
DiskSpeed is a benchmark tool for comparing different file systems on the same hardware and most of your results for the small transfer sizes are just testing memcpy() speed of the disk cache instead of actual disk accesses and as result for example the 32768 bytes read/write results (from/to the disk cache) are much faster than the results of the larger transfers (which may bypass the disk cache and are disk I/O speed).
ScsiSpeed is for checking the speed of the hardware/driver, without using a file system, disk caches, etc.

Topic | Forum

joerg

Re: What the fastest possible x64 emulation way of OS4 today ?

Posted on: 2023/11/4 18:37 #163

Just can't stay away

@Maijestro
If nvram.config doesn't work you can use something like


idetool >NIL: -x a1ide.device 0 69

idetool >NIL: -x a1ide.device 2 69

in your S:startup-sequence or S:user-startup instead to change the transfer mode.
(According to the idetool -l output you are using 2 emulated drives, unit 0 and 2.)

Topic | Forum

joerg

Re: What the fastest possible x64 emulation way of OS4 today ?

Posted on: 2023/11/4 18:08 #164

Just can't stay away

@Maijestro
Quote:

Ok, I replaced the nonvolatile.library.kmod with the Pegasos2 version and nvram.config is in the Kickstart folder but PIO mode 4 is still used.

Make sure you aren't using the unmodified Pegasos2 nvram.config file (peg2ide_xfer/irq) on the AmigaOne but changed it to AmigaOne hardware/drivers (a1ide_xfer/irq).

Quote:

Can I also tell the Uboot firmware that I can activate it for a boot process? I am aware that the variables are not saved without NVRAM support.


setenv a1ide_xfer FFFF

setenv a1ide_irq 1111

But AFAIK AmigaOS can't access current values but only the ones stored in NVRAM ("saveenv" U-Boot command, not supported by QEmu).

Topic | Forum

joerg

Re: What the fastest possible x64 emulation way of OS4 today ?

Posted on: 2023/11/4 17:36 #165

Just can't stay away

@Maijestro
You are currently using PIO mode 4:Quote:

Xfer mode : best pio 12 (PIO 4, 16 MB/s) / best dma 69 (UDMA 5, 100 MB/s) / current 12 (PIO 4, 16 MB/s)

Quote:

assume that in the last section it is "DMA : yes" ?

That's just what the (emulated) drive supports, not what's currently used by the driver.

To use a Kickstart/nvram.config file, instead of the AmigaOne NVRAM which is not yet supported by QEmu, you'd have to replace the AmigaOne Kickstart/nonvolatile.library.kmod with a version from a classic Amiga or Pegasos2 version of AmigaOS 4.x.

Topic | Forum

joerg

Re: What the fastest possible x64 emulation way of OS4 today ?

Posted on: 2023/11/4 16:39 #166

Just can't stay away

@Maijestro
Quote:

With nvram.config which is in the Kickstart directory I tried to activate DMA as follows:

nvram.config is only supported in the classic Amiga version of nonvolatile.library.kmod, which seems to be used for the Pegasos2 as well, but not in the versions used on hardware with real NVRAM.

I'm not sure any more which option(s) display the transfer modes, but one of


idetool -l a1ide.device

idetool -u a1ide.device 0

or

idetool -d a1ide.device 0

should display it.

Topic | Forum

joerg

Re: CD32 music over whdload on EUAE

Posted on: 2023/11/4 15:28 #167

Just can't stay away

@kas1e
Quote:

But yeah, diskimage.device support it as i aware

Since you get errors from it with AmiDVD obviously not enough, or with bugs.

Topic | Forum

joerg

Re: WebKit based browser initiative

Posted on: 2023/11/3 16:41 #168

Just can't stay away

Porting WebCore to AmigaOS 4.x is only about 20% of the work.
Another 20% is porting the JavaScript JIT to PPC, unless there is support for PPC already now? (It wasn't at the time I did the OWB ports, and maybe it's not very important for X1000 and X5000, but it is if it should be usable on other systems as well.)
20% for audio/video/etc. and printing support.
About 40% of the work is implementing a web browser around WebCore/JSC.
Of course a BOOPSI (Enhancer/ReAction/ClassAct) based GUI for the browser would be much better, but for QT there are browsers already which could be used with next to no changes.

Topic | Forum

joerg

Re: Mnemosyne - Disk usage statistics utility for AmigaOS 3.x

Posted on: 2023/10/31 9:04 #169

Just can't stay away

@arisamiga
Quote:

This Update adds the "-g" shell flag to open a window for scans from the shell.

Using flags like "-g" in the arguments is something used on DOS and Unix, but AmigaOS usually uses keywords instead.
Check the dos.library AutoDoc function ReadArgs(), the RKRMs and it's example sources, etc.
Something like "GUI/S" could be used with a ReadArgs() template instead of the "-g" flag.
https://wiki.amigaos.net/wiki/Basic_In ... dard_Command_Line_Parsing has an example as well.

Topic | Forum

joerg

Re: libgcc.soo problem

Posted on: 2023/10/30 19:55 #170

Just can't stay away

@Raziel
Quote:

But wouldn't you end up with loads of libraries this way, dozens of differing libgccxxx.so...one for every game someone compiled years ago?

"Only" 2 versions for each GCC version, one for newlib and one for clib2.

If you put the SOs in PROGDIR:SObjs instead you have one copy for every single program using it, i.e. much more copies, and not not only different but identical copies of the SOs in different directories.

However, a big problem is, or at least was, that none of the clib2 maintainers so far understood how shared objects work on AmigaOS and ignored all bug reports about it, continued to built them without -soname resulting in incompatible shared objects...
And I wouldn't be surprised if the current newlib maintainer builds the newlib SOs with similar bugs, without using -Wl,-soname, as well.

Topic | Forum

joerg

Re: Odyssey 1.23 progress: r5 RC2

Posted on: 2023/10/30 18:49 #171

Just can't stay away

If you want an up to date browser which isn't obsolete on release already forget getting one with an AmigaOS GUI, way too few AmigaOS developers left for something like that.
With OWB it was possible for a short time, as long as Pleyo supported it and had several full time developers doing nothing but updating the WebKit parts and OWB's platform abstraction layer 2-3 times a week. The OS and CPU parts didn't need any, or at least only minor, changes because nearly all incompatible changes in WebKit were covered in the OWB BAL updates instead.
It's very unlikely that there ever will be a web browser again which is as platform independent as OWB was.

Instead a browser using a common GUI instead should be ported, something like the QT6 Browser, if required using AmiCygnix. But with only 1-2 developers, Alfkil and Edgar, working on it there probably wont be anything usable any time soon either...

Topic | Forum

joerg

Re: libgcc.soo problem

Posted on: 2023/10/30 18:07 #172

Just can't stay away

@LiveForIt
Soft links are not required nor should they be used on AmigaOS for shared objects!
Unlike on Unix on AmigaOS there are 2 different directories for the shared objects: The SObjs: Assign which is used when loading executables using shared objects, with something like libgcc.so.2.95.3 (GCC 2.95.3 newlib), libgcc_clib2.so.2.95.3 (GCC 2.95.3 clib2), libgcc.so.4.0.4 (GCC 4.0.4 newlib), etc. and the compiler directories with the different compiler versions, C libraries, etc. in which all versions have the same file name libgcc.so and which are used when linking executables.
The versions in the compiler/C library directories have to be built with something like "-Wl,-soname libgcc.so.2.95.3" to work and load the correct version from SObjs: when the executable is loaded.

Topic | Forum

joerg

Re: QEMU branches

Posted on: 2023/10/27 6:17 #173

Just can't stay away

@smarkusg
IIRC the smallest memory size complete AmigaOne XE systems were sold with is 512 MB.
The µA1-C, which isn't emulated by QEmu, was available with only 256 MB (+32 MB VRAM), but no AmigaOne with only 128 MB RAM.

Edited by joerg on 2023/10/27 6:36:37

Topic | Forum

joerg

Re: QEMU branches

Posted on: 2023/10/26 16:18 #174

Just can't stay away

@Maijestro
Quote:

Balaton has submitted the patches for AmigaOne XE emulation and they just need to be accepted:


mc->default_ram_size = 128 * MiB;

Why? To be usable it should be at least 512 MB, or even better 1 GB.

Topic | Forum

joerg

Re: Whdload crash in some cases under our E-UAE

Posted on: 2023/10/25 14:29 #175

Just can't stay away

@kas1e
For software using FPU instructions you need at least


cpu_type=68020/68881

Topic | Forum

joerg

Re: Whdload crash in some cases under our E-UAE

Posted on: 2023/10/25 14:15 #176

Just can't stay away

@kas1e
Line 1111 exceptions on m68k are caused for example executing FPU instructions on CPUs without a FPU.

Topic | Forum

joerg

Re: Is gprof ever works on os4 ? It is! And can be still!

Posted on: 2023/10/23 17:51 #177

Just can't stay away

@kas1e
Quote:

But then, profiling in clib2 broken, and cant be used easyly even on public kernel on old-supported cpus..soo only clib4.

What's the problem with current newlib versions on public kernels, supported CPUs and adtools GCC+binutils?
At least with my old newlib versions using GCC 2.95.x-4.2.4 and binutils 2.14.x profiling was working.

Topic | Forum

joerg

Re: Is gprof ever works on os4 ? It is! And can be still!

Posted on: 2023/10/23 17:15 #178

Just can't stay away

@Raziel
Quote:

Mabye -pg needs more switches under AmigaOS4?

Only if you are using the new binutils. At least some of them have a broken specs and you have to add -mcrt=newlib to your CFLAGS and LDFLAGS.

Edited by joerg on 2023/10/23 18:15:17

Topic | Forum

joerg

Re: Is gprof ever works on os4 ? It is! And can be still!

Posted on: 2023/10/23 6:35 #179

Just can't stay away

@kas1e
Quote:

So, while CLIB4 and BinUtils are there and can be used right now, as they opensourced, the OS4 update for the kernel will be out when it will be out (i do not know when).

You can update newlib without access to the sources. At least in my versions, I don't know anything about newer ones, IIRC the gprof support code wasn't in newlib.library but in libc.a, and the code didn't include anything C library specific.
Unless the clib4 code depends on other clib4 specific parts, which would be strange, you can simply use "ar d libc.a gprof_object", "ar a libc.a clib4_gprof_object" to update it.
Updating the newlib libc.so without access to the sources should be possible as well.

Topic | Forum

joerg

Re: QEMU branches

Posted on: 2023/10/22 14:26 #180

Just can't stay away

@Maijestro
Quote:

But what speaks against Qemu is:

- complicated setup, not user friendly

- NVRAM support (AmigaOne)

- 16-bit screen output (no 3D acceleration)

- Network unstable

When I also compare WinUae with Qemu, Qemu is the clear winner.

???
- WinUAE is easy to set up.
- No NVRAM support required since the classic Amiga version of AmigaOS 4.x uses a special nvram.library using a nvram.config kickstart module instead (the Pegasos2 version of AmigaOS 4.x seems to use the classic Amiga version as well, but no other versions, incl. the AmigaOne and Sam4x0 ones, do).
- 32 bit screen modes with host 2D HW acceleration (DirectX) and 3D support (old Warp3D only, not Warp3D nova) using an emulated Voodoo3 or S3Virge.
- No network problems.
- Support for sharing files between host and guest.
- Next to no speed differences according to the benchmark results, and the small differences are probably only because WinUAE uses an old version of the PPC emulation which could be updated.

I guess in 1-2 years QEmu will get better than WinUAE, as soon as AmigaOS 4.x virtio drivers for at least gfx and network are available, and the remaining problems in the QEmu emulation (NVRAM and performance monitor support, etc.) are fixed.
Especially since WinUAE is currently limited to Windows and x64 CPUs, although that could be changed as well, it's open source, but I doubt that will happen. QEmu OTOH supports all common systems (Android, Linux, BSD, Windows, etc.) and even works on niche systems like MacOS/ARM.
But currently the clear winner comparing WinUAE with QEmu for using AmigaOS 4.x on emulation is definitely WinUAE.

Edited by joerg on 2023/10/22 15:31:40
Edited by joerg on 2023/10/22 15:32:22

Topic | Forum

Top

« 1 ... 6 7 8 (9) 10 11 12 ... 86 »