Date: Tue, 17 Dec 1996 11:41:08 +1030 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: jonny@mailhost.coppe.ufrj.br (Joao Carlos Mendes Luis) Cc: tony@dell.com, terry@lambert.org, eivind@dimaga.com, hackers@FreeBSD.ORG Subject: Re: Boot loader hacks was: Re: MAXMEM Message-ID: <199612170111.LAA23769@genesis.atrad.adelaide.edu.au> In-Reply-To: <199612161833.QAA25314@gaia.coppe.ufrj.br> from Joao Carlos Mendes Luis at "Dec 16, 96 04:33:55 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Joao Carlos Mendes Luis stands accused of saying: > Just a stupid question: Why does the boot loader should know if > there's more than 64M or not on the system ? Because many of the memory-detecting interfaces require real-mode calls, and the kernel has no means of performing these. > Why couldn't it simply detect 64M at most, and let the kernel > find the rest by itself ? Anyway, is what's done with the > MAXMEM option, isn't it ? > > Moreover: Is there any STRONG reason to ask the BIOS for the > memory amount ? Couldn't it search for the memory ? You can't safely "search" for memory. Systems with parity/ECC will usually NMI you if you hit a region with no memory in it, but a number of systems will just spontaneously reboot. Others will 'mirror' memory from lower locations, requiring you to write into the memory as you perform your search. Only this can disturb memory-mapped peripherals, and so it goes on. Because the BIOS has intimate knowledge of the board and chipset, it's the only authority on the subject. > Joao Carlos Mendes Luis jonny@gta.ufrj.br -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612170111.LAA23769>