DOCSLIB.ORG

Openvms VAX Device Support Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Openvms VAX Device Support Manual OpenVMS VAX Device Support Manual Order Number: AA–PWC8A–TE March 1994 This manual describes how to write a driver for a device connected to a VAX processor. It discusses the required and optional components of a driver and explains their functions. It details the requirements the operating system imposes upon driver code and includes guidelines for creating, loading, and debugging a driver that can run on OpenVMS uniprocessing and multiprocessing systems. Revision/Update Information: This manual supersedes the OpenVMS VAX Device Support Manual, Version 6.0. Software Version: OpenVMS VAX Version 6.1 Digital Equipment Corporation Maynard, Massachusetts March 1994 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1994. All rights reserved. The postpaid Reader’s Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: BI, Bookreader, CI, CMI, DEC, DECnet, Digital, MASSBUS, MicroVAX, MSCP, NMI, OpenVMS, Q–bus, Q22–bus, SBI, TMSCP, TURBOchannel, UNIBUS, VAX, VAXBI, VAXcluster, VAX DOCUMENT, VAX MACRO, VAXstation, VMS, and the DIGITAL logo. The following are third-party trademarks: UNIX is a registered trademark licensed exclusively by X/Open Co. Ltd. Internet is a registered trademark of Internet, Inc. All other trademarks and registered trademarks are the property of their respective holders. ZK5502 This document is available on CD–ROM. This document was prepared using VAX DOCUMENT Version 2.1. Send Us Your Comments We welcome your comments on this or any other OpenVMS manual. If you have suggestions for improving a particular section or find any errors, please indicate the title, order number, chapter, section, and page number (if available). We also welcome more general comments. Your input is valuable in improving future releases of our documentation. You can send comments to us in the following ways: • Internet electronic mail: [email protected] • Fax: 603-881-0120 Attn: OpenVMS Documentation, ZKO3-4/U08 • A completed Reader’s Comments form (postage paid, if mailed in the United States), or a letter, via the postal service. Two Reader’s Comments forms are located at the back of each printed OpenVMS manual. Please send letters and forms to: Digital Equipment Corporation Information Design and Consulting OpenVMS Documentation 110 Spit Brook Road, ZKO3-4/U08 Nashua, NH 03062-2698 USA You may also use an online questionnaire to give us feedback. Print or edit the online file SYS$HELP:OPENVMSDOC_SURVEY.TXT. Send the completed online file by electronic mail to our Internet address, or send the completed hardcopy survey by fax or through the postal service. Thank you. Contents Preface ............................................................ xxi Part I OpenVMS VAX Device Driver Environment 1 Introduction to Device Drivers 1.1 Driver Functions ............................................ 1–2 1.2 Driver Components . ........................................ 1–2 1.2.1 Driver Tables ............................................ 1–2 1.2.2 Driver Routines . ........................................ 1–3 1.3 I/O Database ............................................... 1–4 1.3.1 Driver Tables ............................................ 1–4 1.3.2 Data Structures . ........................................ 1–4 1.3.3 I/O Request Packets ....................................... 1–6 1.4 Synchronization of Driver Activity ............................... 1–6 1.5 Driver Context .............................................. 1–7 1.5.1 Example of Driver Context-Switching . ....................... 1–8 1.6 Hardware Considerations ...................................... 1–9 1.6.1 Driver Dependency on VAX Processing Systems . ............... 1–10 1.6.1.1 Address Space ........................................ 1–10 1.6.1.2 VAX–11/780, VAX–11/785, and VAX 8600/8650 Systems . ....... 1–11 1.6.1.3 VAX–11/750 System .................................... 1–12 1.6.1.4 VAX–11/730 System .................................... 1–14 1.6.1.5 VAX 82x0/83x0, VAX 85x0/8700/88x0, and VAX 6000 Series Systems ............................................. 1–14 1.6.1.6 VAX 9000 Series System ................................ 1–17 1.6.1.7 VAX 7000 Series and VAX 10000 Series Systems .............. 1–19 1.6.1.8 MicroVAX 3400/3600/3900 Series, MicroVAX/VAXstation II, and VAX 4000 Series Systems ................................ 1–21 1.6.1.9 MicroVAX/VAXstation 3100 and VAXstation 3520/3540 Systems ............................................. 1–22 1.7 Programmed-I/O and Direct-Memory-Access Transfers ............... 1–24 1.7.1 Programmed I/O . ........................................ 1–24 1.7.2 Direct-Memory-Access I/O . ................................ 1–24 1.8 Buffered and Direct I/O ....................................... 1–25 1.9 Example of an I/O Request .................................... 1–26 v 2 Handling a $QIO Request 2.1 Driver Code for the LP11 Write Function ......................... 2–1 2.2 A User Process I/O Request .................................... 2–3 2.3 Device-Independent System I/O Preprocessing . ................... 2–3 2.4 Device-Dependent I/O Preprocessing by the Driver .................. 2–3 2.5 Queuing the I/O Request Packet to the Driver . ................... 2–4 2.6 Activating the Printer ........................................ 2–5 2.7 Waiting for a Device Interrupt .................................. 2–5 2.8 Handling Interrupts .......................................... 2–6 2.9 I/O Postprocessing by the Driver ................................ 2–6 2.10 System I/O Postprocessing . .................................... 2–7 3 Synchronization of I/O Request Processing 3.1 Interrupt Priority Levels . .................................... 3–1 3.1.1 Interrupt Service Routines .................................. 3–3 3.1.2 IPL Use During I/O Processing . ............................ 3–3 3.1.2.1 IPL 2 (IPL$_ASTDEL) .................................. 3–3 3.1.2.2 IPL 4 (IPL$_IOPOST) .................................. 3–4 3.1.2.3 IPL 8 to IPL 11 (Fork IPLs) . ............................ 3–5 3.1.2.4 IPL 20 to IPL 23 (Device IPLs) ........................... 3–5 3.1.2.5 IPL 31 (IPL$_POWER) ................................. 3–6 3.1.3 Additional IPLs .......................................... 3–6 3.1.3.1 IPL 3 (IPL$_RESCHED) ................................ 3–6 3.1.3.2 IPL 6 (IPL$_QUEUEAST) . ............................ 3–6 3.1.3.3 IPL 7 (IPL$_TIMERFORK) . ............................ 3–7 3.1.3.4 IPL 8 (IPL$_SYNCH) ................................... 3–7 3.1.3.5 IPL 11 (IPL$_MAILBOX) ................................ 3–7 3.1.3.6 IPL 14 (XDELTA Entry IPL) . ............................ 3–8 3.1.3.7 IPL 22 or IPL 24 (Interval Clock IPLs) . ................... 3–8 3.1.4 Modifying IPL in Driver Code . ............................ 3–8 3.1.4.1 Raising IPL .......................................... 3–9 3.1.4.2 Lowering IPL ......................................... 3–10 3.2 Spinlocks .................................................. 3–11 3.2.1 Fork Locks . ............................................ 3–14 3.2.2 Device Locks ............................................ 3–15 3.3 Device Driver Synchronization .................................. 3–15 3.3.1 Overview of the Synchronization of an I/O Operation . ........... 3–15 3.3.2 Synchronizing the Device Database ........................... 3–19 3.3.3 Synchronizing at Driver Fork Level ........................... 3–20 3.3.3.1 Forking and the System Fork Dispatcher ................... 3–21 3.3.3.2 Restrictions on Fork Processes ............................ 3–22 3.4 Resource Wait Queues ........................................ 3–23 3.4.1 Competing for a Controller’s Data Channel . ................... 3–23 4 Overview of I/O Processing 4.1 Preprocessing an I/O Request .................................. 4–4 4.1.1 Process I/O Channel Assignment . ............................ 4–5 4.1.2 Locating a Device Driver in the I/O Database ................... 4–5 4.1.2.1 Channel Request Block ................................. 4–5 4.1.2.2 Interrupt Dispatch Block ................................ 4–7 4.1.2.3 Device Data Block . .................................... 4–8 4.1.3 Validating the I/O Function ................................. 4–8 vi 4.1.4 Checking Process I/O Request Quotas . ....................... 4–8 4.1.5 Validating the I/O Status Block .............................. 4–8 4.1.6 Allocating and Setting Up an I/O Request Packet . ............... 4–8 4.1.7 FDT Processing . ........................................ 4–9 4.2 Handling Device Activity ...................................... 4–12 4.2.1 Creating a Driver Fork Process to Start I/O .................... 4–13 4.2.2 Activating a Device and Waiting for an Interrupt . ............... 4–14 4.2.3 Handling a Device Interrupt ................................ 4–15 4.2.4 Switching from Interrupt to Fork Process Context . ............... 4–15 4.2.5 Activating a Fork Process
Load more

