anchor.diff:  not be used for general memory allocations. It is used to protect vital
   data structures from being overwritten by the client program. For
   example, on some systems with an IOMMU, the TCE (translation control
  -entry) tables initialized by an ePAPR boot program would need to be
  +entry) tables initialized by an {spec} boot program would need to be
   protected in this manner. Likewise, any boot program code or data used
   during the client program's runtime would need to be reserved (e.g.,
  -RTAS on Open Firmware platforms). The ePAPR does not require the boot
  +RTAS on Open Firmware platforms). The {spec} does not require the boot
   program to provide any such runtime components, but it does not prohibit
   implementations from doing so as an extension.
   
  
positive.code: 
  == The Device Tree
  === Overview
  The ePAPR specifies a construct called a _device tree_ to describe
  system hardware. A boot program loads a device tree into a client
  program's memory and passes a pointer to the device tree to the client.
  
  This chapter describes the logical structure of the device tree and
  specifies a base set of properties for use in describing device nodes.
  Chapter 3 specifies certain device nodes required by an ePAPRcompliant
  device tree. Chapter 6 describes the ePAPR defined device bindings— the
  requirements for representing certain device types classes of devices.
  Chapter 8 describes the in-memory encoding of the device tree.
  
  
negative.code: the client program to have hard-coded descriptions of system hardware.
  
  ==== 32-bit and 64-bit Support
  The {spec} supports CPUs with both 32-bit and 64-bit addressing
  capabilities. Where applicable, sections of the {spec} describe any
  requirements or considerations for 32-bit and 64-bit addressing.
  
  === References
  