[RFC 3/3] powerpc: Add DTS file for the Motorola PrPMC2800 platform
stuart.yoder at freescale.com
Thu Apr 5 03:51:13 EST 2007
> > "existing"
> > The value of this property defines the regions of virtual address
> > space managed by the MMU in whose package this property is defined
> > without regard to whether or not these regions are currently in use.
> > The encodings of virt and len are MMU-specific.
> > Have a look at the PowerPC binding to find out about that specific
> > encoding.
the PowerPC binding defines this--
+ 5.1.7. Memory Management Unit properties
+ To aid a client in taking over the translation mechanism and
+ still interact with Open Firmware (via the client interface),
+ the client needs to know what translations have been established by
+ Open Firmware. The following standard property shall exist within
+ the package to which the mmu property of the /chosen package refers.
+ This property, consisting of sets of translations, defines the
+ currently active translations that have been established by Open
+ Firmware (e.g., using map). Each set has the following format:
+ (virt size phys mode )
+ Each value is encoded as with encode-int.
The "mode" field seems to be undefined.
So would firmware need to define all phys to virt mappings in
the "translations" property or just the interesting ones-- i.e
uart/console and i2c?
More information about the Linuxppc-dev