Newsgroups: comp.os.minix
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!paladin.american.edu!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!howland.reston.ans.net!surfnet.nl!newshost.vu.nl!cs.vu.nl!kjb
From: kjb@cs.vu.nl (Kees J Bot)
Subject: Re: kernel mods
Nntp-Posting-Host: hornet.cs.vu.nl
References: <4h6qb6$36n@clams.camtech.com.au>
Sender: news@cs.vu.nl
Organization: Fac. Wiskunde & Informatica, VU, Amsterdam
Date: Mon, 4 Mar 1996 15:55:54 GMT
Message-ID: <Dnr2x6.G22.0.-s@cs.vu.nl>
Lines: 27

miko@hack.byron.apana.org.au (Miko) writes:

>hey i have a couple of questions for the kernel hackers out there :)

>the first one is.. that my computer has and extra part of memory which 
>may be used by the operating system.. the range is from c5000-fafff.. i 
>know that to do this for 1.3 you just added another hole to the hole 
>table (?) when the memory is initialised in alloc.c (mem_init) from what 
>i can tell the way it is initialised is different.. so how would i go 
>about doing this?? im still learning operating systems.. so.. :)

It might be easiest to modify kernel/misc.c::mem_init() instead of the
mem_init() in MM.  Should be easy.

>and also i have a driver that is for my scsi drive.. which runs using a 
>western digital chip.. and the procedure there was to just copy it to 
>wini.. however that apears to have changed aswell.. so how would i go 
>about making this fit?? can anyway give me some clues?? thanks

The disk drivers have been changed extensively.  The WD scsi driver
would have to be changed in the same manner, which may take quite some
time and effort.  If your system is an XT (why else would you want an
odd bit of memory at c5000?) then you can just as well use the BIOS
disk driver.  On an XT I see no reason at all to want a native driver.
--
	                        Kees J. Bot  (kjb@cs.vu.nl)
	              Systems Programmer, Vrije Universiteit Amsterdam
