AROS for Amiga OS (AFA OS) 4.6

[unusedunused]

Sorry, but i forgot an important factor regarding this issue.
Were you running AOS 3.9 when you did the tests? If you didn't, then the OS was using a 68k-only picture.datatype, which would explain why you did not experience better performance due to the excessive context switching, as you said. What i wrote is true for AOS 3.9 where the picture.datatype is 68/PPC.

I dont see that there was a PPC picuture datatype.where is it ?.I use OS3.5 or maybe 3.1.I dont remember i do my tests when i get ppc card and there come PPC datatypes.My classic have only AOS 3.5.

But I was not the only that notice not much speedup with PPC.I get values from wawa 180 MHZ 604e OS3.9 and warp ppc jpg datatype(i dont have) user that show that 68k speed and PPC jpg speed near same.


i know CGX (and powerup devs) are maybe able to do it, but most programs use warpup.

If there is any there must be a version that work on warpup, because most programs use warpup.

on my past PPC days i use some programs with powerup, but most with warpup.so i need switch sometimes.but when use ppc datatypes this do not allow a switch.


In my tests i use a free ppc jpg datatype(forget the name) and this was not faster as 68k asm optimized datatype.

I test then the warp PPC demo datatype it was fasterr but it do not show colors.
So i guess the speedup was because there was no colors show.

normaly programs on 604 work 5-10 times faster than on my 68060 and the jpegs i test are big (need 3-10 sec to load on 68k.

So i see the PPC datatypes do not speedup.

----------------

That wbclock progam crash on AFA is maybe the reason, because you use a non 4 color Icon or you should increase the stack.

You mean that ?
http://aminet.net/package/util/time/wbclock

this program is written 1994 and show the clock on a Icon, nice idea btw,but there was no OS command that let set you Icondata before AOS3.5.

So this cant work on Icons other than 4-8 colors old Icons.

but i think you can get it working, when you choose in the wblock Option file a 4 Color Icon.

AFA use AROS iconlib complete and the struct for the 4 color Icons is same as in AOS.

but nice, there is sourcecode here, maybe this compile somebody to work on clean way.
It can then too working on MOS and OS4 or AROS.

[Piru]

...
So i see the PPC datatypes do not speedup.

Your reasoning is so fecked up it's not even funny anymore.

[kolla]

Your reasoning is so fecked up it's not even funny anymore.

How lovely of you to drop by with this insightfull comment :laughing:

@bernd
In OS3.9 the picture.datatype is "fat" binary, both PPC and 68k at once, just so you know.

[Karlos]

Re: PPC datatypes on OS3.x

Under 3.5, I noticed a major speedup when moving to PPC datatypes for jpeg, png etc. I noticed a similar speed up when I eventually got OS3.9 and it's image.datatype. The latter accelerated the rendering of the decoded image. I believe that it has PPC support for colour conversion/dithering? Either way, the speed increases over the 040 were highly conspicuous.

[unusedunused]

Re: PPC datatypes on OS3.x

Under 3.5, I noticed a major speedup when moving to PPC datatypes for jpeg, png etc. I noticed a similar speed up when I eventually got OS3.9 and it's image.datatype. The latter accelerated the rendering of the decoded image. I believe that it has PPC support for colour conversion/dithering? Either way, the speed increases over the 040 were highly conspicuous.

You mean you have a 68040 compare with a PPC ?

The 68060 is lots faster, more than 2-3 times.so when use a 68040 its clear PPC is faster

I find values from the test.the real time differ lots, its the time to close the window.the important time is PCPU and TCPU.

when hand stop there is no diffrence notice but this program show that 180 MHZ PPC is slightly faster.the test is done 3 times.

i think a faster PPC does not help much, because the context switch time is not speed up with faster PPC.

Maybe a user can measure how fast the speedup is on his system with and without PPC jpg datatype on his 68060 CPU

when the picture datatype is fat binary then in the test the ppc code in picture datatype should use


>> 68k jpg
>>
>> 18.Ram Disk:> multiview nsos4bbc.jpg
>> 18.Ram Disk:> cputime multiview nsos4bbc.jpg
>> Real 00:00:15.445, PCPU 00:00:03.010, TCPU 00:00:04.513
>> 18.Ram Disk:> cputime multiview nsos4bbc.jpg
>> Real 00:00:06.006, PCPU 00:00:02.988, TCPU 00:00:04.495
>> 18.Ram Disk:> cputime multiview nsos4bbc.jpg
>> Real 00:00:14.825, PCPU 00:00:02.858, TCPU 00:00:04.360
>>
>> ppc jpg
>>
>> 17.Ram Disk:> cputime multiview nsos4bbc.jpg
>> Real 00:00:09.537, PCPU 00:00:02.975, TCPU 00:00:04.475
>> 17.Ram Disk:> cputime multiview nsos4bbc.jpg
>> Real 00:00:08.454, PCPU 00:00:02.992, TCPU 00:00:04.493
>> 17.Ram Disk:> cputime multiview nsos4bbc.jpg
>> Real 00:00:07.158, PCPU 00:00:02.989, TCPU 00:00:04.490

[carvedeye]

Sorry to start up an old thread but i would love to get afa os installed on my miggy but i need to know exactly what i need to type in the start-up sequence and where ?

TIA

[Calimeiro]

After all, i found out that your card has no fpu which is required for AfA to run. You know the correct setup already from the other thread, it hasn't changed since.