@geennaam I'm not sure how much the emulation of the sm501 is slowing it down but at least converting from 16 bit to 32 bit should run in the display thread so that may not affect vcpu thread. The device emulation itself may cause some slow down but I only plan to address that with ati-vga eventually. If you do qemu-system-ppc -device sm501,help it lists device parameters. One parameter I've added is this:
which can be set to control which operations are tried to be accelerated with pixman. By defaiult all are enabled but this may be dependent on your host so what you could do is run Hans's gfxbench once with default setting and once with -device sm501,x-pixman=0 and compare the numbers then find the value that's fastest on your machine. (If you do that also share the results so we know which system needs which values.)
qemu-system-ppc --version QEMU emulator version 8.0.91 (v8.1.0-rc1-35-gccdd312676) Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers
sepate note:
Meanwhile i also tried qemu with voodoo 3 screen via winuae if i select the ip address of winuae+voodoo3 with qemu the firefox screen opens correctly on the winuae+voodoo display then without a private key and it works.
Today I try with the old Nexus 7 with Kali NetHunter with the "modified rom of Nexus 7" now the battery is almost empty. To see if NetHunter works correctly with SSH it lets me open the Display.
Edited by white on 2023/8/2 13:59:27 Edited by white on 2023/8/2 14:14:07 Edited by white on 2023/8/2 14:33:57 Edited by white on 2023/8/2 15:15:31 Edited by white on 2023/8/2 15:52:53 Edited by white on 2023/8/2 15:54:25
Thank you very much for this new version of the SM502 driver. I am still at work, but testing the new resolutions with AmigaOs 4.1 is what I am looking forward to the most.
Ok thanks now it works. Performed with kickstart nvram.config peg2ide_xfer=FFFF and peg2ide_irq=1111 Here the result:
Much faster than real Pegasos2 hardware, maybe even faster than any real Amiga hardware using a HDD or SSD with a PATA or SATA controller, only nvme.device in a X1000/X5000/A1222 is faster.
The AmigaOS 4.x PATA drivers support up to UDMA5 (100 MB/s), but the AmigaOne SE/XE/µA1 and Pegasos2 hardware is slower. The max. speed I got on an AmigaOne XE was ~65 MB/s, but that was using PCI SATA cards, not with the onboard PATA.
joerg wrote:@Maijestro Much faster than real Pegasos2 hardware, maybe even faster than any real Amiga hardware using a HDD or SSD with a PATA or SATA controller, only nvme.device in a X1000/X5000/A1222 is faster.
The AmigaOS 4.x PATA drivers support up to UDMA5 (100 MB/s), but the AmigaOne SE/XE/µA1 and Pegasos2 hardware is slower. The max. speed I got on an AmigaOne XE was ~65 MB/s, but that was using PCI SATA cards, not with the onboard PATA.
Thank you for looking at this. I could not do anything with these numbers.
This confirms that the HD part of Qemu works and there is nothing to improve here, as it already seems to be faster than under real hardware.
The new driver is currently on OS4Depot uploads queue
I have to thank them again fantastic work. The new driver works perfectly under Qemu AmigaOs4.1, all resolutions the driver offers can be used. Tested with BBoot 0.4 and OpenFirmware Pegasos 2
Whether the write speed has improved I can not say yet, but I will test it. The Workbench looks a bit nicer in 1600x900 and there is more space, plus this resolution is also offered by my host system, which was not the case before.
@all here if it can be useful in any way qemu which exports DISPLAY into WinUAE screen without problems. maybe a solution can be found (AmiCygnix) I don't know what exactly is due in this case maybe the graphics driver. Anyone who knows more than me can observe how it works and maybe find a solution. Thank you.
if I can today I try with the nexus 7 tablet with SSH as server with "nethunter" it would be nice if it worked. it would be a small server on the Tablet
also tried "browservice" with qemu works seamlessly with Odyssey proxy I didn't make the video but it works.
It would be interesting to see what numbers @Hans gets for the same scsispeed test to see if it's slower there or it's really just slower compiling code with TCG.
It would be interesting to see what numbers @Hans gets for the same scsispeed test to see if it's slower there or it's really just slower compiling code with TCG.
Testing with a 512 byte, MEMF_FAST, LONG-aligned buffer.
Read from SCSI: 639236 bytes/sec
Testing with a 16384 byte, MEMF_FAST, LONG-aligned buffer.
Read from SCSI: 17973734 bytes/sec
Testing with a 1048576 byte, MEMF_FAST, LONG-aligned buffer.
Read from SCSI: 79691776 bytes/sec
Testing with a 16777216 byte, MEMF_FAST, LONG-aligned buffer.
Read from SCSI: 76260072 bytes/sec
To me, it looks like the whole system is sluggish. For example, the AmiDOCK icon flashing is visibly slower than on my PowerPC machines (when starting a program from the dock).
Don't really want to interrupt, but is that new SM502 driver meant to support 2560x1440? because it doesn't offer it to me regardless of whether I manually add the resolution or not.
MartinW wrote:Don't really want to interrupt, but is that new SM502 driver meant to support 2560x1440? because it doesn't offer it to me regardless of whether I manually add the resolution or not.
Quote:
-enabled videomodes up to 4096 x 2048, due restrictions on real hardware the expected maximum working resolution is 1920x1080
That's what the description says, whatever that's supposed to mean. I personally don't need a higher resolution like 1600x900.
It would be interesting to see what numbers @Hans gets for the same scsispeed test to see if it's slower there or it's really just slower compiling code with TCG.
Perhaps the benchmark tool, should display powerpc cpu, not the emulated 680x0 cpu.
It's a benchmark tool from 1989-1992, implemented by one of the AmigaOS 0.x-2.x developers, and at that time there were no PowerPC CPUs in Amigas yet Only some very minor changes had to be, and were, done in the AmigaOS 4.x versions... It's called SCSISpeed and nobody is using SCSI any more, but it's still working for benchmarking PATA, SATA, USB, NVMe, etc. drivers and hardware.
Oh well, it is what it is. I guess the "due to restrictions" limitation is coming into play. It just means that on my external monitor I still can't go full screen. I don't know why but Qemu scales really, really badly.
Oh well, it is what it is. I guess the "due to restrictions" limitation is coming into play. It just means that on my external monitor I still can't go full screen. I don't know why but Qemu scales really, really badly.
I had exactly the same problem. Host and guest should have the same resolution then the full screen works fine. Qemu doesn't seem to like different resolutions on host and guest system.
I had mentioned that Qemu scales badly months ago, but nobody cared.
This driver apparently works great with latest 4.1FE Update 2 but seems to crash with vanilla 4.1FE. This is a problem for people who try to add this driver to a 4.1FE install CD to boot on QEMU to be able to install it. With the amigaone version on QEMU for example I get with siliconmotion502.chip v53.12:
Dump of context at 0x01AA9250
Trap type: DSI exception
Machine State (raw): 0x0000B030
Machine State (verbose): [ExtInt on] [Super] [FPU on] [IAT on] [DAT on]
Temporary stack trace:
#0: in module Kickstart/kernel+0x00027A30 (0x01227A30)
#1: in module Kickstart/kernel+0x00043250 (0x01243250)
#2: in module Kickstart/kernel+0x00026A94 (0x01226A94)
#3: in module Kickstart/kernel+0x00026AD0 (0x01226AD0)
#4: in module Kickstart/siliconmotion502.chip+0x000041F8 (0x01619F78)
#5: in module Kickstart/siliconmotion502.chip+0x000000AC (0x01615E2C)
#6: in module Kickstart/kernel+0x000259E4 (0x012259E4)
#7: in module Kickstart/PCIGraphics.card+0x00000B6C (0x015F486C)
#8: in module Kickstart/graphics.library.kmod+0x00035140 (0x013D31A0)
#9: in module Kickstart/graphics.library.kmod+0x00033D58 (0x013D1DB8)
#10: in module Kickstart/graphics.library.kmod+0x00000F38 (0x0139EF98)
#11: in module Kickstart/kernel+0x00025658 (0x01225658)
#12: in module Kickstart/kernel+0x000255C0 (0x012255C0)
#13: in module Kickstart/kernel+0x00026438 (0x01226438)
#14: in module Kickstart/kernel+0x00025658 (0x01225658)
#15: in module Kickstart/kernel+0x000255C0 (0x012255C0)
#16: in module Kickstart/kernel+0x00024C74 (0x01224C74)
#17: in module Kickstart/kernel+0x0001375C (0x0121375C)
Crashed task: exec.task (0x6FFAA1E0)
DSI verbose error description: Access not found in hash or BAT (page fault)
Access was a load operation
0: 00000010 01A80200 00000400 6FF92E10 00000001 00000028 00000028 00000000
8: 00092170 00000000 01BC68E2 6FF92E10 28024044 00000000 6FF23000 6FF6E010
16: 6FFB4770 01C6A654 01C70000 01A557C0 01C70000 6FF5F150 6FF965A4 01C70000
24: 00000001 8000000C 00000028 6FF4B5C0 00000001 01AB2B84 00000000 6FF92E10
CR: 48024044 XER: 00000000 CTR: 01219A0C LR: 01219A24
DSISR: 40000000 DAR: 00000001
but the older siliconmotion502 versions work with 4.1FE so installation currently needs using two versions. Is there a chance to fix the newest driver to also work with 4.1FE without updates?
Other question is if you have sources of the AmigaOne SE/XE/uA1 u-boot could you pass it to me please?
but the older siliconmotion502 versions work with 4.1FE so installation currently needs using two versions. Is there a chance to fix the newest driver to also work with 4.1FE without updates?
There is another source besides Hyperion-Entertainment and that is archive.org where you could get AmigaOs4.1 Update 3, but I am not sure if this site is reputable and allowed to link to it.
Only registered users who registered AmigaOs4.1 before the Final Edition have access to Update 3, which of course makes sense.So the only solution at the moment would be to fix the Silicon Motion chip so that it works with the Final Edition of AmigaOs4.1 without Update 1 and 2.
Maybe there were also changes in update 2 that allow the driver to support higher resolutions.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
