Slimline Open Firmware
Upcoming SlideShare
Loading in...5
×
 

Slimline Open Firmware

on

  • 2,437 views

 

Statistics

Views

Total Views
2,437
Views on SlideShare
2,433
Embed Views
4

Actions

Likes
0
Downloads
22
Comments
0

2 Embeds 4

http://www.slideshare.net 3
http://www.lmodules.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 1. Description Low-Level FW: basic platform specific initialization code, memory initialization, … 2. Open Firmware is no official IEEE Standard, but rather a proposal which is a de-facto standard

Slimline Open Firmware Slimline Open Firmware Presentation Transcript

  • LAB: Slimline Open Firmware Power Architecture Developer Conference ‘07 Open Systems Design and Development 2007-09-24 | Heiko J Schick <schickhj@de.ibm.com>, Hartmut Penner <hpenner@de.ibm.com>, Otto Wohlmuth <wohlmuth@de.ibm.com> © 2007 IBM Corporation
  • Who we are … Heiko J Schick SLOF Developer Open Systems Firmware Development Hartmut Penner SLOF Architect Open Systems Firmware Development Dr. Otto Wohlmuth SLOF Godfather ;-)
  • Agenda
    • Open Firmware: De-Facto Industry Standard
    • Overview of Existing Firmware Implementations
    • SLOF Overview and Design Principles
    • SLOF Assets and Platform Support
    • SLOF Deep Dive
    • Outlook
    View slide
  • Open Firmware: De-Fact Industry Standard
    • Loaded and initiated by Low Level Firmware
    • IEEE 1275 implementation
      • Client Interface
        • Interface to the OS
      • Device Interface
        • Creation of device tree
        • Initialization of IO devices
        • Boot loader
      • User Interface
        • Debug Interface ( UART )
        • NVRAM manipulation
    View slide
  • O Overview of Existing Firmware Implementations
  • LinuxBIOS 1 Hardware LinuxBIOS Linux Distribution Linux Distribution Operating System (e.g. Windows, Unix, Linux, OpenSolaris) Operating System (e.g. Windows CE, OpenSolaris, Linux) Linux Kernel ELF Loader Linux Kernel Linux Kernel ELF Loader kexec ELF Loader ELF Loader T T T Transient O Optional Boot Manager or Open Firmware Bochs BIOS ADLO Bootstrap / Startup Code Boot Manager O
  • LinuxBIOS
    • Source Code under GPL
    • RAM controller and memory setup
    • PCI and HyperTransport scan / setup and device enumeration
    • ELF Loader
    • Uses a device tree similar data structure
    • Plans for version 3:
      • modular design
      • easier build process
      • flattened device tree support
      • ePAPR compliant
    2
  • OpenBIOS
    • Original project scope was to develop an open source Open Firmware implementation.
    • Project scope changed from writing a free firmware implementation to present most of the available free and open source Open Firmware implementation (“Umbrella Project”).
  • FirmWorks
    • FirmWorks Open Firmware is a mature, stable, complete Open Firmware implementation that is based on the de-fact IEEE 1275-1994 standard
    • Source Code under BSD/MIT (commercial licensing available)
    • Complete Open Firmware
    • Extensive debugging support - source and assembly language level
    • Minimal dependencies on external toolchains
    • Integrated builder, packager, tokenizer
    1
  • FirmWorks
    • Filesystem support
      • FAT (R/W), ext2 (R/W), ext3 (RO), ISO9660 (RO), JFFS2 (RO)
    • Network support
      • TFTP, TCP/IP, DHCP, DNS, HTTP (client and server), telnet (client and server), IPV6, NFS
    • USB
      • OHCI, UHCI, EHCI (USB 2.0), Mass storage - e.g. FLASH keys, Keyboards, Serial ports, Network interfaces, Hubs
    • Drivers for many common programming interfaces
    • Graphical Boot and Administration Menu
    • Support for System Diagnostics
    • Support for system admin tasks like installation
    2
  • Open Hack’Ware
    • Open Hack’Ware is a free Open Firmware emulator intended to be used on PPC machines
    • Source Code under GPL
    • It is not a real Open Firmware as it knows nothing about Forth
    • Emulates the Open Firmware and RTA interface
    • Emulates some known “interpret” strings to make it able to launch known operating systems
    • Currently used as the Qemu-PPC firmware
  • Extensible Firmware Interface (EFI)
    • Industry interface specification for x86 and IA64 systems
    • Interface for an operating system to interact with firmware attributes
    • Specified in one location (the UEFI Specification)
      • Testable
      • Current
      • Portable
      • Extensible and Flexible
    • Tiano Core
    • Source Code under GPL
  • AMD Generic Encapsulated Software Architecture (AGESA)
    • A Wrapper is the translator between the AMD interface and the Host BIOS interface
    • AGESA code focuses on AMD specific technology
    • Each AMD block has its own wrapper and must call out through its wrapper to acquire services
  • S Slimline Open Firmware
  • What is SLOF ?!?
    • SLOF |släp| noun Computing, Firmware is initialization and boot source code based on the IEEE-1275 standard (also known as the Open Firmware standard).
  • SLOF Overview
    • Initialization and Boot Firmware for Cell Broadband Engine™ (Cell/B.E.) and PowerPC
    • Complete Open Firmware implementation which is based on the de-fact IEEE 1275-1994 standard
    • Source code unter BSD like license
    • Small size and footprint
    • Simplicity and Modularity (easy to use and extend)
    • Boot time optimized
    • Focus on minimal time to market
    1
  • SLOF Overview
    • Minimal dependencies on external toolchains
    • Filesystem support
      • FAT (RO), ext2 (RO), ISO9660 (RO), ROMFS
    • Network support
      • TFTP, DHCP, BOOTP
    • USB
      • OHCI, Mass storage – e.g. CDROM and Flash drivers, Keyboards, Hubs
    • IPMI Keyboard Controller Style Interface (KCS) support
    • Display device support via x86 emulator and FCode evaluator
    • Graphical Boot and Administration Menu
    2
  • Modular Firmware Design Operating System Optional Virtualization Optional Runtime Abstraction Services Optional Secondary Boot Loader Slimline Open Firmware Low-level Firmware Operating System Optional Virtualization Optional Runtime Abstraction Services BOOT-TIME RUN-TIME Firmware Transient Firmware
  • Low-level Firmware
    • Characteristics
    • Chip & Board Initialization
      • Hardware dependent
      • Support JS2x and Cell/B.E. workstation
    • Support of Flash Filesystem
      • 1st stage execution from ROM
      • 2nd stage execution from memory
    • Interface to Open Firmware (SLOF)
      • Loads Open Firmware into memory
      • Transfer of hardware information (e.g. memory size)
    Operating System Optional Virtualization Optional Runtime Abstraction Services Optional Secondary Boot Loader Slimline Open Firmware Low-level Firmware
  • Slimline Open Firmware
    • Characteristics
    • De-facto industry standard for PowerPC and Cell/B.E.
      • IEEE Std. 1275-1994: Standard for Boot (Initialization Configuration) Firmware
      • Platform Independent
    • Fast Firmware and Operating System Bring-Up
      • Short boot-time
      • Small footprint
    • Fast Prototyping
      • Interactive user interface
    • Open Interface
      • Extendable & adaptable
    Operating System Optional Virtualization Optional Runtime Abstraction Services Optional Secondary Boot Loader Slimline Open Firmware Low-level Firmware
  • Secondary Boot Loader
    • Characteristics
    • Standard Interface
      • Uses Open Firmware client interface
    • SLOF internal secondary boot loader
      • C runtime
      • Device driver infrastructure (modules)
      • Easy device driver adaption
    • Open Source
      • Yaboot
      • GRUB 2
    Operating System Optional Virtualization Optional Runtime Abstraction Services Optional Secondary Boot Loader Slimline Open Firmware Low-level Firmware
  • Runtime Abstraction Services
    • Characteristics
    • Standard Interface
      • RTAS ABI from OpenPPR
      • Standard interface to none standard devices
    • Hardware Abstraction
      • Reduces operating systems adaption
    • Supported Calls
      • PCI Configuration Cycles
      • Reboot, power-off
      • RTC access
      • Firmware flash update
    Operating System Optional Virtualization Optional Runtime Abstraction Services Optional Secondary Boot Loader Slimline Open Firmware Low-level Firmware
  • SLOF Platform Support
    • QS2x (Cell/B.E. based blade servers)
    • CAB (Cell/B.E. Accelerator Board)
    • JULI Cluster
      • Firmware for an IBM JS21 cluster.
      • Used to exploit PCI Exress and MSIs.
      • Native Linux (no Hypervisor).
    • XEN on PowerPC
    • SLOF Open Source (IBM JS20)
    • Bimini (Power.org 970MP Reference Design and Workstation)   
    Cell Accelerator Board IBM Cell Processor Based Blade QS20 IBM BladeServer JS21
  • S SLOF Deep Dive
  • SLOF Code Structure Low Level Firmware Layer CPU Init Mem Init I/O MMU I/O Sub Open Firmware Layer Slimline Open Firmware Forth Engine Client Interface RTAS Framework Loader Framework JS21Specific RTAS Service Nano Kernel JS21 Boot Drivers Boot Protocol Stacks Device Interface User Interface JS20 Specific Code & Device Tree JS21 Specific PPC64 Platform Common Operating System JS20 Specific RTAS JS20 Boot Drivers JS21 Specific Forth Code & Device Tree Mem Init I/O MMU I/O Sub JS20 Specific Boot Devices Board SB/H8 Board Southbridge Southbridge Memory
  • SLOF Filesystem Structure
    • Modules organized in File System
      • Load based on name
        • Replacement of module possible
        • Addition of modules possible
    • Customization of FW
      • Later Addition to base FW
        • Open source hypervisor
        • Operation system
        • Device code for specific devices
  • PCI Probe Infrastructure
    • PCI probe code is responsible to setup all devices on PCI bus
      • Configuration space (BAR registers, interrupt number)
      • Create Open Firmware device tree nodes with all
    • The interface can be found in the following files:
    Filename Interface Name Purpose pci-aliases.fs pci-alias Generate aliases for generic device pci-interrupt.fs pci-get-irq-line Calculate IRQ for device pci-get-irq-sense Calculate IRQ sense for device pci-device_<vendorid>_<devid>.fs Provide device specific code (if generic setup is not sufficient) pci-class_<class>.fs Provide class specific setup (if generic setup is not sufficient) pci-bridge_<vendorid>_<devid>.fs Provide bridge specific setup (if generic setup is not sufficient)
  • Display Device Support
    • The following options are supported to initialize graphic cards within SLOF:
      • FCode which is stored in the expansion ROM of the device and executed in the FCode evaluator.
      • VESA BIOS Extension 2.0 which is stored in the expansion ROM of the device and executed via a x86 emulator.
      • Manually via device or class code specific PCI setup files.
    Tested Graphic Adapter Type of Initialization XGI Volari XP 10 x86 Emulation NVIDIA 7x00XX x86 Emulation NVIDIA 6600 GE FCode evaluation ATI Technologies Inc. ES1000 Manually via device specific file
  • SLOF Environment Loader Framework / Service Nano Kernel RTAS Low Level Firmware System Hardware Hypervisor (optional) PPC64 Linux arch tree BPA Linux arch tree glibc GCC PPC64 backend BPA backend libraries applications platform ecosystem SLOF RTAS Linux Device Drivers User Kernel Firmware
  • SLOF Structure S L O F lim- ine pen irmware
  • Open Firmware Client Interface
    • Allows client programs to access Open Firmware services
    • Clients loaded by Open Firmware
      • Operating system
      • Boot loader
    • IEEE 1275 centric interface
      • Device tree traversal
      • Memory handling
      • Console I / 0
    • Call by name
    • Callbacks possible
    • Boot Time
  • Runtime Abstraction Services
    • Encapsulation of HW specifics into machine-independent interface
      • Start and stop Threads in SMP configuration
      • Display Status indicators
      • System Shutdown
      • PCI config cycles
      • Serial I/O
    • Instantiated and relocated by User
    • Users must allocate Memory
    • Call by name
    • Unidirectional
    • Runtime
  • Service Nano Kernel
    • Client application which can be called before the operating system is invoked
    • Framework is written in C to contain more complex applications
    • Can be used for platform tests and experiments
    • Contains OFW client interface and RTAS access methods
    • For SLOF it is only used to implement DHCP, TFTP, and ARP
    1
  • Service Nano Kernel
    • Usage of other license device drivers from within SNK client
      • Network boot
      • DHCP / TFTP / ARB
    • Classical module interface
      • Entry point at beginning of each module
      • Exchange of function pointer tables
    • No inter-linkage
    • C ABI
    • Call by value
    • Bidirectional
    • Boot time
    2
  • O Outlook
  • Outlook
    • Integration of x86 BIOS emulator for graphic card support
    • ePAPR compliant firmware stack using SLOF assets
    • More platforms …
  •