[comp.os.minix] Minix 68k queries

akarkare@eecs.wsu.edu (Ashish Karkare) (10/17/90)

Hello Minix Gurus,

I had a few queries regarding Minix in a 68k environment. They are as 
follows:

1. Is it possible to make the Minix kernel ROMable? This might allow us to
play around with diskless versions of Minix.

2. The Atari ST minix requires 1k per task as opposed to the 512 bytes of
PC Minix. Why is this so ?

3. Does Minix require a physically (logically) contiguous memory? 

4. What changes need to be made if the kernel image is to be made relocatable?

If anyone out there has had an experience with any of the above ideas, or
has suggestions regarding any of the above problems, I would greatly
appreciate your response.

Thanx in anticipation,


Ashish Karkare
(akarkare@yoda.eecs.wsu.edu)

PS: Please post replies to the above address if the topic is not one of 
interest to the group.
-- 
**************************************************************************
*   Ashish Karkare                   INTERNET:akarkare@yoda.eecs.wsu.edu *
*   Computer Sc. Dept.               BITNET  :63007891@wsuvm1            * 
*   Washington State U.              TALKNET :  509 332 8699             *

HBO043%DJUKFA11.BITNET@cunyvm.cuny.edu (Christoph van Wuellen) (10/19/90)

I am pretending to be an 68k guru, but nevertheless....

1.) Kernel ROMable.... hmm, if you put the data segment into RAM, this
    might go, but you have to initialize the data segment (in RAM) from
    ROM tables.

2.) 1K/task: return addresses are 32 bit on an Atari (so are pointers), that
    is twice as much as on PC

3.) contiguous memory: not needed, but you have to change that memtable
    initialiation in MM, which takes a single chunk. It is not possible to
    segment a process!

4.) Relocatable kernel: The kernel itself is relocatable and gets relocated
    by the build utility when creating an OS image for a fixed address,
    (0, in the common cases)
    you can relocate the kernel for other addresses, perhaps at boot-time,
    but you have to change the brain-damaged definition of the interrupt
    vectors (sorry, Frans) as a pair of two 16-bit values (these won't get
    relocated properly.

Christoph van Wuellen.

evans@syd.dit.CSIRO.AU (Bruce.Evans) (10/23/90)

In article <1990Oct17.164053.27568@eecs.wsu.edu> akarkare@eecs.wsu.edu (Ashish Karkare) writes:
>1. Is it possible to make the Minix kernel ROMable? This might allow us to
>play around with diskless versions of Minix.

No reason why not. At worst you can copy the whole thing to RAM. Relocation
may be slightly harder for the 68K.

>2. The Atari ST minix requires 1k per task as opposed to the 512 bytes of
>PC Minix. Why is this so ?

1k for task stacks? Tasks themselves mostly take much more. The stack sizes
are mostly 512 for Minix-ST and 256 for Minix-PC. The 68000 has larger pointers
than the 8086, so more stack is required.

>3. Does Minix require a physically (logically) contiguous memory? 

No, provided there are contiguous blocks large enough to hold processes.
Disconnected memory leads to more wastage from fragmentation.
-- 
Bruce Evans		evans@syd.dit.csiro.au