Case 6:21-cv-00735-ADA Document 32-12 Filed 01/27/22 Page 1 of 7
`
`Exhibit 9
`
`

`

`Case 6:21-cv-00735-ADA Document 32-12 Filed 01/27/22 Page 2 of 7
`
`Digital Edition
`
`Digital Editions of selected Intel Press books are in
`addition to and complement the printed books.
`
`Beyond BIOS:
`Developing with the Unified
`Extensible Firmware Interface
`2nd Edition
`Vincent Zimmer, Michael Rothman and Suresh Marisetty
`
`Intel
`PRESS
`
`Books by Engineers, tor Engineers
`
`Click the icon to access information on other essential
`books for Developers and IT Professionals
`
`Visit our website at www.intel.com/intelpress
`
`

`

`Case 6:21-cv-00735-ADA Document 32-12 Filed 01/27/22 Page 3 of 7
`
`Beyond BIOS
`
`Developing with the Unified Extensible
`Firmware Interface
`
`Second Edition
`
`Vincent Zimmer
`Michael Rothman
`Suresh Marisetty
`
`Intel
`PRESS
`
`

`

`Case 6:21-cv-00735-ADA Document 32-12 Filed 01/27/22 Page 4 of 7
`
`Copyright © 2010 Intel Corporation. All rights rese1ved.
`ISBN 13 978-1-934053-29-4
`
`This publication is designed to provide accurate and authoritative information in regard to the
`subject matter covered. It is sold with the understanding that the publisher is not engaged in
`professional se1vices. If professional advice or other e.."pe1t assistance is required, the services
`of a competent professional person should be sought.
`
`Intel Co1poration may have patents or pending patent applications, trademarks, copyrights, or other
`intellectual property rights that relate to the presented subject matter. TI1e furnishing of documents and
`other materials and information does not provide any license, express or implied, by estoppel or
`otheiwise, to any such patents, trademarks, copyrights, or other intellectual property rights.
`
`Intel may make changes to specifications, product descriptions, and plans at any time, without notice.
`
`Fictitious names of companies, products, people, characters, and/ or data mentioned herein are not
`intended to represent any real individual, company, product, or event.
`
`Intel products are not intended for use in medical, life saving, life sustaining, critical control or safety
`systems, or in nuclear facility applications.
`
`Intel, the Intel logo, Celeron, Intel Centrino, Intel NetBurst, Intel Xeon, Itanium, Pentium, l\1:MX, and
`VTune are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United
`States and other countries.
`
`t Other names and brands may be claimed as the property of others.
`
`Tius book is printed on acid-free paper. (§)
`
`Publisher: Richard Bowles
`Editor: D avid J. Clark
`Program Manager: Stuait Douglas
`T ext D esign & Composition: InfoPros
`Graphic Alt Ted Cyrek (cover) InfoPros (illustrations)
`
`LJ'brary of Congress Cataloging in Publication Data:
`
`10 9 8 7 6 5 4 3 2 1
`First printing, November 2010
`
`

`

`Case 6:21-cv-00735-ADA Document 32-12 Filed 01/27/22 Page 5 of 7
`
`Foreword to the First Edition (cid:127) xi
`
`Foreword to the
`First Edition
`
`Beyond BIOS. Those two words began to circulate through the elite firmware
`architects and developers in the industry standard computing circle around
`1998, when Intel, Microsoft, HP and a number of other companies began to
`lay out the plan for bringing up the first Intel'" ltanium'" systems. The plan was
`originally called IBI, the Intel Boot Initiative. Mainstream PCs had been using
`BIOS ever since the beginning of the IBM PC. Its drawbacks and limitations
`were magnified in the "big iron" machines based on the ltanium processors.
`For example, BIOS depends on many of the PC-AT hardware such as the 8254
`timer and 8259 interrupt controller, which were not designed to scale to larger
`servers like the HP Integrity Superdomet servers. Worse, BIOS assumes a 1MB
`execution memory limit and has very limited memory space to execute the
`Option ROMs on the add-in cards. BIOS' 16-bit nature stifles the platform
`advancement for Itanium systems that are 64-bit based.
`There have been non-BIOS solutions in the more proprietary vertical
`integrated systems design, such as Open Firmware used by IBM Powert, SUN
`SPARCt, and Apple PowerPCt; ARCSt by DEC Alpha, and PDC/IODCt by
`HP PA-RISC. Open Firmware is Forth-based, it is difficult to find the talent,
`and its specifications have not kept up with the evolution of the technology.
`ARCS lacks the driver model to support add-in cards. With BIOS hitting the
`wall and no clear alternative that can be brought into the industry standard
`arena, Intel spearheaded the IBI, which at this stage is named Extensible
`Firmware Interface (EFI), to reflect objective of the effort. EFI brought
`the modern computer software architectural concepts into firmware. EFI
`enables firmware development in high-level languages like C, provides proper
`
`

`

