An I/O System on a Chip

Total Page:16

File Type:pdf, Size:1020Kb

An I/O System on a Chip An I/O System on a Chip The heart of the I/O subsystem for the HP 9000 Model 712 workstation is a custom VLSI chip that is optimized to minimize the manufacturing cost of the system while maintaining functional compatibility and comparable performance with existing members of the Series 700 family. by Thomas V. Spencer, Frank J. Lettang, Curtis R. McAllister, Anthony L. Riccio, Joseph F. Orth, and Brian K. Arnold The HP 9000 Model 712 design is based on threeOther custom I/O functionality that is completely implemented on pieces of VLSI that provide much of the system'sLASI functionalĆ with HP internal designs includes: RSĆ232, Centronics ity: CPU, graphics, and I/O. These chips communicateparallel via interface, a a batteryĆbacked realĆtime clock, and two highĆperformance local bus referred to as GSC (generalPS/2Ćstyle sysĆ keyboard and mouse ports. In addition, LASI proĆ tem connect). This paper will focus primarily on thevides I/O a chip. very simple way of connecting the WD37C65C flexĆ ible disk controller chip to the GSC bus. The system boot A major goal of the Model 712 I/O subsystem was to proĆ ROMs are also directly controlled by the LASI chip. The vide a superset of the I/O performance and functionality Model 712 provides 16Ćbit CDĆquality audio and optionally available from other family members at a significantly reĆ supports two telephone lines. LASI provides the GSC interĆ duced manufacturing cost. This goal was bounded by the face and clock generation (using digital phaseĆlocked loops) reality of a finite amount of engineering resources, and it for both of these audio functions. Fig. 2 shows an approxiĆ was obvious from the start that integrating several of the I/O mate floor plan of the LASI chip. The floor plan shows the functions onto a single piece of silicon could greatly reduce general layout and relative size of each block. the total I/O subsystem manufacturing cost. Each function of the I/O subsystem was examined individually as aLASI candidate contains several system functions that help to minimize for integration. The value of maintaining exact driverĆlevelthe miscellaneous logic required in the system. This includes software compatibility was also evaluated with respectGSC to arbitration the and reset control. LASI also serves as the advantages of minimizing the hardware cost for eachGSC of interrupt the controller. I/O functions. It is possible to use up to four LASI chips on the same GSC The investigation indicated that the optimal solutionbus. for LASIthe can be programmed at reset to reside in one of Model 712 was an I/O subsystem that centered aroundfour different a address locations. The arbitration circuit supĆ single piece of custom VLSI. The chip that resultedports from chaining, this and LASI can be programmed to either drive investigation directly implements many of the requiredor I/O receive reset. functions and provides a glueless interface between the GSC bus and other common industry I/O devices. ThisSystem chip was Support Blocks named LASI, which is an acronym that refers toThe the two following sections give a brief overview of each of major pieces of functionality in the chip, LAN andLASI's SCSI. major The functional blocks that provide system support LASI chip also provides several miscellaneous systemfunctionality funcĆ in the Model 712, but do not directly support or tions that further reduce the amount of discrete logicimplement reĆ any I/O function. quired in the system. GSC Interface. The GSC (general system connect) bus conĆ Chip Overview nects the major VLSI components in the Model 712. It is a 32Ćbit bus with multiplexed address and data. The bus conĆ The LASI chip was designedm inm aCMOS 0.8Ć process and sists of 47 signals for devices capable of being a bus master. is 13.2 mm by 12.0 mm in size (including I/O pads). It conĆ The GSC bus is defined to run at up to 40 MHz giving a tains 520,000 FETs and is packaged in a 240Ćpin MQUAD peak transfer rate of 160 Mbytes/s. package. LASI dissipates approximately three watts when operating at the maximum GSC frequency (40 MHz).The LASI GSC interface block in LASI provides the connectivity was designed primarily using standardĆcell design methodolĆbetween the GSC bus and the wide variety of internal bus ogies although several areas required full custom design.blocks, many of which have different logical and timing reĆ quirements. This block converts the GSC bus to a less comĆ A functional block diagram of LASI is shown in Fig. 1. The plex internal LASI bus. The LASI internal bus is very similar majority of circuitry in LASI is consumed by only two funcĆ to the GSC bus, but it is not as heavily multiplexed and is tions, LAN and SCSI. Both of theses designs were purchased more flexible than the GSC bus in that it easily accommoĆ from outside companies and ported to HP's design process. dates the simpler interface for the generalĆpurpose I/O The SCSI functionality is exactly identical to the NCR 53C710 blocks in LASI. The GSC interface block handles bus errors SCSI controller, and the LAN functionality is exactly identical and keeps track of parity information for other internal to an Intel 82C596 LAN controller. 36April 1995 HewlettĆPackard Journal Hewlett-Packard Company 1995 CPU and Graphics LASI (1) Arbitration GSC Bus (1) (1) Phase-Locked General Loop Clock System Connect Generator (GSC) (1) (1,3) Miscellaneous Interrupt Register Controller (3) (2) SCSI Megacell RS-232 (3) (2) PS/2 Keyboard LAN Megacell and Mouse Controller (2,3) (1) Telephony Real-Time Card Parallel Port (Optional) Clock (2,3) (2,3) Flash Audio Audio EPROM Flexible Disk Circuit and Telephone Interface Interface (1) (2) Clock Generator EPROM Flexible and Reset Interface Disk Controller Controller (1) System Support Blocks (2) General I/O Functions (3) Blocks Capable of Initiating Transactions on the GSC Bus. Fig. 1. LASI chip block diagram. blocks, removing the associated complexity from theseA simpleconĆ strobe signal is asserted while internal data and trollers. Both master and slave devices reside on theaddress LASI buses are valid. Internal devices have no direct inĆ internal bus. teraction with bus errors. LASI is a slave whenever the CPU initiates data transfer.As a bus As master, a LASI is capable of initiating subword, word, slave, LASI supports only subword and word write,doubleĆword, and subĆ and quadĆword transactions on the GSC bus. word, word, and doubleĆword reads.* Internal slaveOnce devices one of LASI's internal bus masters owns the bus, it can only need to support a subset of these transactions.signify There the start of a transaction by assertingmaster_valid the are five different protocol behaviors for slave devicessignal in (see Fig. 3). The device must then simultaneously LASI: unpaced byte wide, paced byte wide, packeddrive byte its DMA addressmaster_address ( ), transaction type, and wide, unpaced word wide, and paced word wide. byte enables onto the bus. On a read, the first available data word will appear on the internal busmaster_ac- when the Unpaced devices, such as the realĆtime clock, don't use a knowledge signal is asserted by the GSC interface. The GSC handshake with the GSC interface, making their protocol interface will not accept anothermaster_valid until all the read very simple. When a device requires a variable length of data has been transferred. time to transfer data it is called paced. The SCSI interface is an example of a paced device. A packed deviceIf is a one timeout that error, address parity error, or data parity error is sends a sequence of bytes to make up a wordencountered or double on the GSC bus, the GSC interface will always word. The boot ROM interface is an example ofdo a packed a normal handshake for the transaction by asserting the device. master_acknowledge signal. The transaction will complete as usual except that an error is logged, disabling arbitration for * In PA-RISC a subword is typically one byte, a word is 32 bits, a double word is 64 bits, and the device so it cannot be a bus master again. This means a quad word is 128 bits. Hewlett-Packard Company 1995 April 1995 HewlettĆPackard Journal37 RS-232 Audio PS/2 Intel 82C596 LAN Interface PS/2 Coprocessor External 8-Bit Bus Controller Real- Parallel Time Port LAN Clock Interface Clock Buffer Interrupt Controller NCR 53C710 SCSI SCSI Controller Interface GSC Phase-Locked Phase-Locked Interface Loop Clock Loop Clock Generator Generator Arbitration Fig. 2. LASI floorplan. that internal masters, at the hardware level, nevercontrolled need to by another arbiter. This feature allows LASI to be respond directly to bus errors. When the GSC interfaceused in block larger systems that provide their own arbitration sees a timeout error it will, from the perspectivecircuit. of its A interĆ second LASI can also be used for I/O expansion nal bus blocks, complete a transaction normally. Inin this lowĆend way systems in which the first LASI is providing the the GSC's error signaling mechanism can correctly terminatecentral arbitration. Support for multiple LASI's on the same an errant transaction without adding complexity to LASI'sGSC bus makes the speedy development of multifunction internal blocks. I/O expansion boards a relatively simple task. Parity is generated in the GSC interface wheneverThe LASI LASI design was simplified by requiring that the LASI sources data or an address on the bus. Parity isarbitration checked circuit gain control of the GSC bus before granting whenever LASI is a data sink. LASI does not respondthe internal to bus to potential bus masters. This saved a signifiĆ address parity errors on the GSC bus, which resultcant in amount a of complexity in the GSC interface block as well timeout error.
Recommended publications
  • Service Handbook B Class Model B132L/B132L+/B160L/B180L
    Service Handbook B Class Model B132L/B132L+/B160L/B180L HP Part No. A4190-90041 Edition E1097 Printed in U.S.A. Hewlett-Packard Co. 1997 Printing History First Printing: October 1997 UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Lim- ited. NOTICE The information contained in this document is subject to change without notice. HEWLETT-PACKARD MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors con- tained herein or for incidental or consequential damages in con- nection with the furnishing, performance or use of this material. Hewlett-Packard assumes no responsibility for the use or reliabil- ity of its software on equipment that is not furnished by Hewlett- Packard. This document contains proprietary information that is protected by copyright. All rights reserved. No part of this document may be photocopied, reproduced or translated to another language without the prior written consent of Hewlett-Packard Company. RESTRICTED RIGHTS LEGEND. Use, duplication, or disclo- sure by government is subject to restrictions as set forth in subdivi- sion (c) (1) (ii) of the Rights in Technical Data and Computer Software Clause at DFARS 252.227.7013. Hewlett-Packard Co., 3000 Hanover St., Palo Alto, CA 94304. 10 9 8 7 6 5 4 3 2 1 ii Safety and Regulatory Statements Safety and Regulatory Statements This section contains safety and regulatory statements pertaining to your B132L/B132L+/B160L/B180L workstation.
    [Show full text]
  • Integrating DMA Into the Generic Device Model
    Integrating DMA Into the Generic Device Model James E.J. Bottomley SteelEye Technology, Inc. http://www.steeleye.com [email protected] Abstract across architectures prior to PCI, the most prominent be- ing EISA. Finally, some manufacturers of I/O chips de- signed them not to be bus based (the LSI 53c7xx series This paper will introduce the new DMA API for the of SCSI chips being a good example). These chips made generic device model, illustrating how it works and ex- an appearance in an astonishing variety of cards with an plaining the enhancements over the previous DMA Map- equal variety of bus interconnects. ping API. In a later section we will explain (using illus- trations from the PA-RISC platform) how conversion to The major headache for people who write drivers for the new API may be achieved hand in hand with a com- non-PCI or multiple bus devices is that there was no plete implementation of the generic device API for that standard for non-PCI based DMA, even though many of platform. the problems encountered were addressed by the DMA Mapping API. This gave rise to a whole hotchpotch of solutions that differed from architecture to architecture: On Sparc, the DMA Mapping API has a completely 1 Introduction equivalent SBUS API; on PA-RISC, one may obtain a “fake” PCI object for a device residing on a non-PCI bus which may be passed straight into the PCI based DMA Back in 2001, a group of people working on non-x86 API. architectures first began discussing radical changes to the way device drivers make use of DMA.
    [Show full text]
  • CE Handbook Series 9X8lx/RX Family and Model 800 Ex5 Class
    HP 3000 and HP 9000 PA-RISC Computer Systems CE Handbook Series 9x8LX/RX Family and Model 800 Ex5 Class FliOW HEWLETT .:~ PACKARD HP Part No. A2051-90003 Printed in U.S.A. 1993 Edition 1 - E 1293 For HP Internal Use Only Notice Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard. This document contains proprietary information which is protected by copyright. All rights are reserved. No part of this document may be photographed, reproduced, or translated to another language without prior written consent of Hewlett-Packard Company. The information contained in this document is subject to change without notice. © Copyright Hewlett-Packard Company, 1993. All rights reserved. Printing History New editions are complete revisions of the manual. Update packages, which are issued between editions, contain additional and replacement pages to be merged into the manual by the customer. The dates on the title page change only when a new edition or a new update is published. No information is incorporated into a reprinting unless it appears as a prior update; the edition does not change when an update is incorporated. Many product updates and fixes do not require manual changes and, conversely, manual corrections may be done without accompanying product changes.
    [Show full text]
  • IBM Tape Device Drivers IBM
    IBM Tape Device Drivers IBM Installation and User's Guide GC27-2130-21 IBM Tape Device Drivers IBM Installation and User's Guide GC27-2130-21 ii IBM Tape Device Drivers: Installation and User's Guide Twenty-second Edition (November 2015) This twenty-second edition of the IBM Tape Device Drivers Installation and User's Guide, GC27-2130-21, replaces and makes obsolete the following manual: IBM Tape Device Drivers Installation and User's Guide, GC27-2130-20. © Copyright IBM Corp. 2007, 2015 iii iv IBM Tape Device Drivers: Installation and User's Guide Read this first Accessing online technical support For online technical support for your Library, visit: v www.ibm.com/support. Registering for My Notification My Notification registration provides email notification when firmware levels have been updated and are available for download and installation. To register for My Notification: 1. Visit the web at http://www-01.ibm.com/software/support/einfo.html. 2. Click My Notifications. Note: Library firmware and tape drive firmware are verified and released together. When updating to the latest firmware, verify that all installed components such as tape drives, and library are at the latest levels noted on the Support website. Mixing different levels of library and tape drive firmware is not supported and can cause unpredictable results. Contacting IBM technical support In the USA: Call 1-800-IBM_SERV (1-800-426-7378). All other Countries/Regions: Visit www.ibm.com/support To open a Service Request online: Under Support & downloads, click Open a service request. © Copyright IBM Corp. 2007, 2015 v vi IBM Tape Device Drivers: Installation and User's Guide Preface These publications and URLs provide user information and installation assistance for IBM® tape drive, medium changer, and library device drivers.
    [Show full text]
  • Service Handbook
    Service Handbook J Class Workstation HP Part No. A2876–90041 Edition E0498 Update to Service Handbook J Class Workstation HP Part No. A2876–90040 R Hewlett–Packard Company 3404 E. Harmony Rd., Ft. Collins, CO 80528–9599 NOTICE The information contained in this document is subject to change without notice. HEWLETT–PACKARD WARRANTY STATEMENT HP PRODUCT DURATION OF WARRANTY J Class Workstation one year 1. HP warrants HP hardware, accessories and supplies against defects in materials and workmanship for the period specified above. If HP receives notice of such defects during the warranty period, HP will, at its option, either repair or replace products which prove to be defective. Replacement products may be either new or like–new. 2. HP warrants that HP software will not fail to execute its programming instructions, for the period specified above, due to defects in material and workmanship when properly installed and used. If HP receives notice of such defects during the warranty period, HP will replace software media which does not execute its programming instructions due to such defects. 3. HP does not warrant that the operation of HP products will be uninterrupted or error free. If HP is unable, within a reasonable time, to repair or replace any product to a condition as warranted, customer will be entitled to a refund of the purchase price upon prompt return of the product. 4. HP products may contain remanufactured parts equivalent to new in performance or may have been subject to incidental use. 5. The warranty period begins on the date of delivery or on the date of installation if installed by HP.
    [Show full text]
  • Independent PA-RISC and Itanium Reference Book
    OpenPA The book of PA-RISC Paul Weissmann Bonn This document and its content are Copyright © 1999-2021 Paul Weissmann, Bonn, Germany, unless otherwise noted. Berlin, Bonn, Palo Alto, San Francisco No parts of this document may be reproduced or copied without prior written permission. Commercial use of the content is prohibited. OpenPA.net, the information resource on PA-RISC. Second edition Release 2.8 Bonn, May 2021 Other editions: Second edition 2.7: July 2020 Second edition 2.6: January 2018 Second edition 2.5: January 2016 Second edition 2.4: July 2012 Second edition 2.3: July 2009 Second edition 2.2: January 2009 Second edition 2.1: October 2008 Second edition 2.0: May 2008 First edition 1.2: December 2007 First edition 1.1: November 2007 First edition 1.0: July 2006 OpenPA.net (online) is a registered serial publication, ISSN 1866-2757. Paul Weissmann can be reached by e-mail: [email protected]. and online at Insignals Cyber Security and OpenKRITIS. Preface This is the print edition of the OpenPA.net website from Spring 2021. OpenPA is a resource for HP PA-RISC and Itanium computers with technical descriptions of workstations, servers, their hardware architecture and supported operating systems This project is independent of and does not represent The Hewlett Packard Company in any way. This is the Second Edition 2.8. Set with LATEX. Changes in Second Edition 2.8 since the last edition (2020): ê Many revisions and corrections (thanks!) ê Text and language in all chapters ê TeX backend update All other changes are listed in chapter 5.1.
    [Show full text]
  • A Low-Cost Workstation with Enhanced Performance and I/O Capabilities
    A Low-Cost Workstation with Enhanced Performance and I/O Capabilities Various entities involved in product development came together at different times to solve a design problem, evaluate costs, and make adjustments to their own projects to accommodate the cost and performance goals of the low-cost HP 9000 B-class workstation. by Scott P. Allan, Bruce P. Bergmann, Ronald P. Dean, Dianne Jiang, and Dennis L. Floyd The design and development of the HP 9000 B-class workstation is a good example of cooperative engineering. In cooperative engineering, the various entities involved in product development come together at different times to solve a problem or make adjustments to their own projects to accommodate a common need. Examples of this cooperation for the B-class workstation include coordination between system designers and firmware developers, the addition of new functionality without impacting the development schedule, close ties with manufacturing, evaluation of implementation based on detailed cost models, and simplification of the PA 7300LC design by moving clocking functions onto a small chip on the system board. Design Objectives The design objectives for the B-class workstation were low cost, quick time to market, performance, functionality, longevity, and modularity. In addition to these objectives, the development team’s main goal was to produce a workstation based on the PA 7300LC processor that would be comparably priced to the HP 9000 Model 715 workstation, but with superior performance and I/O capabilities. This goal and the design objectives remained the same throughout the project. With low cost as the primary objective, any feature that was perceived as too costly or of limited value to our customer base was not included.
    [Show full text]
  • Integrating DMA Into the Generic Device Model
    Integrating DMA Into the Generic Device Model James E.J. Bottomley SteelEye Technology, Inc. http://www.steeleye.com [email protected] Abstract 1.1 Legacy Issues This paper will introduce the new DMA API for the generic device model, illustrating how it works and explaining the enhancements over the previous DMA Mapping API. In a later sec- One of the issues left unaddressed by the DMA tion we will explain (using illustrations from Mapping API was that of legacy buses: Most the PA-RISC platform) how conversion to the non-x86 architectures had developed other bus new API may be achieved hand in hand with a types prior to the adoption of PCI (e.g. sbus complete implementation of the generic device for the sparc; lasi and gsc bus for PA-RISC) API for that platform. which were usually still present in PCI based machines. Further, there were other buses that migrated across architectures prior to PCI, 1 Introduction the most prominent being EISA. Finally, some manufacturers of I/O chips designed them not to be bus based (the LSI 53c7xx series of SCSI Back in 2001, a group of people working on chips being a good example). These chips non-x86 architectures first began discussing made an appearance in an astonishing variety radical changes to the way device drivers make of cards with an equal variety of bus intercon- use of DMA. The essence of the proposal nects. was to mandate a new DMA Mapping API[1] which would be portable to all architectures The major headache for people who write then supported by Linux.
    [Show full text]
  • Verfahren Zum Auslesen Von Speicherzellen Mit Unterschiedlichen
    (19) *DE102012108545A120130404* (10) DE 10 2012 108 545 A1 2013.04.04 (12) Offenlegungsschrift (21) Aktenzeichen: 10 2012 108 545.5 (51) Int Cl.: G11C 16/26 (2013.01) (22) Anmeldetag: 13.09.2012 (43) Offenlegungstag: 04.04.2013 (30) Unionspriorität: (74) Vertreter: 10-2011-0098809 29.09.2011 KR Kuhnen & Wacker Patent- und Rechtsanwaltsbüro, 85354, Freising, DE (71) Anmelder: Samsung Electronics Co., Ltd., Suwon City, (72) Erfinder: Kyungki, KR Joo, Sang-Hyun, Gyeonggi-do, KR; Song, Kiwhan, Seoul, KR; Lee, Ju Seok, Seoul, KR; Choi, Kiwhan, Gyeonggi-do, KR Die folgenden Angaben sind den vom Anmelder eingereichten Unterlagen entnommen (54) Bezeichnung: Verfahren zum Auslesen von Speicherzellen mit unterschiedlichen Schwellwertspannungen ohne Änderung der Wortleitungsspannung, sowie nicht-flüchtige Speichervorrichtung, die dieses verwendet (57) Zusammenfassung: Ein Soft-Decision-Leseverfahren einer nichtflüchtigen Speichervorrichtung enthält Empfan- gen eines Soft-Decision-Lesebefehls, Anlegen einer Lese- spannung (Vwl2), eine ausgewählte Wortleitung (WL), Vorla- den von Bitleitungen (BL), die jeweils mit ausgewählten Spei- cherzellen (A, B, C) der ausgewählten Wortleitung (WL) ver- bunden sind, kontinuierliches Abtasten von Zuständen der ausgewählten Speicherzellen (A, B, C). Die vorgeladenen Spannungen der Bitleitungen (BL) und die an die ausgewähl- te Wortleitung (WL) gelieferte Lesespannung (Vwl2) werden nicht variiert während des Abtasten von Zuständen der aus- gewählten Speicherzellen (A, B, C). DE 10 2012 108 545 A1 2013.04.04 Beschreibung QUERVERWEIS AUF VERWANDTE ANMELDUNG [0001] Es wird die Priorität der am 29. September 2011 eingereichten koreanischen Patentanmeldung, deren Gesamtheit hierin durch Inbezugnahme aufgenommen wird, beansprucht gemäß 35 U. S. C § 119. HINTERGRUND [0002] Beispielhafte Ausführungsformen beziehen sich auf nichtflüchtige Speichervorrichtungen mit Speicher- zellen, die jeweils eine variable Schwellwertspannung besitzen.
    [Show full text]
  • Service Handbook C Class Models C100, C110, C160L, C160, C180
    Service Handbook C Class Models C100, C110, C160L, C160, C180, C200, C240 and C360 HP Part No. A4200-90042 Edition E1298 Printed in U.S.A. Hewlett-Packard Co. 1998 Printing History First Printing: August 1998 UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Lim- ited. NOTICE The information contained in this document is subject to change without notice. HEWLETT-PACKARD WARRANTY STATEMENT HP PRODUCT DURATION OF WARRANTY C160/C180/C200/C240/C360 one year 1. HP warrants HP hardware, accessories and supplies against defects in materials and workmanship for the period specified above. If HP receive notice of such defects during the warranty period, HP will, at its option, either repair or replace products which prove to be defective. Replacement products may be either new or like-new. 2. HP warrants that HP software will not fail to execute its pro- gramming instructions, for the period specified above, due to defects in material and workmanship when properly installed and used. If HP receives notice of such defects during the warranty period, HP will replace software media which does not execute its programming instructions due to such defects. 3. HP does not warrant that the operation of HP products will be uninterrupted or error free. If HP is unable, within a reasonable time, to repair or replace any product to a condition as warranted, customer will be entitled to a refund of the purchase price upon prompt return of the product. 4. HP products may contain remanufactured parts equivalent to new in performance or may have been subject to incidental use.
    [Show full text]
  • The Openpa Project First Edition
    The OpenPA Project First Edition Paul Weissmann Berlin Preface This is the dead-tree, made-for-printing edition of The OpenPA Project (openpa.net). The content is based on the online version’s content from mid-June 2006, parts and pieces were removed and modified for a sane print-out version. This document and its content are Copyright © 1999-2006 Paul Weissmann, Berlin, Germany, unless otherwise noted. No parts of this document may be reproduced or copied without prior written permission. Commercial use of the content is prohibited. The OpenPA Project is an independent resource for information on PA-RISC based computers from HP and other vendors. This project is independent of and does not represent The Hewlett Packard Company in any way. This is the first prerelease edition and may still contain contentual and typographical errors, which hopefully will be corrected in a next edition. Moreover we still have plans for a larger restructuring and expansion for the content for the print edition, which we also hope to include in the next edition, which is very optimistically slated for 2007. Besides adding more and polishing the content we have the dim hope of improving and fleshing out the print/conversion infrastructure, since there still remain several rough XSLT and TEXedges. Set with LATEX. Thanks Many people helped The OpenPA Project with contributions and support over the years. Thanks go to: • Bill Bradford, for hosting the project’s site in its early days • Frank McConnell, for the HP 9000/500 and FOCUS information • Götz Hoffart, for the CSS/HTML help and inspiration • Grant Grundler, for his continuing support • Michael Piotrowski, for corrections and HP-UX background information • Michael Shalayeff, for hosting the project’s site and providing PA-RISC wisdom • Ti Kan, for the technical explanations on the Stratus architecture i ii Contents 1 Introduction 1 2 PA-RISC Hardware Details 3 2.1 PA-RISC Processors .
    [Show full text]
  • Delivering PCI in HP B-Class and C-Class Workstations: a Case Study in the Challenges of Interfacing with Industry Standards
    Delivering PCI in HP B-Class and C-Class Workstations: A Case Study in the Challenges of Interfacing with Industry Standards Ric L. Lewis In the highly competitive workstation market, customers demand a wide range Erin A. Handgen of cost-effective, high-performance I/O solutions. An industry-standard I/O Nicholas J. Ingegneri subsystem allows HP workstations to support the latest I/O technology. Glen T. Robinson Industry-standard I/O buses like the Peripheral Component Interconnect (PCI) allow systems to provide a wide variety of cost-effective I/O functionality. The desire to include more industry-standard interfaces in computer systems continues to increase. This article points out some of the specific methodolo- gies used to implement and verify the PCI interface in HP workstations and describes some of the challenges associated with interfacing with industry- standard I/O buses. PCI for Workstations One of the greatest challenges in designing a workstation system is determining the best way to differentiate the design from competing products. This decision determines where the design team will focus their efforts and have the greatest opportunity to innovate. In the computer workstation industry, the focus is typically on processor performance coupled with high-bandwidth, low-latency memory connections to feed powerful graphics devices. The performance of nongraphics I/O devices in workstations is increasing in importance, but the availability of cost-effective solutions is still the chief concern in designing an I/O subsystem. Rather than providing a select few exotic high-performance I/O solutions, it is better to make sure that there is a wide range of cost-effective solutions to provide the I/O functionality that each customer requires.
    [Show full text]