@AlfredOne

Any chance of releasing some form of Multi-touch SDK? I'd love to see some games or paint programs using Multi-touch!

Cheers,
Bill

Hi balaton,

First, thank you for your work on Qemu for the AmigaOne systems; I'm super excited to see this coming to fruition.

I read through the forum here and came up with this process to git and build Qemu with AmigaOne support for my Ubuntu 20.04 Intel-based Linux box:


# git clone http://scm.osdn.net/gitroot/qmiga/qemu.git
# cd qemu
# git checkout amigaone
# ./configure
# make
# make install

The result was this:

# qemu-system-ppc -M help
Supported machines are:
40p IBM RS/6000 7020 (40p)
amigaone Eyetech AmigaOne/Mai Logic Teron
...

It looks good so far.

I then used AmiDVD to build a custom AmigaOne 4.1 Final Edition ISO image with the siliconmotion502.chip and updated both kicklayouts as directed in:

https://www.amigans.net/modules/newbb/ ... id=138684#forumpost138684

I created the u-boot-amigaone.bin and obtained the VGABIOS-lgpl-latest.bin file.

Then I start the machine with:
qemu-system-ppc \
-M amigaone \
-device VGA,romfile=VGABIOS-lgpl-latest.bin \
-device sm501 -accel tcg \
-drive if=none,id=cd \
-device ide-cd,drive=cd,bus=ide.1 \
-drive if=none,id=hd,file=AmigaOne.img,format=raw \
-device ide-hd,drive=hd,bus=ide.0 -m 2048 \
-device es1370 \
-rtc base=localtime \
-device rtl8139,netdev=network01 -netdev user,id=network01 \
-display sdl \
-serial stdio \
-d unimp,guest_errors \
-trace enable="via*"

At this point, I configured U-Boot to boot CDROM and started getting errors:

articia_reg_write: Unimplemented register write 0x80 1 <- 3a
articia_reg_write: Unimplemented register write 0x80 1 <- 3b
articia_reg_write: Unimplemented register write 0x80 1 <- 50
articia_reg_write: Unimplemented register write 0x80 1 <- 53
articia_reg_write: Unimplemented register write 0x80 1 <- 56
via_isa_write addr 0x85 val 0x3 len 0x1
via_superio_write addr 0xe2 val 0x1c
via_superio_cfg: unimplemented register 0xe2
via_superio_write addr 0xe6 val 0xde
via_superio_cfg: unimplemented register 0xe6
via_superio_write addr 0xe7 val 0xfe
via_superio_cfg: unimplemented register 0xe7
via_superio_write addr 0xe8 val 0xbe
via_superio_cfg: unimplemented register 0xe8
via_isa_write addr 0x85 val 0x1 len 0x1

Then this repeats forever:

via_isa_write addr 0x10 val 0xffffffff len 0x4
via_isa_write addr 0x14 val 0xffffffff len 0x4
via_isa_write addr 0x18 val 0xffffffff len 0x4
via_isa_write addr 0x1c val 0xffffffff len 0x4
via_isa_write addr 0x20 val 0xffffffff len 0x4
via_isa_write addr 0x24 val 0xffffffff len 0x4
via_pm_write addr 0x10 val 0xffffffff len 0x4
via_pm_write addr 0x14 val 0xffffffff len 0x4
via_pm_write addr 0x18 val 0xffffffff len 0x4
via_pm_write addr 0x1c val 0xffffffff len 0x4
via_pm_write addr 0x20 val 0xffffffff len 0x4
via_pm_write addr 0x24 val 0xffffffff len 0x4
Invalid read at addr 0xFD0E0000, size 1, region '(null)', reason: rejected
Invalid read at addr 0xFD0E0001, size 1, region '(null)', reason: rejected
Invalid read at addr 0xFD0E0002, size 1, region '(null)', reason: rejected
Invalid read at addr 0xFD0E0003, size 1, region '(null)', reason: rejected
Invalid read at addr 0xFD0E0004, size 1, region '(null)', reason: rejected
Invalid read at addr 0xFD0E0005, size 1, region '(null)', reason: rejected
...
Invalid read at addr 0xFD0E0FFD, size 1, region '(null)', reason: rejected
Invalid read at addr 0xFD0E0FFE, size 1, region '(null)', reason: rejected
Invalid read at addr 0xFD0E0FFF, size 1, region '(null)', reason: rejected
articia_reg_write: Unimplemented register write 0x80 1 <- b0
articia_reg_write: Unimplemented register write 0x80 1 <- b0

