Open Firmware Working Group Home Page.
Open Firmware developers should periodically check here for recommended practice documents. These documents are authorized by the Open Firmware Working Group and extend, clarify and/or modify previously published specifications.
Some accepted proposals may have been accepted as recommended practice, but have not yet been written as a recommended practice document. You may want to check for accepted proposals in the proposal index or in the proposals section of this document.
For recommended practice developers, there's also a template available for writing your recomended practice document.
This page, playground:/pub/1275/practice/index.html, was last updated on Mon Jan 6 17:15:40 PST 1997 and is maintained by David Kahn, dmk-xxx@Eng.Sun.Com. (Remove '-xxx' to use email address.)
Table of Contents.
Recommended Practice Template Document.
This recommended practice extends the terminal emulator package and adds new optional features to display device drivers to provide 16 color text extensions to client programs. This document creates new FCodes, which must be supported in firmware implementations which comply with this recommended practice.
This recommended practice creates new methods for supporting simple graphics in display device drivers, (i.e. draw-rectangle). These extensions are typically used by ease-of-use installation and booting software, but may also be used by the CPU firmware to present an easy-to-use interface for the selection and display of devices.
This recommended practice, authorized by working group proposal #272, creates a standard technique which allows file system services to be layered (interposed) on top of unmodified FCode device drivers. The recomended practice creates a new FCode and a new client interface service.
Generic Names, authorized by working group proposal #251, allows device nodes to contain human readable, generic names.
Device Support Extensions describes the application of Open Firmware to various common devices, such as keyboard, pointing devices, real time clocks, etc.
TFTP Booting Extensions, Version 1.0, August 29, 1998, is an approved, recomended practice document, describing extensions to the core defined obp-tftp package and "network" device types to add additional capabilities to network device booting, including the bootp protocol.
Interrupt Mapping, Draft Version 0.9, July 12, 1996 is a draft, unapproved, recomended practice document, describing methods to define the interrupt topology of a system within the Open Firmware Device Tree.
Open Firmware Recommended Practice: SCSI-3 Parallel Bus, Version 1.0, December 23, 1996, authorized by working group proposal #375, defines the application of Open Firmware to the SCSI-3 Parallel Bus.
Working group proposal 215, formalizes the client interface as a vocabulary and allows the client interface to be arbitrariliy extended.
Working group proposal 245, is a specific extension that deals with some assumptions NT makes about fonts and char heights.
Working group proposal 248, creates a standard method, size, that returns the size of the device. It applies to all packages for which size information is relevant. The proposal also creates the #blocks standard method, which applies to all devices of type byte and block.
Working group proposal 268, creates a standard property, version, that defines the contents of a device, versus the device itself. For example, it might describe the current version of the contents of a flash prom device.
Working group proposal 270, adds test-method to the generic client interface package. This client interface allows a client program to determine if an arbitrary method exists in a package.
Working group proposal 288 creates the wide and differential properties for scsi host adaptors.
Working group proposal 410 creates the dma-ranges standard property which describes the DMA structure of a device.
Table of Contents.
Open Firmware Working Group Home Page.