On 11/6/07, Paul Brook <[EMAIL PROTECTED]> wrote: > > > IIUC enabling/disabling boot mode is no different to and other VM change. > > > If the virtual->physical mapping happens to be the same then it's > > > perfectly ok to reuse the TB. > > > > Not in this case: in boot mode, physical and virtual address 0 > > generates TBs from PROM code. > > How is this different to using the MMU to map the PROM at virtual address > zero?
In that case, the virtual address is zero, but physical address is 0xff0000000. Oh, now I see my error, it is the same in the boot mode case too! Sorry about the noise. > I see exactly one use of MMU_BM. It simply hard-wires a particular > virtual->physical address mapping. It derives from the Sparc specification, where the PC at reset is zero. I wonder why they didn't put the start of memory somewhere higher instead of this hack. On Sparc64 the reset vector is implementation dependent so it can be directly set to the PROM address.