My virtual Sam460 is working well.

Thoughts on what I've done wrong?

cheers,
Bill "tekmage" Borsari

@all

Mr Toast put together this killer poster for AmiWest 2023, just a few weeks away!

Hi All,

I've put together a quick Devcon survey to help inform the AmiWest 2023 Devcon. You can take the survey here: https://forms.gle/S9bvJsqPzqN6TfPeA

Thanks!
Bill "tekmage" Borsari

@AmigaOldskooler

I always love reading the blog and getting a refresher on the monthly news. Also, I appreciate the AmiWest shoutout!

Cheers,
Bill

I have an X5000, and I'm also looking at getting an A1222+. I agree that limited hardware in the marketplace means every sale to an existing user does not grow our community. We know that A-Eon purchased 1500 CPUs back in the mid-2010s. We also understand that the T1022 is a challenging CPU choice due to SPE.

Let's assume AAA has used the full CPU inventory in this production run, and they will have 1500 units for sale when it's released (We don't know the production number, and there have been CPUs used in dev boards, etc., but let's assume for now.) If willing customers who already have OS 4 machines decide not to buy these systems so that other, net new AmigaOS 4 customers can, we open ourselves to more stagnation. That could create the worst-case situation with boards sitting on the shelf, unsold.

That will signal to the producers not to further invest in future boards or production. These sales generate revenue that can be used to further development. Right now, we are in a downward spire, and we need to change this to an upward spiral.

Consider this, Amedia Computer has two different OS 4 systems for sale right now, the X5000/40 and the Sam460le. All indications show that the A1222+ will be available this year too. That means we will have 3 different AmigaOS 4 compatible systems commercially available in 2023. We have not seen that since the early 2010s with AmigaOne and Sam's.

Bottom line, if you want to buy one of those boards, do it! Buy 10. The only way AmigaOS 4 will survive is if these systems sell.

We must reward those who take the risk to produce HW for our beloved OS.

Hi All,



It looks like I'm unable to reply to the news thread with links, so here are the photos I took on Friday. The Amiga's presence at the event was much more significant than I had expected. My visit was cut short, so I only at a chance to take a few photos.

Click here to view the gallery


Bill "tekmage" Borsari
Don't forget to check out AmiWest

I've been looking at Ghostscript, which has an impressive array of capabilities, including a PCL engine. Our port is old, and an update would go a long way for most users.

The build instructions are here: https://ghostscript.readthedocs.io/en/latest/Make.html

Happy porting!

Bill "tekmage" Borsari

Hi All,

I was looking at the DCRAW package and saw the libgphoto2 work. A few things are interesting about libgphoto2.

First, it's still under development and supports the latest cameras.

Second, it has a 'port' capability for talking directly to cameras which is beyond what PTP can do.

Third, it has a fuse module so camera's can be mounted directly to the systems.

Fourth, I think it would be possible to leverage libgphoto2 in a datatype that would unlock the world of RAW images for any format within our beloved tools.

The code is here: https://github.com/gphoto/libgphoto2

Cheers,
Bill "tekmage" Borsari

PS, Eldee will ask for an SPE-compiled version!

Machine: Qemu 460EX Intel(R) Xeon(R) CPU E31265L @ 2.40GHz

7.Workbench:> Benchmarks/CPUBench/CPUBench.script
CPUBench v1.0


RageMem:
RageMem/RageMem: Unknown command
7.Workbench:> cd Benchmarks/CPUBench/
7.Workbench:Benchmarks/CPUBench> CPUBench-results-5-24-2023
CPUBench-results-5-24-2023: file is not executable
7.Workbench:Benchmarks/CPUBench> CPUBench.script
CPUBench v1.0


RageMem:

RAGEMEM v0.37 - compiled 11/06/2010

CPU: AMCC PPC460EX 1.2 @ 1150 Mhz
Caches Sizes: L1: 32 KB - L2: 256 KB - L3: none
Cache Line: 32

---> CPU <---
MAX MIPS: 2913

---> L1 <---
READ32: 1901 MB/Sec
READ64: 2841 MB/Sec
WRITE32: 1822 MB/Sec
WRITE64: 3109 MB/Sec

---> L2 <---
READ32: 185 MB/Sec
READ64: 203 MB/Sec
WRITE32: 184 MB/Sec
WRITE64: 196 MB/Sec

