Motorola Mobility, Inc. v. Apple, Inc.

Filing 218

AFFIDAVIT signed by : Jill Ho. re 217 Response in Opposition to Motion Declaration of Jill Ho in Support of Apple's Opposition (D.E. 217) by Apple, Inc. (Attachments: # 1 Exhibit A, # 2 Exhibit B, # 3 Exhibit C, # 4 Exhibit D, # 5 Exhibit E, # 6 Exhibit F, # 7 Exhibit G, # 8 Exhibit H, # 9 Exhibit I, # 10 Exhibit J, # 11 Exhibit K, # 12 Exhibit L)(Pace, Christopher)

Download PDF
Exhibit I Compaq Computer Corporation Phoenix Technologies Ltd. Intel Corporation Plug and Play BIOS Specification Version 1.0A May 5, 1994 This specification has been made available to the public. You are hereby granted the right to use, implement, reproduce, and distribute this specification with the foregoing rights at no charge. This specification is, and shall remain, the property of Compaq Computer Corporation ("Compaq") Phoenix Technologies LTD ("Phoenix") and Intel corporation ("Intel"). NEITHER COMPAQ, PHOENIX NOR INTEL MAKE ANY REPRESENTATION OR WARRANTY REGARDING THIS SPECIFICATION OR ANY PRODUCT OR ITEM DEVELOPED BASED ON THIS SPECIFICATION. USE OF THIS SPECIFICATION FOR ANY PURPOSE IS AT THE RISK OF THE PERSON OR ENTITY USING IT. COMPAQ, PHOENIX AND INTEL DISCLAIM ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND FREEDOM FROM INFRINGEMENT. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, NEITHER COMPAQ, PHOENIX NOR INTEL MAKE ANY WARRANTY OF ANY KIND THAT ANY ITEM DEVELOPED BASED ON THIS SPECIFICATION, OR ANY PORTION OF IT, WILL NOT INFRINGE ANY COPYRIGHT, PATENT, TRADE SECRET OR OTHER INTELLECTUAL PROPERTY RIGHT OF ANY PERSON OR ENTITY IN ANY COUNTRY. Table Of Contents _______________________________ References ___________________________________________________________________________3 1.0 Overview ________________________________________________________________________3 1.1 Goals of a Plug and Play System BIOS 4 1.2 Enhancements to the current BIOS architecture 5 1.3 Elements of the Plug and Play BIOS architecture 6 Plug and Play BIOS Specification 1.0A 1.3.1 Bi-modal functionality 1.3.2 OS Independence 1.3.3 Expandability 1.4 Installation Structure Page 2 6 6 6 7 2.0 System BIOS Initialization __________________________________________________________7 2.1 System BIOS POST Requirements 7 2.1.1 System Board Storage Requirements 8 2.1.2 System BIOS Resource Management 9 2.1.3 Isolating Committed Resources 9 2.1.4 System BIOS Resource Allocation 9 2.2 Plug and Play ISA Card Support 11 2.2.1 Assigning CSN to Plug and Play ISA cards 11 2.2.2 Initializing Plug and Play ISA Cards 11 2.3 BIOS POST Option ROM Initialization 12 2.4 Transferring Control to the Operating System 13 2.5 POST Execution flow 13 3.0 Option ROM Support _____________________________________________________________16 3.1 Option ROM Header 16 3.2 Expansion Header for Plug and Play 17 3.3 Option ROM Initialization 22 3.4 Option ROM Initialization flow 23 3.5 ISA Option ROMs and Resource Mapping 24 3.6 Error Recovery: Returning to the Boot flow 24 4.0 Configuration Support ____________________________________________________________25 4.1 System Device Configuration List 25 4.2 System Device Node Definition 25 4.3 Plug and Play BIOS Functions 29 4.4 Plug and Play Installation Check 29 4.4.1 System BIOS Plug and Play Compliance - "$PnP" 32 4.5 System Configuration Interface 34 4.5.1 Function 0 - Get Number of System Device Nodes 35 4.5.2 Function 1 - Get System Device Node 36 4.5.3 Function 2 - Set System Device Node 38 4.6 Event Notification Interface 40 4.6.1 Function 3 - Get Event 42 4.6.2 Function 4 - Send Message 43 4.6.3 Function 5 - Get Docking Station Information 47 4.6.4 Function 6 - Reserved 49 4.6.5 Function 7 - Reserved 49 4.6.6 Function 8 - Reserved 49 4.7 Extended Configuration Services 50 4.7.1 Function 9 - Set Statically Allocated Resource Information 51 4.7.2 Function 0Ah - Get Statically Allocated Resource Information 53 4.7.3 Function 40h - Get Plug & Play ISA Configuration Structure 54 4.7.4 Function 41h - Get Extended System Configuration Data (ESCD) Info 56 4.7.5 Function 42h - Read Extended System Configuration Data (ESCD) 56 4.7.6 Function 43h - Write Extended System Configuration Data (ESCD) 57 4.8 Power Management Services 58 4.8.1 Function 0Bh - Get APM ID Table 58 Plug and Play BIOS Specification 1.0A Page 3 Appendix A: Generic Option ROM Headers _____________________________________________61 Appendix B: Device Driver Initialization Model___________________________________________62 Appendix C: Return Codes____________________________________________________________64 Plug and Play BIOS Specification 1.0A Page 4 References _____________________________________ Plug and Play ISA Specification Version 1.0A May 5, 1994 Send email to plugplay@microsoft.com to obtain a copy. EISA Specification Version 3.12 Contact BCPR Services Inc to obtain a copy. Extended System Configuration Data Specification Version 1.02a Contact Intel Corporation to obtain a copy. Device Identifier Reference Table & Device Type Code Table Browse the PlugPlay forum on CompuServe to obtain a copy. 1.0 Overview ___________________________________ This Plug and Play BIOS Specification defines new functionality to be provided in a PC compatible system BIOS to fulfill the goals of Plug and Play. To achieve these goals, several new components have been added to the System BIOS. Two key areas that are addressed by the System BIOS are resource management and runtime configuration. Resource management provides the ability to manage the fundamental system resources which include DMA, Interrupt Request Lines (IRQs), I/O and Memory addresses. These resources, termed system resources, are in high demand and commonly are over-allocated or allocated in a conflicting manner in ISA systems, leading to bootstrap and system configuration failures. A plug and play system BIOS will play a vital role in helping to manage these resources and ensure a successful launch of the operating system. In its role as resource manager, a Plug and Play BIOS takes on the responsibility for configuring Plug and Play cards, as well as systemboard devices during the power-up phase. After the POST process is complete, control of the Plug and Play device configuration passes from the system BIOS to the system software. The BIOS does, however, provide configuration services for systemboard devices even after the POST process is complete. These services are known as Runtime Services. Runtime configuration is a concept that has not previously existed in a System BIOS before. The system BIOS has not previously provided the ability to dynamically change the resources allocated to systemboard devices after the operating system has been loaded. The Plug and Play BIOS Specification provides a mechanism whereby a Plug and Play operating system may perform this resource allocation dynamically at runtime. The operating system may directly manipulate the configuration of devices which have traditionally been considered static via a System BIOS device node structure. In addition, a Plug and Play System BIOS may also support event management. By means of the interfaces outlined in this document, the System BIOS may communicate the insertion and removal of newly installed devices which have been added to the system at runtime. The event management support defined by this specification are specific to devices controlled by the system BIOS, such as docking a notebook system to, or undocking it from, an expansion base. This event management does not encompass the insertion and removal of devices on the various expansion busses. This document describes the BIOS support necessary for both systemboards and add-in boards with Option ROMs. 1.1 Goals of a Plug and Play System BIOS Considering the scope of Plug and Play, the following are the goals of the Plug and Play BIOS Specification. Maximize ISA compatibility Plug and Play BIOS Specification 1.0A Page 5 This is the key consideration in a system BIOS. It is considered unacceptable to change the architecture of a System BIOS to prevent the thousands of ISA cards and software programs that rely on the system BIOS for services. Eliminate resource conflicts during the POST procedure A common problem that plagues many ISA systems today is the fact that there are a lot more devices available than there are system resources. In this environment, devices are bound to have conflicting resources. The system BIOS will now play a key role to help prevent these resource conflicts by not enabling devices which conflict with the primary boot devices, and relocating boot devices, if necessary, to allow a successful load of the operating system. It is the role of the operating system to provide support for communicating irreconcilable resource conflicts to the user. Support Plug and Play ISA cards A Plug and Play system BIOS is responsible for the isolation, enumeration, and optional configuration of Plug and Play ISA cards. These cards, which provide information on their resource requirements and permit software to configure those resources, will allow the system BIOS to arrive at a conflict free configuration necessary to load the operating system. Allow dynamic configuration of systemboard devices Systemboard devices have traditionally been treated as having somewhat static configurations. It is a goal of the Plug and Play BIOS specification to provide a standard mechanism whereby systemboard devices may be configured dynamically by system software. This will grant configuration management software a great deal of flexibility when system resources are in demand and alternate configurations are necessary. Note: Dynamic device configuration requires explicit device driver support. Provide system event notification The system BIOS is capable of detecting certain hardware events that could affect the system configuration. By providing an event notification mechanism, an operating system can recognize the event and process any necessary configuration changes.

Disclaimer: Justia Dockets & Filings provides public litigation records from the federal appellate and district courts. These filings and docket sheets should not be considered findings of fact or liability, nor do they necessarily reflect the view of Justia.


Why Is My Information Online?