Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!masscomp!rpi!crdgw1!sixhub!davidsen
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.unix.sysv386
Subject: Re: memory mapping (was: '386 Unix Wars)
Keywords: sco unix interactive wars
Message-ID: <2732@sixhub.UUCP>
Date: 26 Dec 90 02:01:26 GMT
References: <33791527@bfmny0.BFM.COM> <2812@cirrusl.UUCP> <350@metran.UUCP>
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Organization: *IX Public Access UNIX, Schenectady NY
Lines: 21


  Let me ask a question here, based on something I partially remember
from setting up ISC some months ago... There was a table which defined
memory, and we used it to define memory which could not do DMA, to force
the o/s to fake it. I *thought* I read in the description of that table
that it could also be used to block out a section of RAM to keep the o/s
from using it, but to still use RAM *above* the reserved space.

  The docs are miles away, and I'm on vacation to boot. If someone can
come up with the details they may be germane to this discussion. I
thought the purpose of that capability was to allow blocks of reserved
memory for memory mapped i/o such as ethernet cards, etc.

  Note: we got this from Dell, some of it said ISC and some Dell. We
found certain other things about the implementation which didn't fit our
needs, so Ionly worked with it for a few weeks.
-- 
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
    sysop *IX BBS and Public Access UNIX
    moderator of comp.binaries.ibm.pc and 80386 mailing list
"Stupidity, like virtue, is its own reward" -me