Power.org unleashes new standard
Keywords:specification ePAPR? standard Power.org? CPU?
Various software components must typically interact to initialize and boot a computer system. For example, boot firmware might perform a low-level system hardware initialization before passing control to the OS, bootloader or hypervisor. Consistent interfaces and conventions facilitate the interactions between these software components. The ePAPR standard provides a complete interface definition, between boot programs and client programs, and defines minimum system requirements to facilitate the development of a wide variety of embedded systems based on Power Architecture CPUs.
The ePAPR standard uses a "device tree" to describe the basic properties or characteristics for physical devices in a system. ePAPR-compliant systems load a device tree into a client program's memory, enabling that program to access system hardware that it might not otherwise have been able to dynamically detect. This abstraction capability shields software and systems engineers from much of the underlying hardware complexity, making it easier, faster and more reliable to port software and to build Power Architecture-based embedded systems. The ePAPR also specifies standard mechanisms for booting systems with multiple CPUs.
Visit Asia Webinars to learn about the latest in technology and get practical design tips.