>>>>> On 16 Aug 1993 07:51:37 EST,
>>>>> In message <CBurq3.
...@sse.ie>,
>>>>> mulla
...@sse.ie (Ronan Mullally) wrote:
Ronan> bootstrap -k vmlinux -r ramdisk.img ?
If you have a 68040 it's going to crash, because Linux/68k doesn't yet
support the 68040.
If you have a 68EC030, it's going to crash, because you don't have a
functioning MMU.
If you have AGA with a full 68030, I don't know what would happen,
because I don't know of anybody who has tried this yet. I don't know
if the current display code can display anything on AGA graphics.
Ronan> [...] and perhaps because the MMU in my EC030 isn't quite up to
Ronan> the job. I hope it's one of the first two! The MMU works very
Ronan> well with Enforcer, and *seems* to be OK, but then again...
If you have a 68EC030, then the MMU doesn't work at all. You just
*think* it does because enforcer catches *some* illegal accesses.
Enforcer can catch illegal accesses to non-existent memory, because
the computer hardware generates a bus fault, which enforcer can
decode. Enforcer uses the MMU to protect certain chunks of valid
memory in the Amiga (e.g. ROM, exception vectors). If your MMU
doesn't work, then enforcer won't catch any accesses (e.g. a write to
ROM) to these areas.
If you run the "lawbreaker" program which comes with enforcer, you'll
probably find that it only catches one enforcer hit (an access to a
non-existent address). If your MMU was functioning properly, it would
catch a number of hits, including a few accesses to low memory.
|
