Subject: Followup on discontiguous ram
To: None <port-mvme68k@NetBSD.ORG>
From: Steve Woodford <steve@mctavish.demon.co.uk>
List: port-mvme68k
Date: 11/16/1996 17:19:58
Following on from my last message about getting VMEbus RAM cards to work
with D32 addresses... I'm prepared to have a go at implementing this,
having read some useful stuff in the current-users list (thanks Jason!).

Some of the low-level stuff to poke around in NVRAM for offboard RAM
start and end addresses is going to have to be wrapped in #ifdef MVME147
since I can't code for anything else. Shame we don't have a board
independent nvram driver yet <sigh>. Yet more crockery in locore.s before
VM is switched on...

Also, since I'm going to rely on the contents of NVRAM locations
0xfffe0764 -> 0xfffe076b for this, it's only fair to mandate that offboard
RAM is contiguous accross multiple boards. This shouldn't be a problem
with ~3Gb A32/D32 space on the '147 ;-) I suppose I could code the new
routines in pmap.c to handle more than a couple of non-contiguous physical
memory spaces though, just in case...

Cheers, Steve

Steve Woodford: steve@mctavish.demon.co.uk             NetBSD-1.2/mvme68k
Small fast computers breed fat slow programmers.        Motorola MVME147S
                  ...This is a Microsoft free zone...