can then access the page table entries directly using user data space with
the MOVES instruction. This should resolve the problem on the Duo 2x0
series with hard hangs in this function.
Warning: do not call any function that accesses user data space (FC $1)
from get_pte()!
- Figure out what CPU we have, rather than assuming the Booter knows,
and set cputype variable accordingly.
- Carefully rearrange the order of various MMU/ATC operations so as to
eliminate possible side effects. Also, re-order the initial bootstrap
code to make clear what various sections of this code do.
- Adjust to combined initenv()/genenvvars() (the latter has assimilated
the former).
- Add a function code argument to ptest040().
- Use symbolic constants from assym.h where appropriate (and defined).
- Some style cleanup.
- Combine initenv() and getenvvars().
- Hardwire some PowerBook internal video addresses, from Takashi Hamada.
- When printing out the machine model/CPU, use the new cputype variable
instead of the Booter's PROCESSOR environment variable.
- Use new ptest040() function code argument (though for now, the MMU is
disabled on the 040).
- Revert previous change in get_physical() that seems to have broken
some machines; use an ADD instead of an OR when determining the PA.
- Some (very minor) style cleanup of asm code.
the kernel panics. It may be initialized to 0 with the kernel option
"DDB_ONPANIC=0", and is patchable. It may be changed at run-time
from within the DDB (as a DDB variable) or via the ddb.onpanic sysctl
node.
Export all DDB built-in variables via sysctl.
tls