Recommended publications
  • Muxserver 380 Hardware Installation Manual Order Number EK-DSRZD-IM-002
    MUXserver 380 Hardware Installation Manual Order Number EK-DSRZD-IM-002 2nd Edition Second Edition - February 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation (Australia) Pty. Limited. Digital Equipment Corporation (Australia) Pty. Limited assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation (Australia) Pty. Limited or its affiliated companies. Copyright ©1992 by Digital Equipment Corporation (Australia) Pty. Limited. All Rights Reserved. Printed in Australia. The postpaid READER’S COMMENTS form on the last page of this document requests the user’s critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC DIBOL UNIBUS DEC/CMS EduSystem UWS DEC/MMS IAS VAX DECnet MASSBUS VAXcluster DECstation PDP VMS DECsystem–10 PDT VT DECSYSTEM–20 RSTS DECUS RSX DECwriter ULTRIX dt Contents Preface viii Chapter 1 Introduction 1.1 Overview of the MUXserver 380 Network . ................................1–1 1.2 Typical MUXserver 380 Network Configuration ...............................1–2 1.3 The MUXserver 380 . .................................................1–3 1.4 Connecting the MUXserver 380 . ........................................1–6 1.5 Installation Overview . ................................................1–10 1.6 Items Required for MUXserver 380 Installation .............................1–11 1.7 Service Options ......................................................1–12 1.7.1 Digital On-Site Service .
    [Show full text]
  • A Machine-Independent DMA Framework for Netbsd
    AMachine-Independent DMA Framework for NetBSD Jason R. Thorpe1 Numerical Aerospace Simulation Facility NASA Ames Research Center Abstract 1.1. Host platform details One of the challenges in implementing a portable In the example platforms listed above,there are at kernel is finding good abstractions for semantically- least three different mechanisms used to perform DMA. similar operations which often have very machine- The first is used by the i386 platform. This mechanism dependent implementations. This is especially impor- can be described as "what you see is what you get": the tant on modern machines which share common archi- address that the device uses to perform the DMA trans- tectural features, e.g. the PCI bus. fer is the same address that the host CPU uses to access This paper describes whyamachine-independent the memory location in question. DMA mapping abstraction is needed, the design consid- DMA address Host address erations for such an abstraction, and the implementation of this abstraction in the NetBSD/alpha and NetBSD/i386 kernels. 1. Introduction NetBSD is a portable, modern UNIX-likeoperat- ing system which currently runs on eighteen platforms covering nine processor architectures. Some of these platforms, including the Alpha and i3862,share the PCI busasacommon architectural feature. In order to share device drivers for PCI devices between different platforms, abstractions that hide the details of bus access must be invented. The details that must be hid- den can be broken down into twoclasses: CPU access Figure 1 - WYSIWYG DMA to devices on the bus (bus_space)and device access to host memory (bus_dma). Here we will discuss the lat- The second mechanism, employed by the Alpha, ter; bus_space is a complicated topic in and of itself, is very similar to the first; the address the host CPU and is beyond the scope of this paper.
    [Show full text]
  • Digital Technical Journal, Number 7, August 1988: CVAX
    Digital Technical Tournal Digital Equipment Corporation Managing Editor Richard W Beam Edltor Jane C. Dlak Pcoductloa St& Production Editor - Helen 1 Partenon Designer - Charlotte Bell Typographers -Jonathan M. Bohy Macgaret Burdine lllusultor - Deborah Kc~lcy Advisoiy Board Samuel H. Fuller, Chairman Robert M. Glorioso John W. McCredle Mahendra R. Patel F. Grant Saviers William D. Srrcckr Victor A. Vyssutsky The Digital Technical Journal is published by Digital Equipment Corporatloa, 77 Reed Road, Hudson, Magsachu~etts0 1749. Changes of address should be sent to Digital Equipment Corporation. attention: List Maintenance. I0 Forbes Road, Northboro, MA 01532 Please indude the address label wlth changes marked. Comments on the content of any paper arc welcomed. Write to the editor at Mall Stop HL02.3/K11 at the published~bpaddress. Comments can ahbe sent on the BNET to RDVAX: :BIAKEor on the ARPANET to B~%RDVAX.DE~DE~. Copyright @ 1988 Digital Equipment Corporation. Copying without fee is permitted provided that such copies are made for use in educational lnstltutions by faculty members and are nor distributed for commercial advantage. Abstncting with credit of Digital Equipment Corporation's authorship is permltted. Requests for other copies for a Pee may br made to Digiul Press of Digital Equipment Corporation. A11 rights reserved. The information in this journal is subject to change without notice and should not bc construed as a com- mltment by Digital Equipment Corporation. Digital Equipment Corpmtion assumes no responslbllity for any errors that may appcss in this document ISSN 0898.901X Documentatlcm Number EY-6742H-DP The following are wademarks of Digital Gquipmcnt Corporation: ALL.IN-I.
    [Show full text]
  • PDP-11 Bus Handbook (1979)
    The material in this document is for informational purposes only and is subject to change without notice. Digital Equipment Corpo­ ration assumes no liability or responsibility for any errors which appear in, this document or for any use made as a result thereof. By publication of this document, no licenses or other rights are granted by Digital Equipment Corporation by implication, estoppel or otherwise, under any patent, trademark or copyright. Copyright © 1979, Digital Equipment Corporation The following are trademarks of Digital Equipment Corporation: DIGITAL PDP UNIBUS DEC DECUS MASSBUS DECtape DDT FLIP CHIP DECdataway ii CONTENTS PART 1, UNIBUS SPECIFICATION INTRODUCTION ...................................... 1 Scope ............................................. 1 Content ............................................ 1 UNIBUS DESCRIPTION ................................................................ 1 Architecture ........................................ 2 Unibus Transmission Medium ........................ 2 Bus Terminator ..................................... 2 Bus Segment ....................................... 3 Bus Repeater ....................................... 3 Bus Master ........................................ 3 Bus Slave .......................................... 3 Bus Arbitrator ...................................... 3 Bus Request ....................................... 3 Bus Grant ......................................... 3 Processor .......................................... 4 Interrupt Fielding Processor .........................
    [Show full text]
  • PDP-A RAM LIBRARY PROG
    .. [Q]OECUS ! PDP-a RAM LIBRARY PROG . CATALOG PDP-8 PROGRAM LIBRARY CATALOG The DECUS Library Staff wishes to express appreciation to the many authors who have submitted new or revised programs and to the many other individuals who have contributed their time to improving the DECUS Library. June 1979 C DIGITAL EQUIPMENT COMPUTER USERS SOCIETY This is a complete PDP-8 DECUS Library Catalog. It includes a complete listing of current PDP-8, BASIC-8, and FOCAL-8 DECUS programs. First Edition December 1973 Updated July 1974 Updated December 1974 Updated May 1975 Updated November 1975 Updated June 1976 Combined and revised March 1977 Updated and revised August 1978 Updated and revised June 1979 Copyright © 1979, Digital Equipment Corporation, Maynard, Massachusetts The DECUS Program Library is a clearing house only; it does not sell, generate or test programs. All programs and information are provided "AS IS". DIGITAL EQUIPMENT COMPUTER USERS SOCIETY, DIGITAL EQUIPMENT CORPORATION AND THE CONTRIBUTOR DISCLAIM ALL WARRANTIES ON THE PROGRAMS AND ANY MEDIA ON WHICH THE PROGRAMS ARE PROVIDED, INCLUDING WITHOUT LIMITATION, ALL IMPLIED WARRANTIES OF MER­ CHANT ABILITY AND FITNESS. The descriptions, service charges, exchange rates, and availability of software available from the DECUS Library are subject to change without notice. The following are trademarks of Digital Equipment Corporation: COMPUTER LABS DECtape FOCAL PDP COMTEX DECUS INDAC PHA DDT DIBOL LAB·S RSTS DEC DIGITAL MASSBUS RSX DECCOMM EDUSYSTEM OMNIBUS TYPESET-8 DECsystem·l0 FLIP CHIP OS-8 TYPESET·ll DECSYSTEM·20 UNIBUS 5/79-14 CONTENTS iii Section 1 General Information 1.1 Special Announcements for 1979 ......
    [Show full text]
  • VAX 6000 Series Installation Guide
    VAX 6000 Series Installation Guide Order Number EK–600EB–IN.002 This guide is intended for use by Digital customer service engineers and self-maintenance customers installing a VAX 6000 series system. digital equipment corporation maynard, massachusetts First Printing, October 1990 Revised, November 1991 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software, if any, described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Copyright ©1990, 1991 by Digital Equipment Corporation. All Rights Reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: DEC PDP VAXcluster DEC LANcontroller ULTRIX VAXELN DECnet UNIBUS VMS DECUS VAX XMI DWMVA VAXBI FCC NOTICE: The equipment described in this manual generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such radio frequency interference when operated in a commercial environment. Operation of this equipment in a residential area may cause interference, in which case the user at his own expense may be required to take measures to correct the interference.
    [Show full text]
  • VAX 6000 Platform Technical User's Guide
    VAX 6000 Platform Technical User’s Guide Order Number: EK–600EA–TM-001 This manual serves as a reference for field-level repair or programming for systems based on the VAX 6000 platform. The manual describes the platform architecture, the XMI system bus, the DWMBB XMI-to-VAXBI adapter, and the power and cooling systems found in the H9657-CA/CB/CU cabinet. Digital Equipment Corporation First Printing, May 1991 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software, if any, described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Copyright ©1991 by Digital Equipment Corporation All Rights Reserved. Printed in U.S.A. The postpaid READER’S COMMENTS form on the last page of this document requests the user’s critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEMNA PDP VAXcluster DEC ULTRIX VAXELN DEC LANcontroller UNIBUS VMS DECnet VAX XMI DECUS VAXBI dt This document was prepared using VAX DOCUMENT, Version 1.2 Contents PREFACE xiii CHAPTER 1 THE VAX 6000 PLATFORM OVERVIEW 1–1 1.1 SPECIFICATIONS 1–2 1.2 SYSTEM FRONT VIEW 1–4
    [Show full text]
  • Digital Technical Journal, Number 7, August 1988: CVAX-Based Systems
    CVAX-based Systems Digital Technical Journal Digital Equipment Corporation umhcr 7 August I9R8 Managing Editor Richard W Beane Editor jane C. Blake Production Staff Produnion Editor- Helen L. Paucrson Designer- Charlo!!<: Bell Typographers- Jonathan !\·f. Uohy Margart:t Burdine lllustrawr- Dt:borah Keeley Advisory Board Samuel H. Fuller, Chairman Robert M. Glorioso John W McCredie Mahendra R. Patel F. Grant Saviers William D. Strecker Victor A. Vyssotsky The Digital Tecbnical jnumal is published by Digital Equipmt:nt Corporation. 77 Reed Road. Hudson. Massachuscus 01749. Changes of address should be sent to Digital E quipment Corporation. aut:ntion: List Maintenance. I 0 Forbes Road. Northboro. MA 015j2. Please includt: the address label with changes marked. Comments on the content of any paper are wclcomt:d. Write to the editor at Mail Stop 1-lLOl-.�/Kil at the published-by address. Comments can also be sent on the ENET to RDV�'X::OIAKE or on the ARPANET to BLA.K.E'X,RDVAX. DEC�)l)ECWRL. Copyright © 1988 Digital Equ ipment Corporation. Copying without fee is permiued providt:d that such copies are made for use in t:duc:uional institmions by faculty members and arc not distributed for commercial advamage. Abstracting with credit of Digital Equipment Corporation's authorship is pcrmiued. Requests for other copies for a fee may be made 10 Digital Press of Digital Equipmem Corporation. All rights reserved. The information in this journal is subject to change without notice and should not be construed as a com­ miunem by Digital E quipment Corporation. Digital Equipment Corporation assumt:s no responsibility for any errors that may appear in this document.
    [Show full text]
  • Computer Architectures an Overview
    Computer Architectures An Overview PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sat, 25 Feb 2012 22:35:32 UTC Contents Articles Microarchitecture 1 x86 7 PowerPC 23 IBM POWER 33 MIPS architecture 39 SPARC 57 ARM architecture 65 DEC Alpha 80 AlphaStation 92 AlphaServer 95 Very long instruction word 103 Instruction-level parallelism 107 Explicitly parallel instruction computing 108 References Article Sources and Contributors 111 Image Sources, Licenses and Contributors 113 Article Licenses License 114 Microarchitecture 1 Microarchitecture In computer engineering, microarchitecture (sometimes abbreviated to µarch or uarch), also called computer organization, is the way a given instruction set architecture (ISA) is implemented on a processor. A given ISA may be implemented with different microarchitectures.[1] Implementations might vary due to different goals of a given design or due to shifts in technology.[2] Computer architecture is the combination of microarchitecture and instruction set design. Relation to instruction set architecture The ISA is roughly the same as the programming model of a processor as seen by an assembly language programmer or compiler writer. The ISA includes the execution model, processor registers, address and data formats among other things. The Intel Core microarchitecture microarchitecture includes the constituent parts of the processor and how these interconnect and interoperate to implement the ISA. The microarchitecture of a machine is usually represented as (more or less detailed) diagrams that describe the interconnections of the various microarchitectural elements of the machine, which may be everything from single gates and registers, to complete arithmetic logic units (ALU)s and even larger elements.
    [Show full text]
  • PMAZ-AA Turbochannel SCSI Module Functional Specification
    -- -- PMAZ-AA TURBOchannel SCSI Module Functional Specification Revision 1.2 Workstation Systems Engineering Digital Equipment Corporation 100 Hamilton Avenue Palo Alto, CA 94301 August 27, 1990 August 1990 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibilty for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. Digital Equipment Coporation assumes no responsibility for the use or reliability of its software on equip- ment that is not supplied by Digital or its af®liated companies. Digital Equipment Corporation 1990. All Rights reserved Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: DEC DECnet DECstation DECsystem DECUS MicroVAX MicroVMS PDP TURBOchannel ULTRIX ULTRIX-32 UNIBUS VAX VAXBI VAXcluster VAXstation VMS VT i -- -- Blank Page ii -- -- Table of Contents 1. PMAZ-AA SCSI Module 2. Address Map 3. Interrupts 4. Power Estimates 5. External Interface 6. Functional Description 6.1. 53C94 ............................................................................................................................... 4 6.2. SCSI Buffer ..................................................................................................................... 4 6.3. DMA Address Register ..................................................................................................
    [Show full text]
  • Openvms I/O User's Reference Manual
    OpenVMS I/O User’s Reference Manual Order Number: AA–PV6SD–TK April 2001 This manual contains the information necessary to interface directly with the I/O device drivers supplied as part of the Compaq OpenVMS operating system. Several examples of programming techniques are included. This document does not contain information on I/O operations using the OpenVMS Record Management Services. Revision/Update Information: This manual supersedes the OpenVMS I/O User’s Reference Manual, OpenVMS Alpha Version 7.2, OpenVMS VAX Version 7.2 Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation Compaq, VAX, VMS, and the Compaq logo Registered in U.S. Patent and Trademark Office. OpenVMS and Tru64 are trademarks of Compaq Information Technologies Group, L.P in the United States and other countries. Microsoft, MS-DOS, Visual C++, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States and other countries. Intel, Intel Inside, and Pentium are trademarks of Intel Corporation in the United States and other countries. Motif, OSF/1, and UNIX are trademarks of The Open Group in the United States and other countries. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein.
    [Show full text]
  • Personal Decstation Series Technical Overview
    Personal DECstation Series Technical Overview • Personal DECstation 5000/20 • Personal DECstation 5000/25 TM Nameplate d i g i t a l WSMXS001 Worksystems Base Product Marketing Digital Equipment Corporation Palo Alto, California Version 1.0 December, 1991 Digital believes the information in this publication is accurate as of its publication date; such information is subject to change without notice. Digital is not responsible for any errors in the information given in this publication. The software described in this document is furnished under license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not sup- plied by Digital Equipment Corporation or its affiliated companies. The following are trademarks of Digital Equipment Corporation: DEC, DECstation, DEC Ada, DEC FUSE, DEC GKS, DEC PHIGS, DEC VUIT, DECnet, DECwindows, DECsystem, the DIGITAL Logo, PATHWORKS, PixelStamp, TURBOchannel, ULTRIX, VAX, VAXstation, VMS, and XUI. PostScript is a registered trademark of Adobe Systems, Inc. AT&T and System V are regis- tered trademarks of American Telephone and Telegraph Company. Apple and Macintosh are registered trademarks of Apple Computer, Inc. Network Computing System is a trademark of Hewlett-Packard Company. Intel is a trademark of Intel Corporation. PC/AT is a trademark and IBM and OS/2 are registered trademarks of International Business Machines Corporation. Lotus is a registered trademark of Lotus Development Corporation. MIPS is a registered trade- mark of MIPS Computer Systems, Inc. MS-DOS is a registered trademark of Microsoft Corpo- ration. NFS is a trademark of Sun Microsystems, Inc.
    [Show full text]