---> RAM <---
READ32: 184 MB/Sec
READ64: 192 MB/Sec
WRITE32: 185 MB/Sec
WRITE64: 194 MB/Sec
WRITE: 163 MB/Sec (Tricky)

---> VIDEO BUS <---
READ: 200 MB/Sec
WRITE: 105 MB/Sec



SortBench:
-------------------------------------------------------------
SORTBENCH 1.1 (Gunnar von Boehn)
Its a CPU benchmark that stresses CPU, DCache and branch prediction.
-------------------------------------------------------------
1 K Element : 742.50 MB/sec
2 K Element : 697.66 MB/sec
4 K Element : 778.47 MB/sec
8 K Element : 720.20 MB/sec
16 K Element : 748.09 MB/sec
32 K Element : 443.68 MB/sec


BogoMIPS:
Calibrating delay loop..

Ok - 160.00 BogoMips



Dhrystone:
Dhrystone Benchmark, Version 2.1 (Language: C)
Program compiled without 'register' attribute

Execution starts, 50000000 runs through Dhrystone
Execution ends

Final values of the variables used in the benchmark:

Int_Glob: 5
should be: 5
Bool_Glob: 1
should be: 1
Ch_1_Glob: A
should be: A
Ch_2_Glob: B
should be: B
Arr_1_Glob[8]: 7
should be: 7
Arr_2_Glob[8][7]: 50000010
should be: Number_Of_Runs + 10
Ptr_Glob->
Ptr_Comp: 1831520336
should be: (implementation-dependent)
Discr: 0
should be: 0
Enum_Comp: 2
should be: 2
Int_Comp: 17
should be: 17
Str_Comp: DHRYSTONE PROGRAM, SOME STRING
should be: DHRYSTONE PROGRAM, SOME STRING
Next_Ptr_Glob->
Ptr_Comp: 1831520336
should be: (implementation-dependent), same as above
Discr: 0
should be: 0
Enum_Comp: 1
should be: 1
Int_Comp: 18
should be: 18
Str_Comp: DHRYSTONE PROGRAM, SOME STRING
should be: DHRYSTONE PROGRAM, SOME STRING
Int_1_Loc: 5
should be: 5
Int_2_Loc: 13
should be: 13
Int_3_Loc: 7
should be: 7
Enum_Loc: 1
should be: 1
Str_1_Loc: DHRYSTONE PROGRAM, 1'ST STRING
should be: DHRYSTONE PROGRAM, 1'ST STRING
Str_2_Loc: DHRYSTONE PROGRAM, 2'ND STRING
should be: DHRYSTONE PROGRAM, 2'ND STRING

Duration in seconds: 458.7
Microseconds for one run through Dhrystone: 9.2
Dhrystones per Second: 108997.6
Dhrystone MIPS (DMIPS) 62



Quicksort:
Elaborating quicksort of 1000 numbers repeated for 10 times
Unsorted array:
<clip>
Sorted array:
<clip>
Total time taken by CPU: 9.10


Sieve:

Sieve of Eratosthenes (Scaled to 10 Iterations)
Version 1.2, 03 April 1992

Array Size Number Last Prime Linear RunTime MIPS
(Bytes) of Primes Time(sec) (Sec)
8191 1899 16381 0.002632 0.002632 629.9
10000 2261 19997 0.003213 0.003033 670.0
20000 4202 39989 0.006427 0.005684 724.2
40000 7836 79999 0.012854 0.016022 520.1
80000 14683 160001 0.025708 0.033569 502.2
160000 27607 319993 0.051415 6.543884 5.2
320000 52073 639997 0.102831 20.197144 3.4
640000 98609 1279997 0.205661 46.981201 3.0
1280000 187133 2559989 0.411322 117.324219 2.4
2560000 356243 5119997 0.822645 255.551758 2.2
5120000 679460 10239989 1.645289 613.300781 1.9
10240000 1299068 20479999 3.290578 1366.015625 1.7
20480000 2488465 40960001 6.581156 3063.984375 1.5

Relative to 10 Iterations and the 8191 Array Size:
Average RunTime = 0.487321 (sec)
High MIPS = 724.2
Low MIPS = 1.5



Whetstone:

Please wait...

Loops: 50000 Iterations: 1 Duration: 67.8 seconds
C Converted Double Precision Whetstones: 73.8 MIPS


