DOCSLIB.ORG

DRI User Guide VA Linux Systems, Inc

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
DRI User Guide VA Linux Systems, Inc DRI User Guide VA Linux Systems, Inc. Professional Services - Graphics. 15 June 2001 1. Preamble 1.1 Copyright Copyright © 2000-2001 by VALinux Systems, Inc. All Rights Reserved. Permission is granted to make and distribute verbatim copies of this document provided the copyright notice and this permission notice are preserved on all copies. 1.2 Trademarks OpenGL is a registered trademark and SGI is a trademark of Silicon Graphics, Inc. Unix is a reg- istered trademark of The Open Group. The `X' device and X Window System aretrademarks of The Open Group. XFree86 is a registered trademark of The XFree86 Project, Inc. Linux is a regis- tered trademark of Linus Torvalds. Intel is a registered trademark of Intel Corporation. 3Dlabs, GLINT,and Oxygen areeither registered trademarks or trademarks of 3Dlabs Inc. Ltd. 3dfx, Voodoo3, Voodoo4, and Voodoo5 areregistered trademarks of 3dfx Interactive, Incorporated. Matrox is a registered trademark of Matrox Electronic Systems Ltd. ATIRage and Radeon are registered trademarks of ATI Technologies, Inc. All other trademarks mentioned arethe property of their respective owners. 2. Introduction With XFree86 4.x and the Direct Rendering Interface (DRI), hardwareaccelerated 3D graphics can be considered a standardfeatureonLinux workstations. Support for other operating systems, such as FreeBSD, is underway. This document describes how to use the DRI system and troubleshoot problems which may occur. Readers should have a basic understanding of Linux, X and OpenGL. See the resources section at the end for moredocumentation and softwaredownloads. This document does not cover compilation or installation of XFree86 4.x. It is assumed that you've already installed a Linux distribution which includes XFree86 4.x or that you'reanexperi- enced Linux developer who has compiled the DRI for himself. DRI download, compilation and installation instructions can be found at http://dri.sourceforge.net/DRIcompile.html Edits, corrections and updates to this document may be mailed to <brian@tungstengrah- pics.com>. 3. Supported Architectures & Hardware DRI User Guide 1 DRI User Guide 2 3.1 CPU Architectures The architectures currently supported by the DRI have grown from the initial Intel i386 systems to now include the Alpha Processor and the Sun SPARC machines. Intel's SSE (a.k.a. Katmai) instructions areused in optimized vertex transformation functions in Mesa-based drivers. This requires a recent Linux kernel both at compile and runtime. See the DRI Compile Guide for compile-time requirements. At runtime a check is made to determine if the CPU can execute SSE instructions. They'redisabled otherwise. AMD's 3DNow! instructions arealso used in optimized vertex transformation functions in the Mesa-based DRI drivers. 3DNow! is supported in most versions of Linux. Like the SSE opti- mizations, a runtime check is made to determine if the CPU can execute 3DNow! instructions. Alpha-based systems can use Compaq's optimized math library for improved 3D performance. See the DRI Compilation Guide for details. 3.2 Graphics Hardware XFree86 4.2 (or later versions) includes 3D acceleration for the following graphics hardware: • 3dfx, supported on Intel x86, AMD and Alpha: • Voodoo5 5500 • Voodoo4 4500 • Voodoo3 3500 TV • Voodoo3 3000 AGP • Voodoo3 3000 PCI • Voodoo3 2000 AGP • Voodoo3 2000 PCI • Voodoo Banshee • Velocity 100/200 Thereare many configurations of 3dfx cards on the market. Not all have been tested. • Matrox, supported on Intel x86 and AMD: • Matrox G200 • Matrox G400 • Intel i810/i815/i830 (motherboardchipsets) • i810 • i810-dc100 • i810e • i815 • i830 • ATIRage 128, supported on Intel x86, AMD and Alpha: • Rage Fury • Rage Magnum DRI User Guide 3 • XPERT2000 • XPERT128 • XPERT99 • All-in-Wonder 128 • Rage 128 PCI (Alpha-based systems) Note that both PCI and AGP versions of Rage 128 based cards aresupported at this time. • ATIRadeon, supported on Intel x86, AMD and Alpha: • Radeon SDR AGP • Radeon DDR AGP • Radeon 32MB SDR PCI (Alpha-based systems) • Radeon 7000, M6 (RV100) • Radeon 7200 (R100) • Radeon 7500, M7 (RV200) • Radeon 8500, 9100 (R200) • Radeon 9000, M9 (RV250) • 3Dlabs, supported on Intel x86 and AMD: • Oxygen GMX 2000 (MX/Gamma based). Note: this driver is no longer being actively developed. Support for other hardwareisunderway. Most of the DRI development work is funded by con- tracts with IHVs. These contracts often prevent us from announcing drivers beforethey're released. Queries about upcoming drivers may not be answerable. 4. Prerequisite Software • The DRI is available in XFree86 4.0 and later. • Some hardwaredrivers requirespecific versions of the Linux kernel for AGP support, etc. See section 10 for specifics. • You DO NOT need to install Mesa separately. The parts of Mesa needed for hardware acceleration arealready in the XFree86/DRI project. 5. Kernel Modules 3D hardwareacceleration requires a DRI kernel module that’s specific to your graphics hardware. The DRI kernel module version must exactly match your running kernel version. Since thereare so many versions of the kernel, it's difficult to provide precompiled kernel modules. While the Linux source tree includes the DRI kernel module sources, the latest DRI kernel sources will be found in the DRI source tree. See the DRI Compilation Guide for information on compiling the DRI kernel modules. XFree86 4.0.1 added automatic kernel module loading to the X server. On Linux, the X server uses modprobe to load kernel modules. In Linux 2.4.x the DRM kernel modules should be kept in /lib/modules/2.4.x/kernel/drivers/char/drm/ for automatic loading to work. Optionally,DRM kernel modules can be loaded manually with insmod prior to starting the X DRI User Guide 4 server. Youcan verify that the kernel module was installed with lsmod, checking the X server startup log, and checking that /proc/dri/0 exists. 6. XF86Config file The XFree86 configuration file is usually found in /etc/X11/XF86Config.This section describes the parts which must be specially set for the DRI. First, the XF86Config file must load the GLX and DRI modules: Section "Module" ... #This loads the GLX module Load "glx" #This loads the DRI module Load "dri" EndSection Next, the DRI section can be used to restrict access to direct rendering. A client can only use direct rendering if it has permission to open the /dev/dri/card? file(s). The permissions on these DRI device files is controlled by the "DRI" section in the XF86Config file. If you want all of the users on your system to be able to use direct-rendering, then use a simple DRI section like this: Section "DRI" Mode 0666 EndSection This section will allow any user with a current connection to the X server to use direct rendering. If you want to restrict the use of direct-rendering to a certain group of users, then create a group for those users by editing the /etc/group file on your system. For example, you may want to create a group called xf86dri and place two users (e.g., fred and jane)inthat group. Todo that, you might add the following line to /etc/group: xf86dri:x:8000:fred,jane Youhave to be careful that the group id (8000 in this example) is unique. Then you would use the following DRI section: Section "DRI" Group "xf86dri" Mode 0660 EndSection This would limit access to direct-rendering to those users in the xf86dri group (fred and jane in this example). When other users tried to use direct rendering, they would fall back to unaccel- erated indirect rendering. [Note that thereisaknown bug in XFree86 4.0 that prevents some changes to the DRI section from taking effect. Until this bug is fixed, if you change the DRI section, please also remove the /dev/dri directory with the rm -rf /dev/dri command.] Finally,the XF86Config file needs Device and Screen sections specific to your hardware. Look in section 10: Hardware-Specific Information and Troubleshooting for details. DRI User Guide 5 7. Memoryusage Using the 3D features of a graphics cardrequires morememory than when it's just used as a 2D device. Double buffering, depth buffering, stencil buffers, textures, etc. all requireextra graphics memory. These features may requirefour times the memory used for a simple 2D display. If your graphics carddoesn't have a lot of memory (less than 16MB, for example), you may have to reduce your screen size and/or color depth in order to use 3D features. Reducing the screen resolution will also leave morespace for textureimages, possibly improving 3D performance. If, for example, you play Quake3 at 1024x768 but start your display at 1600x1200 you might con- sider restarting X at 1024x768 in order to maximize your texturememory space. The documentation included with your cardshould have information about maximum screen size when using 3D. 8. Using 3D Acceleration This section describes how to link your application with libGL.so and verify that you areinfact using 3D acceleration. 8.1 libGL.so Your OpenGL program must link with the libGL.so.1.2 library provided by XFree86. The libGL.so.1.2 library contains a GLX protocol encoder for indirect/remote rendering and DRI code for accessing hardwaredrivers. In particular,besureyou'renot using libGL.so from another source such as Mesa or the Utah GLX project. Unless it was built in a special way,the libGL.so library does not contain any 3D hardwaredriver code. Instead, libGL.so dynamically loads the appropriate 3D driver during initialization. Most simple OpenGL programs also use the GLUT and GLU libraries. Asource for these libraries is listed in the Resources section below. 8.2 Compiling and linking an OpenGL program Asimple GLUT/OpenGL program may be compiled and linked as follows: gcc program.c -I/usr/local/include -L/usr/local/lib -L/usr/X11R6/lib -lglut -lGLU -lGL -o program The -I option is used to specify wherethe GL/glut.h (and possibly the GL/gl.h and GL/glu.h) header file may be found.
Load more

Recommended publications
  • Release Notes for X11R6.8.2 the X.Orgfoundation the Xfree86 Project, Inc
    Release Notes for X11R6.8.2 The X.OrgFoundation The XFree86 Project, Inc. 9February 2005 Abstract These release notes contains information about features and their status in the X.Org Foundation X11R6.8.2 release. It is based on the XFree86 4.4RC2 RELNOTES docu- ment published by The XFree86™ Project, Inc. Thereare significant updates and dif- ferences in the X.Orgrelease as noted below. 1. Introduction to the X11R6.8.2 Release The release numbering is based on the original MIT X numbering system. X11refers to the ver- sion of the network protocol that the X Window system is based on: Version 11was first released in 1988 and has been stable for 15 years, with only upwardcompatible additions to the coreX protocol, a recordofstability envied in computing. Formal releases of X started with X version 9 from MIT;the first commercial X products werebased on X version 10. The MIT X Consortium and its successors, the X Consortium, the Open Group X Project Team, and the X.OrgGroup released versions X11R3 through X11R6.6, beforethe founding of the X.OrgFoundation. Therewill be futuremaintenance releases in the X11R6.8.x series. However,efforts arewell underway to split the X distribution into its modular components to allow for easier maintenance and independent updates. We expect a transitional period while both X11R6.8 releases arebeing fielded and the modular release completed and deployed while both will be available as different consumers of X technology have different constraints on deployment. Wehave not yet decided how the modular X releases will be numbered. We encourage you to submit bug fixes and enhancements to bugzilla.freedesktop.orgusing the xorgproduct, and discussions on this server take place on <[email protected]>.
    [Show full text]
  • Contributors
    gems_ch001_fm.qxp 2/23/2004 11:13 AM Page xxxiii Contributors Curtis Beeson, NVIDIA Curtis Beeson moved from SGI to NVIDIA’s Demo Team more than five years ago; he focuses on the art path, the object model, and the DirectX ren- derer of the NVIDIA demo engine. He began working in 3D while attending Carnegie Mellon University, where he generated environments for playback on head-mounted displays at resolutions that left users legally blind. Curtis spe- cializes in the art path and object model of the NVIDIA Demo Team’s scene- graph API—while fighting the urge to succumb to the dark offerings of management in marketing. Kevin Bjorke, NVIDIA Kevin Bjorke works in the Developer Technology group developing and promoting next-generation art tools and entertainments, with a particular eye toward the possibilities inherent in programmable shading hardware. Before joining NVIDIA, he worked extensively in the film, television, and game industries, supervising development and imagery for Final Fantasy: The Spirits Within and The Animatrix; performing numerous technical director and layout animation duties on Toy Story and A Bug’s Life; developing games on just about every commercial platform; producing theme park rides; animating too many TV com- mercials; and booking daytime TV talk shows. He attended several colleges, eventually graduat- ing from the California Institute of the Arts film school. Kevin has been a regular speaker at SIGGRAPH, GDC, and similar events for the past decade. Rod Bogart, Industrial Light & Magic Rod Bogart came to Industrial Light & Magic (ILM) in 1995 after spend- ing three years as a software engineer at Pacific Data Images.
    [Show full text]
  • Reviving the Development of Openchrome
    Reviving the Development of OpenChrome Kevin Brace OpenChrome Project Maintainer / Developer XDC2017 September 21st, 2017 Outline ● About Me ● My Personal Story Behind OpenChrome ● Background on VIA Chrome Hardware ● The History of OpenChrome Project ● Past Releases ● Observations about Standby Resume ● Developmental Philosophy ● Developmental Challenges ● Strategies for Further Development ● Future Plans 09/21/2017 XDC2017 2 About Me ● EE (Electrical Engineering) background (B.S.E.E.) who specialized in digital design / computer architecture in college (pretty much the only undergraduate student “still” doing this stuff where I attended college) ● Graduated recently ● First time conference presenter ● Very experienced with Xilinx FPGA (Spartan-II through 7 Series FPGA) ● Fluent in Verilog / VHDL design and verification ● Interest / design experience with external communication interfaces (PCI / PCIe) and external memory interfaces (SDRAM / DDR3 SDRAM) ● Developed a simple DMA engine for PCI I/F validation w/Windows WDM (Windows Driver Model) kernel device driver ● Almost all the knowledge I have is self taught (university engineering classes were not very useful) 09/21/2017 XDC2017 3 Motivations Behind My Work ● General difficulty in obtaining meaningful employment in the digital hardware design field (too many students in the field, difficulty obtaining internship, etc.) ● Collects and repairs abandoned computer hardware (It’s like rescuing puppies!) ● Owns 100+ desktop computers and 20+ laptop computers (mostly abandoned old stuff I
    [Show full text]
  • Matrox Graphics Card Driver Download MATROX G200 GRAPHICS CARD WINDOWS 8 X64 DRIVER DOWNLOAD
    matrox graphics card driver download MATROX G200 GRAPHICS CARD WINDOWS 8 X64 DRIVER DOWNLOAD. On this is needed just for any other projects Wikimedia Commons. MATROX GRAPHICS MILLENNIUM PCI DRIVER FOR WINDOWS - Drivers in this section are previously released drivers and should be used for trouble shooting purposes only. Games, and expansion needed to date. The standard package contains, Matrox G200 VGA BMC. It was initially advertised has having partial D3D9 capabilities. Other configurations include composite video card on the card works fine. For download driver Matrox Video card/adapter G200 you must select some parameters, such. Z-fighting may also be a problem and enabling bit z- buffer can help this. G's biggest problem was initially advertised has having partial D3D9 capabilities. Driver Notes. DL380p G8 G200. MATROX GRAPHICS MILLENNIUM PCI DRIVER DOWNLOAD - However, contrary to the video mode's name, G does not support full DVD decoding hardware acceleration. Other configurations include composite video matrox g200 mms graphics card ability and onboard TV tuner, making the Matrox G MMS. MATROX MILLENIUM G200 AGP DRIVER DOWNLOAD - The chip also supported features such as trilinear mip-map filtering and anti-aliasing though this was rarely used. The Software is copyrighted and protected by the laws of the United States and other countries, and international treaty provisions. PowerEdge M620 blade server is an ideal blend of density, performance, efficiency and scalability. Italian blogger, publisher, game dev and social person. MATROX G200 Sign in multi-display with 4. Supermicro X9SCM-F motherboard is using a dedicated graphic from Matrox G200eW. The newest software for your Matrox G200 MMS.
    [Show full text]
  • Technical Reference Manual Hp Business Pc Technology
    hp business pc technology hp vectra xe310 hp vectra xe320 hp vectra vl400 hp vectra vl410 hp vectra vl420 hp e-pc c10/s10 hp e-pc 40 hp e-pc 42 technical reference manual hp business pcs www.hp.com/go/vectrasupport www.hp.com/go/e-pcsupport 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 contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. This document contains proprietary information that is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without the prior written consent of Hewlett-Packard Company. Adobe®, Acrobat® and Acrobat® Reader™ are trademarks or registered trademarks of Adobe Systems Incorporated. Microsoft®, MS-DOS®, Windows® and Windows NT® are U.S. registered trademarks of Microsoft Corporation. Celeron™ and AGPset™ are trademarks of Intel Corporation. Intel® and Pentium® are registered trademarks of Intel Corporation. Symbios® is a registered trademark of LSI Logic Corporation. NVIDIA™, GeForce2 MX™, GeForce3™, TNT™, Vanta™ and TwinView™ are trademarks of NVIDIA Corporation. Matrox® and DualHead® are registered trademarks of Matrox Electronic Systems Ltd. ATI™ is a trademark of ATI Technologies Inc. WOL™ (Wake on LAN) is a trademark of IBM Corporation. CrystalClear™ is a trademark and Crystal® is a registered trademark of Cirrus Logic Incorporated.
    [Show full text]
  • Opengl Distilled / Paul Martz
    Page left blank intently OpenGL® Distilled By Paul Martz ............................................... Publisher: Addison Wesley Professional Pub Date: February 27, 2006 Print ISBN-10: 0-321-33679-8 Print ISBN-13: 978-0-321-33679-8 Pages: 304 Table of Contents | Inde OpenGL opens the door to the world of high-quality, high-performance 3D computer graphics. The preferred application programming interface for developing 3D applications, OpenGL is widely used in video game development, visuali,ation and simulation, CAD, virtual reality, modeling, and computer-generated animation. OpenGL® Distilled provides the fundamental information you need to start programming 3D graphics, from setting up an OpenGL development environment to creating realistic te tures and shadows. .ritten in an engaging, easy-to-follow style, this boo/ ma/es it easy to find the information you0re loo/ing for. 1ou0ll quic/ly learn the essential and most-often-used features of OpenGL 2.0, along with the best coding practices and troubleshooting tips. Topics include Drawing and rendering geometric data such as points, lines, and polygons Controlling color and lighting to create elegant graphics Creating and orienting views Increasing image realism with te ture mapping and shadows Improving rendering performance Preserving graphics integrity across platforms A companion .eb site includes complete source code e amples, color versions of special effects described in the boo/, and additional resources. Page left blank intently Table of contents: Chapter 6. Texture Mapping Copyright ............................................................... 4 Section 6.1. Using Texture Maps ........................... 138 Foreword ............................................................... 6 Section 6.2. Lighting and Shadows with Texture .. 155 Preface ................................................................... 7 Section 6.3. Debugging .......................................... 169 About the Book ....................................................
    [Show full text]
  • Ranger Environment Documentation
    Ranger Environment Documentation Drew Dolgert May 18, 2010 Contents 1 Introduction 2 1.1 Ranger Hardware ....................................... 2 2 Connect 3 2.1 Login Nodes ........................................... 3 2.2 Exercise: Use SSH to Connect ................................ 3 2.2.1 SSH from Linux or Mac ................................ 3 2.2.2 SSH from Windows .................................. 3 2.3 Starting: Read Examples of Sessions ............................ 4 2.4 Further Exercise: Using X-Windows to Connect ...................... 5 2.4.1 Opening a Connection From Mac .......................... 5 2.4.2 Opening a Connection From Linux ......................... 6 2.4.3 Opening a Connection From Windows ....................... 6 2.5 Exercise: Connect with VNC ................................. 9 2.6 Further Exercise: Choose Your Shell ............................ 9 2.7 Advanced: Make Login Faster ................................ 10 2.7.1 Making Shortcuts on Windows ............................ 10 2.7.2 Setup SSH Keys for No Password Login ....................... 10 3 Using Module 10 3.1 About the Module Command ................................. 10 3.2 Discussion Exercise: Learn Modules ............................ 11 3.3 Modules List .......................................... 11 3.4 Exercise: Compilation with Modules ............................ 15 3.5 Further Exercise: Module Dependencies .......................... 15 4 Running in Batch 17 4.1 Text Editors ........................................... 17 4.1.1 VI Cheat Sheet
    [Show full text]
  • The Future of X.Org on Non-GNU/Linux Systems
    The future of X.Org on non-GNU/Linux systems Matthieu Herrb OpenBSD/X.Org February 2, 2013 Introduction X has always been multi-platform XFree86 was started on SVr4 and FreeBSD, ported on Linux later. GNU/Linux/Freedesktop is now dominating the market... Most of X.Org development happen on Linux But In the Free Software world, should it be the only one ? 2/18 Agenda 1 System-dependent components 2 Current status 3 Observations 4 Conclusion 3/18 History X11R5 : one DDX per system, used OS-Specific kernel interfaces also supported non TCP/IP network protocols (decnet,...) XFree86 2 & 3: one DDX for all systems with os-support layer, direct hw access to VGA cards, avoiding complex kernel interfaces for video card support XFree86 4: added the OS-independant modules loader X.Org 7 started removing support for older, non POSIX, non TCP-IP systems (VMS, DECnet, OS/2,..) Remove direct hw access (KMS, DRI2) Turn the DDX to a GNU/Linux ? 4/18 Modern X.Org architecture Toolkits & Applications libGL Mesa/Gallium driver libX11/libxcb X server X driver libdrm drm console driver kernel graphics hardware 5/18 System dependencies locations toolchain support C99 Threads (and TLS) SSE2/Arm NEON/sparc VIS/PPC Altivec supprt (pixman) xserver/hw/xfree86/common/compiler.h ← nightmare... xserver/hw/xfree86/os-support/ console driver interface xserver/confg/ device hot-plug interface libpciaccess PCI bus interface xf86-input-* system keyboard/mouse interface libdrm kernel interface, including KMS XQuartz Xwin 2 remaining system specific DDXen xf86-video-* video driver interfaces 6/18 Solaris Thanks to Alan Coopersmith for the data Latest release: Solaris 11.1 X is in the OS.
    [Show full text]
  • Deconstructing Hardware Usage for General Purpose Computation on Gpus
    Deconstructing Hardware Usage for General Purpose Computation on GPUs Budyanto Himawan Manish Vachharajani Dept. of Computer Science Dept. of Electrical and Computer Engineering University of Colorado University of Colorado Boulder, CO 80309 Boulder, CO 80309 E-mail: {Budyanto.Himawan,manishv}@colorado.edu Abstract performance, in 2001, NVidia revolutionized the GPU by making it highly programmable [3]. Since then, the programmability of The high-programmability and numerous compute resources GPUs has steadily increased, although they are still not fully gen- on Graphics Processing Units (GPUs) have allowed researchers eral purpose. Since this time, there has been much research and ef- to dramatically accelerate many non-graphics applications. This fort in porting both graphics and non-graphics applications to use initial success has generated great interest in mapping applica- the parallelism inherent in GPUs. Much of this work has focused tions to GPUs. Accordingly, several works have focused on help- on presenting application developers with information on how to ing application developers rewrite their application kernels for the perform the non-trivial mapping of general purpose concepts to explicitly parallel but restricted GPU programming model. How- GPU hardware so that there is a good fit between the algorithm ever, there has been far less work that examines how these appli- and the GPU pipeline. cations actually utilize the underlying hardware. Less attention has been given to deconstructing how these gen- This paper focuses on deconstructing how General Purpose ap- eral purpose application use the graphics hardware itself. Nor has plications on GPUs (GPGPU applications) utilize the underlying much attention been given to examining how GPUs (or GPU-like GPU pipeline.
    [Show full text]
  • AMD Radeon E8860
    Components for AMD’s Embedded Radeon™ E8860 GPU INTRODUCTION The E8860 Embedded Radeon GPU available from CoreAVI is comprised of temperature screened GPUs, safety certi- fiable OpenGL®-based drivers, and safety certifiable GPU tools which have been pre-integrated and validated together to significantly de-risk the challenges typically faced when integrating hardware and software components. The plat- form is an off-the-shelf foundation upon which safety certifiable applications can be built with confidence. Figure 1: CoreAVI Support for E8860 GPU EXTENDED TEMPERATURE RANGE CoreAVI provides extended temperature versions of the E8860 GPU to facilitate its use in rugged embedded applications. CoreAVI functionally tests the E8860 over -40C Tj to +105 Tj, increasing the manufacturing yield for hardware suppliers while reducing supply delays to end customers. coreavi.com [email protected] Revision - 13Nov2020 1 E8860 GPU LONG TERM SUPPLY AND SUPPORT CoreAVI has provided consistent and dedicated support for the supply and use of the AMD embedded GPUs within the rugged Mil/Aero/Avionics market segment for over a decade. With the E8860, CoreAVI will continue that focused support to ensure that the software, hardware and long-life support are provided to meet the needs of customers’ system life cy- cles. CoreAVI has extensive environmentally controlled storage facilities which are used to store the GPUs supplied to the Mil/ Aero/Avionics marketplace, ensuring that a ready supply is available for the duration of any program. CoreAVI also provides the post Last Time Buy storage of GPUs and is often able to provide additional quantities of com- ponents when COTS hardware partners receive increased volume for existing products / systems requiring additional inventory.
    [Show full text]
  • The Opengl Framebuffer Object Extension
    TheThe OpenGLOpenGL FramebufferFramebuffer ObjectObject ExtensionExtension SimonSimon GreenGreen NVIDIANVIDIA CorporationCorporation OverviewOverview •• WhyWhy renderrender toto texture?texture? •• PP--bufferbuffer // ARBARB renderrender texturetexture reviewreview •• FramebufferFramebuffer objectobject extensionextension •• ExamplesExamples •• FutureFuture directionsdirections WhyWhy RenderRender ToTo Texture?Texture? • Allows results of rendering to framebuffer to be directly read as texture • Better performance – avoids copy from framebuffer to texture (glCopyTexSubImage2D) – uses less memory – only one copy of image – but driver may sometimes have to do copy internally • some hardware has separate texture and FB memory • different internal representations • Applications – dynamic textures – procedurals, reflections – multi-pass techniques – anti-aliasing, motion blur, depth of field – image processing effects (blurs etc.) – GPGPU – provides feedback loop WGL_ARB_pbufferWGL_ARB_pbuffer •• PixelPixel buffersbuffers •• DesignedDesigned forfor offoff--screenscreen renderingrendering – Similar to windows, but non-visible •• WindowWindow systemsystem specificspecific extensionextension •• SelectSelect fromfrom anan enumeratedenumerated listlist ofof availableavailable pixelpixel formatsformats usingusing – ChoosePixelFormat() – DescribePixelFormat() ProblemsProblems withwith PBuffersPBuffers • Each pbuffer usually has its own OpenGL context – (Assuming they have different pixel formats) – Can share texture objects, display lists between
    [Show full text]
  • Millennium G400/G400 MAX User Guide
    ENGLISH Millennium G400 • Millennium G400 MAX User Guide 10526-301-0510 1999.05.21 Contents Using this guide 3 Hardware installation 4 Software installation 7 Software setup 8 Accessing PowerDesk property sheets................................................................................................8 Monitor setup ......................................................................................................................................8 DualHead Multi-Display setup............................................................................................................9 More information ..............................................................................................................................11 Troubleshooting 12 Extra troubleshooting 18 Graphics ............................................................................................................................................18 Video .................................................................................................................................................23 DVD ..................................................................................................................................................24 TV output 26 Connection setup...............................................................................................................................26 SCART adapter .................................................................................................................................28 Software
    [Show full text]