Welcome, Guest. Please login or register.

Author Topic: Vampire, Gotek, 68000, misteries, doubts, questions...  (Read 2638 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Motormouth

Re: Vampire, Gotek, 68000, misteries, doubts, questions...
« on: September 10, 2017, 03:14:35 PM »
Quote from: Thomas Richter;830510
.

Note that Kickstart 1.3 only supports CPUs up to the 68020. This *might* be a problem, but I do not know.


@Thomas Richter
I have head this before, but we (where I worked) had both a amiga 2500 (ie an A2000 with an A2630 board) and an A2000 with a GVP board with 50 Mhz 68030 board, (was using lightwave and the toaster).  I never really had much issue with 030.  It most worked fine with 1.3.3 and well written workbench apps.
The only issue was some old programs that did not like high mapped 32 bit memory,  I would always map the memory high when possible and have some 16 bit ram (usually at least 2 megs) in the 8meg space for compatibility.

Now as for games that banged the copper, most did not work with even with 68020 as you can guess.


Things got squirrelly with the 68040, We had bought a fusion forty.  The 040 had to be patched to work with 1.3.  It worked fine with lightwave and the toaster (with the patches), but not with all our software.  Luckily it was lightwave we needed.
« Last Edit: September 10, 2017, 03:20:20 PM by Motormouth »
 

Offline Motormouth

Re: Vampire, Gotek, 68000, misteries, doubts, questions...
« Reply #1 on: September 11, 2017, 01:40:09 AM »
Quote from: Thomas Richter;830524
That's not quite the point. This is from the 1.3 exec/execbase:

Code: [Select]

/******* AttnFlags */
/*  Processors and Co-processors: */
#define AFB_68010       0       /* also set for 68020 */
#define AFB_68020       1
#define AFB_68881       4  
#define AFF_68010       (1<<0)
#define AFF_68020       (1<<1)
#define AFF_68881       (1<<4)

IOWs, the 1.3 exec did not detect and did not signal the 68030. That's what I meant that "it is not supported".   Yes, it typically makes little difference, and the cache of the 68030 (which is really the major difference from an Os perspetive) is small enough so it *typically* does not hurt.  


Kick 1.3 had no provision to flush caches, and no Os interface for this either. Code had to do it itself, though the 256 bytes of cache were small enough to cause trouble only in rare cases.

Thus, 1.3 worked on the 68020 by chance, not by design, and had no idea about the 68030. All that came with v37.


@Thomas Richter

Ahh, Ok I get it.