All tests done.
7.Workbench:Benchmarks/CPUBench>
160001 0.021982 0.025787 653.8
160000 27607 319993 0.043964 5.501556 6.2
320000 52073 639997 0.087928 15.746765 4.4
640000 98609 1279997 0.175855 45.649414 3.0
1280000 187133 2559989 0.351710 108.325195 2.6
2560000 356243 5119997 0.703421 234.252930 2.4
5120000 679460 10239989 1.406841 556.298828 2.1
10240000 1299068 20479999 2.813683 1125.214844 2.0
20480000 2488465 40960001 5.627366 2732.617188 1.7

Relative to 10 Iterations and the 8191 Array Size:
Average RunTime = 0.431285 (sec)
High MIPS = 791.5
Low MIPS = 1.7



Whetstone:

Please wait...

Loops: 50000 Iterations: 1 Duration: 57.8 seconds
C Converted Double Precision Whetstones: 86.6 MIPS

X5000/20:

RageMem:

RAGEMEM v0.37 - compiled 11/06/2010

CPU: Freescale P5020 (E5500 core) 1.2 @ 1995 Mhz
Caches Sizes: L1: 32 KB - L2: 512 KB - L3: none
Cache Line: 64

---> CPU <---
MAX MIPS: 3988

---> L1 <---
READ32: 7532 MB/Sec
READ64: 15041 MB/Sec
WRITE32: 7533 MB/Sec
WRITE64: 15045 MB/Sec

---> L2 <---
READ32: 4286 MB/Sec
READ64: 7708 MB/Sec
WRITE32: 5020 MB/Sec
WRITE64: 8813 MB/Sec

---> RAM <---
READ32: 732 MB/Sec
READ64: 1341 MB/Sec
WRITE32: 1748 MB/Sec
WRITE64: 1754 MB/Sec
WRITE: 2320 MB/Sec (Tricky)

---> VIDEO BUS <---
READ: 22 MB/Sec
WRITE: 535 MB/Sec



SortBench:
-------------------------------------------------------------
SORTBENCH 1.1 (Gunnar von Boehn)
Its a CPU benchmark that stresses CPU, DCache and branch prediction.
-------------------------------------------------------------
1 K Element : 3720.51 MB/sec
2 K Element : 3696.03 MB/sec
4 K Element : 3682.75 MB/sec
8 K Element : 3761.76 MB/sec
16 K Element : 3316.98 MB/sec
32 K Element : 3272.27 MB/sec


BogoMIPS:
Calibrating delay loop..

Ok - 320.00 BogoMips



Dhrystone:
Dhrystone Benchmark, Version 2.1 (Language: C)
Program compiled without 'register' attribute

Execution starts, 50000000 runs through Dhrystone
Execution ends

Final values of the variables used in the benchmark:

Int_Glob: 5
should be: 5
Bool_Glob: 1
should be: 1
Ch_1_Glob: A
should be: A
Ch_2_Glob: B
should be: B
Arr_1_Glob[8]: 7
should be: 7
Arr_2_Glob[8][7]: 50000010
should be: Number_Of_Runs + 10
Ptr_Glob->
Ptr_Comp: 1405485704
should be: (implementation-dependent)
Discr: 0
should be: 0
Enum_Comp: 2
should be: 2
Int_Comp: 17
should be: 17
Str_Comp: DHRYSTONE PROGRAM, SOME STRING
should be: DHRYSTONE PROGRAM, SOME STRING
Next_Ptr_Glob->
Ptr_Comp: 1405485704
should be: (implementation-dependent), same as above
Discr: 0
should be: 0
Enum_Comp: 1
should be: 1
Int_Comp: 18
should be: 18
Str_Comp: DHRYSTONE PROGRAM, SOME STRING
should be: DHRYSTONE PROGRAM, SOME STRING
Int_1_Loc: 5
should be: 5
Int_2_Loc: 13
should be: 13
Int_3_Loc: 7
should be: 7
Enum_Loc: 1
should be: 1
Str_1_Loc: DHRYSTONE PROGRAM, 1'ST STRING
should be: DHRYSTONE PROGRAM, 1'ST STRING
Str_2_Loc: DHRYSTONE PROGRAM, 2'ND STRING
should be: DHRYSTONE PROGRAM, 2'ND STRING

Duration in seconds: 26.0
Microseconds for one run through Dhrystone: 0.5
Dhrystones per Second: 1923210.4
Dhrystone MIPS (DMIPS) 1094



