IRIX® 6.3 for O2™ Device Driver Programming Guide

Total Page:16

File Type:pdf, Size:1020Kb

IRIX® 6.3 for O2™ Device Driver Programming Guide IRIX® 6.3 for O2™ Device Driver Programming Guide Document Number 007-3443-002 CONTRIBUTORS Written by David Cortesi Illustrated by Dany Galgani Edited by Christina Cary Significant engineering contributions by (in alphabetical order): Rich Altmaier, Peter Baran, Brad Eacker, Ben Fathi, Steve Haehnichen, Bruce Johnson, Tom Lawrence, Greg Limes, Ben Mahjoor, Charles Marker, Dave Olson, Bhanu Prakash, James Putnam, Sarah Rosedahl, Brett Rudley, Deepinder Setia, Adam Sweeney, Michael Wang, Daniel Yau. Beta test contributions by: Jeff Stromberg of GeneSys St Peter’s Basilica image courtesy of ENEL SpA and InfoByte SpA. Disk Thrower image courtesy of Xavier Berenguer, Animatica. © 1998, Silicon Graphics, Inc.— All Rights Reserved The contents of this document may not be copied or duplicated in any form, in whole or in part, without the prior written permission of Silicon Graphics, Inc. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure of the technical data contained in this document by the Government is subject to restrictions as set forth in subdivision (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013 and/or in similar or successor clauses in the FAR, or in the DOD or NASA FAR Supplement. Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer is Silicon Graphics, Inc., 2011 N. Shoreline Blvd., Mountain View, CA 94043-1389. Silicon Graphics and the Silicon Graphics logo, and the terms CHALLENGE, Crimson, Indigo, Indigo2, Indigo2 Maximum Impact, Indy, IRIX, O2, Onyx, Origin2000, POWER CHALLENGE, POWER Channel, POWER Indigo2, and POWER Onyx are trademarks of Silicon Graphics, Inc. MIPS, R4000, R8000, and R10000 are trademarks of MIPS Technologies, Inc. Sun and SunOS are trademarks of Sun Microsystems, Inc. MC6800, MC68000, and VERSAbus are trademarks of Motorola Corporation. IBM is a trademark of International Business Machines. Intel is a trademark of Intel Corporation. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. X Window System is a trademark of Massachusetts Institute of Technology. IRIX® for O2™ Device Driver Programming Guide Document Number 007-3443-002 Contents List of Examples xvii List of Figures xix List of Tables xxi About This Guide xxv What You Need to Know xxv What This Guide Contains xxvi Other Sources of Information xxvii Developer Program xxvii Internet Resources xxvii Standards Documents xxviii Important Reference Pages xxviii Additional Reading xxix Conventions Used in This Guide xxx PART I IRIX Device Integration 1. Physical and Virtual Memory 3 Physical Address Space 4 Physical Device Addresses 4 Physical Memory Addresses 4 iii : CPU Access to Memory and Devices 5 CPU Modules 5 CPU Access to Memory 6 Processor Operating Modes 8 Virtual Address Mapping 8 Address Space Creation 9 Address Exceptions 9 CPU Access to Device Registers 10 Direct Memory Access 11 PIO Addresses and DMA Addresses 12 Cache Use and Cache Coherency 15 The 32-Bit Address Space 16 Segments of the 32-bit Address Space 16 Virtual Address Mapping 18 User Process Space—kuseg 18 Kernel Virtual Space—kseg2 19 Cached Physical Memory—kseg0 19 Uncached Physical Memory—kseg1 20 The 64-Bit Address Space 20 Segments of the 64-Bit Address Space 20 Compatibility of 32-Bit and 64-Bit Spaces 22 Virtual Address Mapping 22 User Process Space—xkuseg 23 Supervisor Mode Space—xksseg 23 Kernel Virtual Space—xkseg 24 Cache-Controlled Physical Memory—xkphys 24 Device Driver Use of Memory 26 Allowing for 64-Bit Mode 26 Memory Use in User-Level Drivers 27 Memory Use in Kernel-Level Drivers 28 iv : 2. Device Configuration 31 Hardware Inventory 31 Using the Hardware Inventory 32 Creating an Inventory Entry 34 Device Special Files 34 Device Representation 35 Defining Device Names 37 Configuration Files 39 Master Configuration Database 40 System Configuration Files 41 System Tuning Parameters 41 X Display Manager Configuration 41 3. Device Control Software 43 User-Level Device Control 43 EISA Mapping Support 44 VME Mapping Support 44 PCI Mapping Support 45 User-Level DMA From the VME Bus 45 User-Level Control of SCSI Devices 45 Managing External Interrupts 46 User-Level Interrupt Management 46 Memory-Mapped Access to Serial Ports 47 Kernel-Level Device Control 47 Kinds of Kernel-Level Drivers 48 Typical Driver Operations 48 Upper and Lower Halves 56 Layered Drivers 58 Combined Block and Character Drivers 58 Drivers for Multiprocessors 59 Loadable Drivers 59 v : PART II Device Control From Process Space 4. User-Level Access to Devices 63 VME Programmed I/O 64 Mapping a VME Device Into Process Address Space 64 VME PIO Access 67 VME PIO Bandwidth 68 EISA Programmed I/O 68 Mapping an EISA Device Into Memory 69 EISA PIO Bandwidth 71 VME User-Level DMA 72 Using the udmalib Functions 73 Advantages of User DMA 75 DMA Engine Bandwidth 75 Example User DMA Function 76 PCI Programmed I/O 78 Mapping a PCI Device Into Process Address Space 78 5. User-Level Access to SCSI Devices 81 Overview of the dsreq Driver 82 Generic SCSI Device Special Files 82 Major and Minor Device Numbers in /dev/scsi 83 Form of Filenames in /dev/scsi 83 Creating Additional Names in /dev/scsi 84 Relationship to Other Device Special Files 85 The dsreq Structure 85 Values for ds_flags 87 Data Transfer Options 89 Return Codes and Status Values 89 Testing the Driver Configuration 92 Using the Special DS_RESET and DS_ABORT Calls 93 Using DS_ABORT 93 Using DS_RESET 94 vi : Using dslib Functions 94 dslib Functions 94 Using dsopen() and dsclose() 95 Issuing a Request With doscsireq() 97 SCSI Utility Functions 97 Using Command-Building Functions 100 Example dslib Program 107 6. Control of External Interrupts 117 External Interrupts in Challenge and Onyx Systems 118 Generating Outgoing Signals 118 Receiving Incoming External Interrupts 119 7. User-Level Interrupts 125 Overview of ULI 125 The User Level Interrupt Handler 126 Restrictions on the ULI Handler 126 Planning for Concurrency 127 Using Multiple Devices 128 Setting Up 128 Opening the Device Special File 128 Locking the Program Address Space 129 Registering the Interrupt Handler 130 Interacting With the Handler 131 Sample Program 133 PART III Kernel-Level Drivers 8. Structure of a Kernel-Level Driver 139 Summary of Driver Structure 140 Entry Point Naming and lboot 140 Entry Point Summary 142 vii : Driver Flag Constant 145 Flag D_MP 145 Flag D_WBACK 146 Flag D_MT 146 Flag D_OLD 146 Initialization Entry Points 147 When Initialization Is Performed 147 Entry Point init() 148 Entry Point edtinit() 148 Entry Point start() 149 Open and Close Entry Points 150 Entry Point open() 150 Entry Point close() 153 Control Entry Point 154 Choosing the Command Numbers 155 Supporting 32-Bit and 64-Bit Callers 155 User Return Value 155 Data Transfer Entry Points 155 Entry Points read() and write() 155 Entry Point strategy() 157 Poll Entry Point 158 Use and Operation of poll(2) 159 Entry Point poll() 160 Memory Map Entry Points 161 Concepts and Use of mmap() 162 Entry Point map() 163 Entry Point mmap() 165 Entry Point unmap() 166 Interrupt Entry Point 167 Associating Interrupt to Driver 167 Interrupt Handler Operation 167 viii : Support Entry Points 170 Entry Point unload() 170 Entry Point halt() 171 Entry Point size() 172 Entry Point print() 172 Handling 32-Bit and 64-Bit Execution Models 173 Planning for Multiprocessor Use 174 The Multiprocessor Environment 174 Synchronizing Within Upper-Half Functions 176 Coordinating Upper-Half and Interrupt Entry Points 177 Converting a Uniprocessor Driver 178 Example Conversion Problem 179 9. Device Driver/Kernel Interface 181 Important Data Types 182 The Device Number Types 182 Structure uio_t 184 Structure buf_t 185 Lock and Semaphore Types 187 Important Header Files 188 Memory Allocation 189 General-Purpose Allocation 190 Allocating Objects of Specific Kinds 191 Suballocation Functions 193 Transferring Data 194 General Data Transfer 195 Transferring Data Through a uio_t Object 197 Managing Virtual and Physical Addresses 198 Testing Device Physical Addresses 198 Managing Mapped Memory 199 Working With Page and Sector Units 200 Setting Up a DMA Transfer 201 User Process Administration 205 Sending a Process Signal 206 ix : Waiting and Mutual Exclusion 206 Mutual Exclusion Compared to Waiting 207 Basic Locks 208 Long-Term Locks 210 Reader/Writer Locks 213 Priority Level Functions 215 Waiting for Time to Pass 216 Waiting for Memory to Become Available 218 Waiting for Block I/O to Complete 219 Waiting for a General Event 221 Semaphores 224 10. Building and Installing a Driver 227 Defining Device Numbers 228 Selecting a Major Number 228 Selecting Minor Numbers 229 Defining Device Special Files 229 Static Definition of Device Special Files 229 Dynamic Definition of Device Special Files 229 Compiling and Linking 230 Using /var/sysgen/Makefile.kernio 230 Compiler Variables 231 Compile Options, 32-Bit Kernel 232 Compile Options, 64-Bit Kernel 233 Configuring a Nonloadable Driver 234 How Names Are Used in Configuration 234 Placing the Object File in /var/sysgen/boot 235 Describing the Driver in /var/sysgen/master.d 235 Configuring a Kernel 238 Generating a Kernel 239 x : Configuring a Loadable Driver 239 Public Global Variables 239 Compile Options for Loadable Drivers 240 Master File for Loadable Drivers 240 Registration 241 Loading 241 Unloading 242 Configuring for a Dynamic Major Number 243 11. Testing and Debugging a Driver 245 Preparing the System for Debugging 245 Placing symmon
Recommended publications
  • Using Restricted Transactional Memory to Build a Scalable In-Memory Database
    Using Restricted Transactional Memory to Build a Scalable In-Memory Database Zhaoguo Wang†, Hao Qian‡, Jinyang Li§, Haibo Chen‡ † School of Computer Science, Fudan University ‡ Institute of Parallel and Distributed Systems, Shanghai Jiao Tong University § Department of Computer Science, New York University Abstract However, the correctness of the resulting code is complex to reason about and relies on the processor’s (increasingly The recent availability of Intel Haswell processors marks the complex) memory model. transition of hardware transactional memory from research Recently, Intel has shipped its 4th-generation Haswell toys to mainstream reality. DBX is an in-memory database processor with support for Hardware Transactional Mem- that uses Intel’s restricted transactional memory (RTM) to ory [16]. This opens up a third possibility to scaling multi- achieve high performance and good scalability across multi- core software. Instead of relying on fine-grained locking core machines. The main limitation (and also key to practi- and atomic operations, one can synchronize using hardware cality) of RTM is its constrained working set size: an RTM transactions, which offer a programming model that is ar- region that reads or writes too much data will always be guably even more straightforward than mutual exclusion. aborted. The design of DBX addresses this challenge in sev- The promise is that the resulting implementation is much eral ways. First, DBX builds a database transaction layer on simpler and easier-to-understand while still retaining the top of an underlying shared-memory store. The two layers performance benefits of fine-grained locking. use separate RTM regions to synchronize shared memory Does hardware transactional memory actually deliver its access.
    [Show full text]
  • Using the GNU Compiler Collection (GCC)
    Using the GNU Compiler Collection (GCC) Using the GNU Compiler Collection by Richard M. Stallman and the GCC Developer Community Last updated 23 May 2004 for GCC 3.4.6 For GCC Version 3.4.6 Published by: GNU Press Website: www.gnupress.org a division of the General: [email protected] Free Software Foundation Orders: [email protected] 59 Temple Place Suite 330 Tel 617-542-5942 Boston, MA 02111-1307 USA Fax 617-542-2652 Last printed October 2003 for GCC 3.3.1. Printed copies are available for $45 each. Copyright c 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being \GNU General Public License" and \Funding Free Software", the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled \GNU Free Documentation License". (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Short Contents Introduction ...................................... 1 1 Programming Languages Supported by GCC ............ 3 2 Language Standards Supported by GCC ............... 5 3 GCC Command Options .........................
    [Show full text]
  • A Ballista Retrospective
    Software Robustness Testing A Ballista Retrospective Phil Koopman [email protected] http://ballista.org With contributions from: Dan Siewiorek, Kobey DeVale John DeVale, Kim Fernsler, Dave Guttendorf, Nathan Kropp, Jiantao Pan, Charles Shelton, Ying Shi Institute for Complex Engineered Systems Overview Introduction • APIs aren’t robust (and people act as if they don’t want them to be robust!) Top 4 Reasons people give for ignoring robustness improvement • “My API is already robust, especially for easy problems” (it’s probably not) • “Robustness is impractical” (it is practical) • “Robust code will be too slow” (it need not be) • “We already know how to do it, thank you very much” (perhaps they don’t) Conclusions • The big future problem for “near-stationary” robustness isn’t technology -- it is awareness & training 2 Ballista Software Testing Overview SPECIFIED INPUT RESPONSE BEHAVIOR SPACE SPACE ROBUST SHOULD VAL I D OPERATION WORK INPUTS MO DULE REPRODUCIBLE UNDEFINED UNDER FAILURE TEST SHOULD INVALID INPUTS UNREPRODUCIBLE RETURN FAILURE ERROR Abstracts testing to the API/Data type level • Most test cases are exceptional • Test cases based on best-practice SW testing methodology 3 Ballista: Test Generation (fine grain testing) Tests developed per data type/subtype; scalable via composition 4 Initial Results: Most APIs Weren’t Robust Unix & Windows systems had poor robustness scores: • 24% to 48% of intentionally exceptional Unix tests yielded non-robust results • Found simple “system killer” programs in Unix, Win 95/98/ME, and WinCE
    [Show full text]
  • Introduction to UNIX What Is UNIX? Why UNIX? Brief History of UNIX Early UNIX History UNIX Variants
    What is UNIX? A modern computer operating system Introduction to UNIX Operating system: “a program that acts as an intermediary between a user of the computer and the computer hardware” CS 2204 Software that manages your computer’s resources (files, programs, disks, network, …) Class meeting 1 e.g. Windows, MacOS Modern: features for stability, flexibility, multiple users and programs, configurability, etc. *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003. (C) Doug Bowman, Virginia Tech, 2001- 2 Why UNIX? Brief history of UNIX Used in many scientific and industrial settings Ken Thompson & Dennis Richie Huge number of free and well-written originally developed the earliest software programs versions of UNIX at Bell Labs for Open-source OS internal use in 1970s Internet servers and services run on UNIX Borrowed best ideas from other Oss Largely hardware-independent Meant for programmers and computer Based on standards experts Meant to run on “mini computers” (C) Doug Bowman, Virginia Tech, 2001- 3 (C) Doug Bowman, Virginia Tech, 2001- 4 Early UNIX History UNIX variants Thompson also rewrote the operating system Two main threads of development: in high level language of his own design Berkeley software distribution (BSD) which he called B. Unix System Laboratories System V Sun: SunOS, Solaris The B language lacked many features and Ritchie decided to design a successor to B GNU: Linux (many flavors) which he called C. SGI: Irix They then rewrote UNIX in the C FreeBSD programming language to aid in portability. Hewlett-Packard: HP-UX Apple: OS X (Darwin) … (C) Doug Bowman, Virginia Tech, 2001- 5 (C) Doug Bowman, Virginia Tech, 2001- 6 1 Layers in the UNIX System UNIX Structure User Interface The kernel is the core of the UNIX Library Interface Users system, controlling the system Standard Utility Programs hardware and performing various low- (shell, editors, compilers, etc.) System Interface calls User Mode level functions.
    [Show full text]
  • Absolute BSD—The Ultimate Guide to Freebsd Table of Contents Absolute BSD—The Ultimate Guide to Freebsd
    Absolute BSD—The Ultimate Guide to FreeBSD Table of Contents Absolute BSD—The Ultimate Guide to FreeBSD............................................................................1 Dedication..........................................................................................................................................3 Foreword............................................................................................................................................4 Introduction........................................................................................................................................5 What Is FreeBSD?...................................................................................................................5 How Did FreeBSD Get Here?..................................................................................................5 The BSD License: BSD Goes Public.......................................................................................6 The Birth of Modern FreeBSD.................................................................................................6 FreeBSD Development............................................................................................................7 Committers.........................................................................................................................7 Contributors........................................................................................................................8 Users..................................................................................................................................8
    [Show full text]
  • Oracle Solaris Studio 12.3 Debugging a Program With
    Oracle® Solaris Studio 12.3: Debugging a ProgramWith dbx Part No: E21993 December 2011 Copyright © 1992, 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms setforth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
    [Show full text]
  • Debugging a Program with Dbx
    Debugging a Program With dbx Sun™ Studio 11 Sun Microsystems, Inc. www.sun.com Part No 819-3683-10 November 2005, Revision A Submit comments about this document at: http://www.sun.com/hwdocs/feedback Copyright © 2005 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. Use is subject to license terms. This distribution may include materials developed by third parties. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, Java, and JavaHelp are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon architecture developed by Sun Microsystems, Inc. This product is covered and controlled by U.S. Export Control laws and may be subject to the export or import laws in other countries. Nuclear, missile, chemical biological weapons or nuclear maritime end uses or end users, whether direct or indirect, are strictly prohibited. Export or reexport to countries subject to U.S. embargo or to entities identified on U.S. export exclusion lists, including, but not limited to, the denied persons and specially designated nationals lists is strictly prohibited.
    [Show full text]
  • Introduction
    CS307 Operating Systems Introduction Fan Wu Department of Computer Science and Engineering Shanghai Jiao Tong University Spring 2020 Operating Systems Operating Systems 2 Operating Systems UNIX-family: BSD(Berkeley Software Distribution), System-V, GNU/Linux, MINIX, Nachos, OS X, iOS BSD-family: FreeBSD, NetBSD, OpenBSD System-V-family: AIX, HP-UX, IRIX, Solaris Linux-family: Red Hat, Debian, Ubuntu, Fedora, openSUSE, Linux Mint, Google's Android, WebOS, Meego MS-DOS, Microsoft Windows, Windows Mobile, Win-CE, WP8 AmigaOS Symbian, MeeGo Google Chrome OS OS/2 XrossMediaBar(XMB) for PS3, Orbis OS for PS4 Input Output System for Wii Tiny-OS, LynxOS, QNX, VxWorks Operating Systems 3 Four Components of a Computer System People, machines, other computers Application programs define the ways in which theSystem system programs resources are arecomputer used to software solve the computingdesigned to problems operate theof thecomputer users hardware and toControls provide and a platformcoordinates for runninguse of hardware application among programsvarious applications and users provides basic computing resources Operating Systems 4 Computer System Structure Hardware – provides basic computing resources CPU, memory, I/O devices Operating system – Controls and coordinates use of hardware among various applications and users System programs – are computer software designed to operate the computer hardware and to provide a platform for running application programs BIOS and device drivers Application programs – define the ways in
    [Show full text]
  • A Short User Manual for Dbx
    A Short User Manual for dbx \dbx" is the name of the debugger that is available for use on many Unix systems. This document is intended to list the most common dbx commands and briefly explain how to use them. It is not a complete description of dbx but should be a sufficient reference to get started. For a more detailed description or to find out about other commands and options, execute the command % man dbx or from within dbx use the 'help' command (recommended). Subjects covered below: let (dbx) be the prompt while in dbx mode: a) Compiling your code for use with the debugger [ cc with -g flag] b) Starting the debugger [ \%dbx executable ] c) Getting help while using the debugger [ (dbx) help ] d) Running your program in the debugger [ (dbx) run ] e) Setting breakpoints in the program [ (dbx) stop ] f) Listing the breakpoints that are set [ (dbx) status ] g) Removing a breakpoint [ (dbx) delete ] h) Stepping through the program [ (dbx) step, (dbx) next ] i) Jumping ahead to the next breakpoint [ (dbx) cont ] j) Examining the values of variables [ (dbx) print ] k) Listing a portion of the source code [ (dbx) list ] l) Leaving the debugger [ (dbx) quit ] To use dbx to debug your C programs you need to follows the procedure: 1. Compiling your code for use with the debugger: You must use the -g flag when compiling your code. For example: % cc -g myfile.c will create an a.out executable suitable for dbx. 2. Starting the debugger: Give the 'dbx' command along with the name of the exe- cutable you wish to examine.
    [Show full text]
  • Debugging a Program with Dbx
    Debugging a Program With dbx A Sun Microsystems, Inc. Business 901 San Antonio Road Palo Alto, , CA 94303-4900 Part No: 805-4948 Revision A, February 1999 USA 650 960-1300 fax 650 969-9131 Debugging a Program With dbx Part No: 805-4948 Revision A, February 1999 Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303-4900 U.S.A. All rights reserved. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Portions of this product may be derived from the UNIX® system, licensed from Novell, Inc., and from the Berkeley 4.3 BSD system, licensed from the University of California. UNIX is a registered trademark in the United States and in other countries and is exclusively licensed by X/Open Company Ltd. Third-party software, including font technology in this product, is protected by copyright and licensed from Sun’s suppliers. RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions of FAR 52.227-14(g)(2)(6/87) and FAR 52.227-19(6/87), or DFAR 252.227-7015(b)(6/95) and DFAR 227.7202-3(a). Sun, Sun Microsystems, the Sun logo, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and in other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
    [Show full text]
  • Google Announces Chrome OS, for Release Mid
    Google Announces Chrome OS, For Release Mid-... http://tech.slashdot.org/story/09/07/08/0953238/... Slashdot Stories Slash Boxes Comments Search Deals new SlashTV Jobs Newsletter Submit Login Join Slashdot81 Full 19 stories Abbreviated can be 0listened Hidden to in audio form via an RSS feed,/Sea as read by our own robotic overlord. Score: 5 4 3 2 Nickname: 1 0 -1Password: 989 More Login Public Terminal Nickname:Log In Forgot your password? Sign in with Password: Google Public Terminal Twitter Log In Forgot yourFacebook password? Close LinkedIn Close Close Stories Submissions Popular Blog Slashdot Build Ask Slashdot Book Reviews Games Idle YRO Technology Cloud Hardware Linux Management Mobile Science Security Storage 1 of 31 03/01/15 17:19 Google Announces Chrome OS, For Release Mid-... http://tech.slashdot.org/story/09/07/08/0953238/... Announcing: Slashdot Deals - Explore geek apps, games, gadgets and more. (what is this?) Close, and don't show me this again Google Announces Chrome OS, For Release Mid-2010 1089 Posted by timothy on Wednesday July 08, 2009 @07:14AM from the bring-on-the-shiny dept. Zaiff Urgulbunger writes "After years of speculation, Google has announced Google Chrome OS, which should be available mid-2010. Initially targeting netbooks, its main selling points are speed, simplicity and security — which kind of implies that the current No.1 OS doesn't deliver in these areas! The Chrome OS will run on both x86 and ARM architectures, uses a Linux kernel with a new windowing system. According to Google, 'For application developers, the web is the platform.
    [Show full text]
  • SDE 3.0.1 System Requirements
    SDE 3.0.1 System Requirements This PDF contains system requirements information, including hardware requirements, best performance configurations, and limitations, for SDE 3.0.1. Compaq/Digital Tru64 UNIX V4.0b o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 Compaq/Digital Tru64 UNIX V4.0c o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 Compaq/Digital Tru64 UNIX V4.0d o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 HP HP-UX 10.20 (700 series, 8x7 series) o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 o Sybase SQL Server 11.0.2 HP HP-UX 11.0 (700 series, 8x7 series) o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 IBM AIX 4.1.5.0 o IBM DB2 Common Server 2.1.2 o IBM DB2 Universal Database (UDB) 5.0 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 o Sybase SQL Server 11.0.2 IBM AIX 4.2.1.0 o IBM DB2 Universal Database (UDB) 5.0 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 IBM AIX 4.3.0.0 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 PC-Intel Windows NT 4.0 o Microsoft SQL Server 6.5 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 SGI IRIX 6.2 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 o Sybase SQL Server 11.0.2 SGI IRIX 6.3 o Oracle 8 (32 bit) Enterprise
    [Show full text]