Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
Agnostic Device Drivers
1. Agnostic Device Drivers ( ADD ) Concept, Design, and Implementation of a Slimline Boot Firmware for Linux on Power Architecture IBM Deutschland Entwicklung GmbH Schoenaicherstr. 220 71032 Boeblingen
To replace the title / subtitle with your own: Click on the title block -> select all the text by pressing Ctrl+A -> press Delete key -> type your own text
Device-Tree: The set of devices attached to the system, including permanently installed devices and plug-in devices, is described by an Open Firmware data structure known as device tree.
RPA: - implements a Hypervisor - can run several Operating Systems - implements RTAS Apple: - doesn’t implement RTAS and a Hypervisor - has Platform Expert (Hardware and Operating System “Platform Expert” Code, which is copied from the firmware to the kernel of the Operating System, where it is executed)
Agnostic Device Drivers (ADD) Concept and Basics (1): During the boot phases of the operating system, the Device-Tree (including ADD Byte-Code) is fetched over the client interface of Open Firmware. Device-Tree, with the Byte-Code included, is stored by the operating system and is available after lifetime of Open Firmware. (2): ADD Interpreter loads Byte-Code from the stored Device-Tree. (3): ADD Interpreter executes Byte-Code asynchronous.
Control Structures: - Finite loop incrementing by 1 - Finite loop incrementing by <n> - Indefinite loop terminating when <f> is 'true‘ - Indefinite loop terminating when <f> is 'false‘ - Infinite loop - Two-branch conditional Defining Words: - Variables - Constants - Colon Definitions (Sub-Routines)
![Contents ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)