Quicksort:
Elaborating quicksort of 1000 numbers repeated for 10 times
Unsorted array:
<clip>
Sorted array:
<clip>
Total time taken by CPU: 2.76


Sieve:

Sieve of Eratosthenes (Scaled to 10 Iterations)
Version 1.2, 03 April 1992

Array Size Number Last Prime Linear RunTime MIPS
(Bytes) of Primes Time(sec) (Sec)
8191 1899 16381 0.000877 0.000877 1889.7
10000 2261 19997 0.001071 0.001068 1902.2
20000 4202 39989 0.002142 0.001945 2115.8
40000 7836 79999 0.004285 0.004730 1761.7
80000 14683 160001 0.008569 0.009308 1811.3
160000 27607 319993 0.017138 0.018921 1801.6
320000 52073 639997 0.034277 0.040283 1710.0
640000 98609 1279997 0.068554 0.100098 1389.9
1280000 187133 2559989 0.137107 0.275879 1018.1
2560000 356243 5119997 0.274215 1.098633 515.9
5120000 679460 10239989 0.548430 3.554688 321.6
10240000 1299068 20479999 1.096859 8.789062 262.3
20480000 2488465 40960001 2.193719 19.804688 234.6

Relative to 10 Iterations and the 8191 Array Size:
Average RunTime = 0.002590 (sec)
High MIPS = 2115.8
Low MIPS = 234.6



Whetstone:

Please wait...

Loops: 50000 Iterations: 1 Duration: 8.5 seconds
C Converted Double Precision Whetstones: 590.7 MIPS


All tests done.

Check out this discussion:
https://www.amigans.net/modules/news/article.php?storyid=3096

@328gts

Dude! Impressive score.

@Ami603

Check back on comment #50. I've emailed the support email at Onyxsoft and did not get a reply. If you have a better way to reach Daniel, please do!

Cheers,
Bill "tekmage" Borsari

@salass00

Fixed the standard ASL:

TEKMAGE: 9T 8,067G 2,170G 79% -1 Read/Write 10.0.0.20-space SMB\02

Backup still has an issue. I suspect the problem is now with Backup and its ability to deal with the 10T volume.

I'll reach out to OnyxSoft and see what they say :)

Thanks!
Bill "tekmage" Borsari

Thanks for the tool!

17.RAM Disk:> smb2-statvfs-sync smb://tekmage:*************@10.0.0.20/space
Blocksize:1024
Blocks:10735329280
Free:2315610508
Avail:2315610508
17.RAM Disk:> smb2-statvfs-sync smb://tekmage:************@10.0.0.20/Media
Blocksize:1024
Blocks:10735329280
Free:2315590144
Avail:2315590144

@salass00

Thank you for this work! I'm blown away by the performance of this code, I seen over 50 MB/s moving large files, never seen that on my X5000 before...

I have hit a snag. I went to back up my system using the Onyxsoft.se "backup" tool and I'm not able to even select the device from the file requester.

I'm mounting from my Linux machine and can move data both directions using the copy command from the CLI with no issues. Here is what "c:info" shows:

MEDIA: 2,046G 3,896G 2,245G 62% -1 Read/Write 10.0.0.20-Media SMB\02
TEKMAGE: 2,046G 3,896G 2,245G 62% -1 Read/Write 10.0.0.20-space SMB\02


However, when I use backup's file requester it reports the devices a 100% full, and more interesting, when I use something like multiview and list all the devices I see the drives as "190% full."

(MEDIA) 190% full, 2,245GB free, 3,896.9GB in use

When I mount the same partition using smbfs I see a different space accounting:

c:info
nas2: 2,047G 0K 2,047G 0% 1 Read/Write space DOS\00

ASL:
(nas2) 0% full, 2,047GB free, 512B in use


Thoughts?

Cheers,
Bill "tekmage" Borsari

@AmigaOldskooler

I love reading these posts! Keep it coming.

Cheers,
Bill "tekmage" Borsari

@kas1e

I was hoping to get a list of apps that work so I can explore and discover or re-discover new things :)

Hi All,

With the release of NovaBridge this week I thought it might be nice to start a thread on app compatibility. My goal is to have a thread where people can post things that work or are not working with the new library.

It would also be helpful to have some notes like OS version, machine type, and video card.

I'll start!


=================
Teeworlds
X5000, OS 4.1 FE Update 2 + beta
Enhancer 2.2
RX580

Status: Runs without issue
================

Who else to jump in?

Cheers,
Bill "tekmage" Borsari