`Case 6:21-cv-00735-ADA Document 32-12 Filed 01/27/22 Page 6 of 7
`
`xii (cid:127) Beyond BIOS: Developing with the Unified Extensible Firmware Interface
`
`abstraction of hardware, and enables extensibility through the GUID concept.
`The benefits of EFI were so convincing that Microsoft and the industry made
`it the only boot mechanism for the Itanium-based systems.
`Now that the IA-32 processors are also extended to 64-bit via Intel® 64, the
`industry is working on Unified EFI (UEFI) as the standard pre-boot firmware
`infrastructure going forward. Intel also spearheaded the effort on the Intel
`Platform Innovation Framework for EFI (Framework). The Framework is
`Intel's implementation of EFI, and it is also the starting point for the industry
`to define the Platform Initialization (PI) specifications that establish the
`firmware internal interface architecture as well as firmware-to-silicon interfaces
`that enable silicon driver modularity and interoperability. With Framework's
`implementation of UEFI and PI, Intel has completed the task of replacing
`BIOS, thus enabling the industry to move beyond BIOS.
`This book is a landmark in the development of the UEFI and PI firmware.
`It couples a powerful, modern firmware infrastructure with a unique look
`into the mind of a few UEFI/PI architects who have made the Framework
`implementation into reality and as a reference. It's accessible to the student
`in firmware development, yet conveys a deep technical understanding of the
`UEFI/PI architecture and the Framework implementation. It covers all major
`areas of the Framework implementation that the firmware developers need to
`understand. Using this book along with the EFI Development Kit (EDK) code
`on the TianoCore.org open source project would be an excellent tutorial for
`the firmware engineers to move beyond BIOS.
`Vincent Zimmer has been running the PI Working Group meetings and
`Michael Rothman has been running the UEFI Specification Working Group
`meetings, helping the Chair of both groups, Mark Doran. Vincent has also
`been very involved in the Trusted Computing Group, defining security related
`extensions for EFL Michael Rothman and Robert Hale are also the lead forces
`in the development of the Human Interface Infrastructure coming up in the
`next generation of the UEFI Specification. These authors are some of the elite
`EFI architects who have helped bring the dream of moving beyond BIOS into
`reality, thus among the best possible teachers of this subject matter.
`This book is for you if you'd like to understand the UEFI/PI architecture and
`the Framework implementation; that is, to understand how to move beyond
`BIOS. It gives you all the technical background to understand Bill Gates'
`WINHEC 2006 Keynote Speech when he said: "There are changes across the
`board, in terms of how hardware and software work together. If we think about
`
`

`

`Case 6:21-cv-00735-ADA Document 32-12 Filed 01/27/22 Page 7 of 7
`
`Foreword to the First Edition (cid:127) xiii
`
`boot, we're finally moving away from the old BIOS to this unified extensible
`firmware interface, and that gives us new flexibility and capability, and it's
`got a rich API set to build on, so many of you are working with us on that."
`For any student in this field, this book provides an important bridge between
`normative specifications and the informative details of the development.
`Today, Itanium-based systems are no longer the only machines supporting
`EFL All the Imel® -based Apple Mact systems are supporting EFL Systems
`based on Intel® 64 IA-32 processors are also in the process of supporting
`UEFL Embedded systems are also making use of the UEFI/PI architecture in
`its specialized environment. Operating systems, such as Windows t, Linux t,
`HP-UXt, Open VMS, FreeBSD, and so on are already £FI-based on Itanium(cid:173)
`based systems. Windows, Linux and OS-Xt are in the process of supporting
`UEFI on Intel® 64 IA-32 processor-based systems. Currently OS-X already
`supports EFI on the IA-32 processor-based Mac systems.
`This book is the first to describe in detail the Framework implementation
`of UEFI and PI architecture. I am very pleased to recommend this new must(cid:173)
`read to you who may have been living in the BIOS world for so long to see the
`life beyond BIOS as envisioned by Bill Gates. I also recommend that readers
`take full advantage of the open source TianoCore.org. Sample code is worth a
`thousand words. The EDK is a great companion for the book.
`Dong Wei
`Vice President and Chief Executive, the Unified Forum
`HP Distinguished Technologist
`Granite Bay, California
`June 18, 2006
`
`