A Cross-Platform Evaluation of Graphics Shader Compiler
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Vulkan Loader Deep Dive Mark Young and Lenny Komow Welcome! Who We Are
Vulkan Loader Deep Dive Mark Young and Lenny Komow Welcome! Who We Are.. • LunarG: – Software engineering firm focusing on Graphics and Shader technologies – Valve provides financing to support Vulkan Ecosystem: • Vulkan desktop loader • Validation layers • Tools (Trace/Replay, VIA) • Mark Young: – Current Vulkan desktop loader owner – OpenGL User-Mode drivers 9.5 years (ATI/AMD) – DirectX Kernel-Mode drivers 5 years (Qualcomm) • Lenny Komow – Desktop Loader support (working towards co-owner) – 2D/3D ECAD rendering 1.5 years (Cadence Design) Ask Yourself, “What Do I Want to Learn?” “You’ve got to be very careful if you don’t know where you are going, because you might not get there.” -Yogi Berra What This Is Not... • An introduction to Vulkan • A Vulkan tutorial on writing: – Applications Don’t abandon ship yet! – Layers – Drivers • An overview of using Validation Layers Look for that and more on the Khronos Vulkan Resources page We Will Be Covering... - A detailed look at the Vulkan Loader and its interfaces to: - Applications - Drivers - Layers - Debug settings - Possible optimizations Vulkan App Developer View Loader Position (High-Level) Really Loader(s) Plural • Intent is only one loader to rule them all, but reality is – Two different loaders: • Desktop Loader – Same source used for Linux/Windows • Android Loader – Nougat+ devices • Still, one loader interface design (in GitHub and LunarG Vulkan SDK) Loader Interface Doc • Available in Vulkan-LoaderAndValidationLayers Github ./loader/LoaderAndLayerInterface.md • Valid for all Vulkan -
Lightning Talks
X.Org Developer’s Conference 2019 Report of Contributions https://xdc2020.x.org/e/XDC2019 X.Org Develope … / Report of Contributions State of the X.org Contribution ID: 8 Type: not specified State of the X.org Friday, 4 October 2019 14:50 (20 minutes) Your secretary’s yearly report on the state of the X.org Foundation. Expect updates on the freedeskop- top.org merger, internship and student programs, XDC, and more! Code of Conduct Yes GSoC, EVoC or Outreachy No Presenter: VETTER, Daniel (Intel) Session Classification: Main Track September 26, 2021 Page 1 X.Org Develope … / Report of Contributions Everything Wrong With FPGAs Contribution ID: 10 Type: not specified Everything Wrong With FPGAs Friday, 4 October 2019 11:40 (45 minutes) FPGAs and their less generic cousin, specialized accelerators have come onto the scene in a way that GPUs did 20 or so years ago. Indeed new interfaces have cropped up to support them in a fashion resembling early GPUs, and some vendors have even opted to try to use DRM/GEM APIs for their devices. This talk will start with a background of what FPGAs are, how they work, and where they’re currently used. Because the audience is primarily people with graphics/display background, I will make sure to cover this well. It will then discuss the existing software ecosystem around the various usage models with some comparison of the existing tools. If time permits, I will provide a demo comparing open tools vs. closed ones. The goal of the talk is to find people who have lived through DRI1 days and are abletohelp contribute their experience (and coding) toward improving the stack for the future accelerators. -
Third Party License Terms List
QNX® THIRD PARTY LICENSE TERMS LIST Version 2.14a Includes: Supplement for Screen Graphics Subsystem for QNX Software Development Platform 6.5 Service Pack 1 (“Screen”) (See Publication History for version details) Table of Contents 1. Introduction 2. Tables 2.1 Condensed Version of File Mapping Tables (Summarized by License Family) 2.2 Complete Version of File Mapping Tables (Includes Full Legal ID Codes) 3. Licenses 3.1 License Types and Codes 3.2 License Texts © 2015 QNX Software Systems Limited, a subsidiary of BlackBerry Limited. All rights reserved. QNX, QNX CAR, Momentics, Neutrino and Aviage are trademarks of BlackBerry Limited, which are registered and/or used in certain jurisdictions, and are used under license by QNX Software Systems Limited. All other trademarks belong to their respective owners. 1. Introduction This version 2.14a of the QNX Third Party License Terms List (“TPLTL”) is the companion document to version 2.14a of the QNX License Guide (“License Guide”) (see http://licensing.qnx.com/document-archive/). As explained in the License Guide, QNX Software Systems Limited (“QSS”) incorporates certain third-party software in our products. The license terms associated with some of the third-party software requires that we provide the recipient with additional information such as attributions, copies of licenses, or source code (“Compliance”). This document encapsulates Compliance for Screen. This TPLTL is divided into two sections as follows: 1. The summary tables in section 2.1 provide an overview of types of licenses (“Legal ID Codes”) for third-party software that QSS has reused and that have Compliance requirements. -
Mesa Documentation Release 12.0
Mesa Documentation Release 12.0 Brian Paul et al. August 28, 2016 General 1 Introduction 1 2 Developers 7 3 Supported Systems and Drivers9 4 Disclaimer 11 5 Mesa Frequently Asked Questions 13 6 Release Notes 19 7 Acknowledgements 25 8 Conformance 27 9 Downloading 39 10 Compiling and Installing 41 11 Compilation and Installation using Autoconf 45 12 Precompiled Libraries 49 13 Mailing Lists 51 14 Bug Database 53 15 Webmaster 55 16 Shading Language Support 57 17 Mesa EGL 61 18 OpenGL ES 65 19 Environment Variables 67 20 Off-screen Rendering 73 21 Debugging Tips 75 i 22 Performance Tips 77 23 Mesa Extensions 79 24 Function Name Mangling 81 25 llvmpipe 83 26 VMware guest GL driver 87 27 Gallium Post-processing 91 28 Application Issues 93 29 Viewperf Issues 95 30 Code Repository 99 31 Mesa source code tree overview 103 32 Development Utilities 107 33 Help Wanted / To-Do List 109 34 Development Notes 111 35 Source Code Documentation 121 36 GL Dispatch in Mesa 123 37 Indices and tables 127 ii CHAPTER 1 Introduction Mesa is an open-source implementation of the OpenGL specification - a system for rendering interactive 3D graphics. A variety of device drivers allows Mesa to be used in many different environments ranging from software emulation to complete hardware acceleration for modern GPUs. Mesa ties into several other open-source projects: the Direct Rendering Infrastructure and X.org to provide OpenGL support to users of X on Linux, FreeBSD and other operating systems. Project History The Mesa project was originally started by Brian Paul. -
Android-X86 Status Update Graphics Stack Evolution
26-28 Sept. - A Coruña Android-x86 status update from lead developer Chih-Wei Huang Graphics stack evolution android-x86.org presented by Mauro Rossi (maurossi) Agenda - Part I 26-28 Sept. - A Coruña Android-x86 status update • Android-x86 project origins • Android-x86 as seen in analytics • Porting proceedings • How to contribute to add new supported Hardware • Stable and development release status • Future Plans android-x86.org Android-x86: what is it? 26-28 Sept. - A Coruña It is an Android Board Support Package* For generic x86 platforms, including Desktop, Laptops Effective Desktop OS alternative, with “Mouse Click as a Touch” Completely Open Source and tracked as Linux OS in DistroWatch Started in 2009 by Chih-Wei Huang and Yi Sun (beyounn) *https://en.wikipedia.org/wiki/Board_support_package android-x86.org Android-x86 in analytics (1/2) 26-28 Sept. - A Coruña 3 milion downloads reached and users still growing android-x86.org Android-x86 in analytics (2/2) 26-28 Sept. - A Coruña android-x86.org Porting proceedings 26-28 Sept. - A Coruña • Prepare the codebase manifest xml • AOSP git projects • Modified AOSP git projects • device/generic/x86 • device/generic/common (BoardConfig.mk, init.sh) • frameworks/base (SurfaceFlinger) • hardware/libhardware{,_*} • system/core • kernel • Android-x86 git projects • bootable/newinstaller • external/drm_gralloc • external/libdrm (update versions) • external/mesa (updated versions) • external/llvm (updated versions) Chih-Wei Wang android-x86.org Our development cycle 26-28 Sept. - A Coruña “Agile by necessity” Apply android-x86 patches (git rebase) to AOSP Try to build and fix compiling errors Try to boot, identify and fix problems • Display is one the most critical aspects android-x86.org Android-x86 and CI/CD 26-28 Sept. -
Releasing and Testing Free Opensource Graphics Drivers: the Case of Mesa3d
Releasing and Testing Free Opensource Graphics Drivers: the case of Mesa3D Emil Velikov ([email protected]) Juan A. Suárez ([email protected]) with Pierre-Loup Griffais ([email protected]) XDC 2018 The speakers - Emil Velikov - Software engineer at Collabora - Mesa developer since 2011, release manager 2014 - Juan A. Suárez - Software engineer at Igalia - Mesa developer since 2015, release manager 2017 XDC 2018 Agenda - Introduction to Mesa3D - Releases - Historical walk of the release process - The current process - Test systems used - Freedesktop’s GitLab CI - LunarG’s Mesa3D regression test system XDC 2018 Introduction to Mesa3D - Started by Brian Paul in 1993 (25 years old!) - “Framework” to implement graphics drivers supporting different graphics standards: OpenGL/ES, Vulkan, OpenCL, OpenMax, etc - Different parts common to all drivers - Parts common to many drivers (NIR, Gallivm, etc) - Drivers targeting many vendors - Official drivers from Intel - Unofficial drivers from AMD and NVidia - ARM drivers - Qualcomm, Broadcom, Vivante - Two virtual drivers - VMware and VirGL - Four software drivers XDC 2018 Releases - Feature releases - Big releases with new features - 4 in a year (one per quarter, more or less): Mesa YEAR.X.0, with X={0..3} - Started as branch point in master - Apply patches to stabilize and fix bugs - Create a RC release per week, around 4 weeks until everything is fine - Create final release from last RC - Bugfix releases - No new features, only fixes - One release every two weeks - Last release -
Vulkan Developer Driver Branch ( - Will Be in Mainline Drivers Soon
DEVELOPER DAY #KhronosDevDay GDC 2019 #KhronosDevDay © Copyright Khronos™ Group 2018 - Page 1 Schedule 1:20 Vulkan: The State of the Union • Tom Olson (Arm), Karl Schultz (LunarG), Jeff Bolz (NVIDIA) Break 2:40 Making Use of New Vulkan Features • Matthäus Chajdas (AMD), Tiemo Jung (Gaijin), Lewis Gordon (Samsung) Break 4:00 Bringing ‘Fortnite’ to Mobile with Vulkan and OpenGL ES • Jack Porter (Epic Games) and Kostiantyn Drabeniuk (Samsung) Break 5:30 Ubisoft’s Experience Developing with Vulkan • Jean-Noe Morissette (Ubisoft) Copyright © 2019 The Khronos® Group Inc. - Page 2 DEVELOPER DAY Vulkan: The State of the Union GDC 2019 #KhronosDevDay © Copyright Khronos™ Group 2018 - Page 3 Vulkan and OpenGL ES Updates Vulkan: The State of the Union • Tom Olson (Arm), Vulkan WG chair GPU Assisted Validation: A Shallow Dive • Karl Schultz (LunarG) Buffer References • Jeff Bolz (NVIDIA) Copyright © 2019 The Khronos® Group Inc. - Page 4 Vulkan: The State of the Union Tom Olson (Arm), Vulkan WG Chair Copyright © 2019 The Khronos® Group Inc. - Page 5 Adoption news: Hardware Hardware and Drivers Support from all* major GPU vendors ANV • Standard in desktop driver drops Still some legacy issues • Driver updates needed for older HW • Low-end mobile GPU limitations RADV Copyright © 2019 The Khronos® Group Inc. - Page 6 Adoption news: Platforms Supported on the major open Oses Open Platforms • Best on Android, Linux, Win 10 Portability Initiative for closed platforms • Linkable open source libraries • Map Vulkan calls to native API • Support only the efficient subset Copyright © 2019 The Khronos® Group Inc. - Page 7 Platform news: Q is my favorite letter! https://commons.wikimedia.org/w/index.php?curid=1293008 By Towpilot - Own work, CC BY CC work, Own - SA 3.0, SA https://android-developers.googleblog.com/2019/03/introducing-android-q-beta.html Copyright © 2019 The Khronos® Group Inc. -
004 Vulkangettingstarted
Getting Started with Vulkan Loader, Layers, and Other Resources Before You Begin Supported Operating Systems: - Windows 7+ (32-bit or 64-bit) - Linux - Ubuntu 14.04 or newer - Fedora Core 23 or newer - Android Nougat or newer C/C++ Compiler (minimum): - Visual Studio 2013 - GCC 4.8.1 - Clang 3.3 Tools: - Python 3 - CMake 3.0+ - Git Graphics Hardware Desktop Devices (minimum): AMD: Radeon HD 77xx [Windows] Radeon R9 [Linux] Intel: Skylake [Windows] Ivy Bridge [Linux] Nvidia: GeForce 600 series Android Nougat (or newer) Devices: ARM: Mali T760 Imagination: PowerVR Series 6 Nvidia: Tegra K1 Qualcomm: Adreno 500 NOTE: This is an approximate list. Contact your HW provider for up-to-date support info. Vulkan SDKs Contain Useful Content - Latest Documentation - Validation layers - Samples - Other Useful Tools Android Vulkan SDK https://developer.android.com/ndk/guides/graphics/getting-started.html Targets: - Android Nougat Devices Requires: - Android Studio 2.1+ Desktop Vulkan SDK https://vulkan.lunarg.com/ Targets: - Windows - Linux Also Includes: - Latest Vulkan Loader/Run-time - Additional Layers - Screenshot - Trace/replay - Tutorial Released every 4 - 6 weeks Vulkan Installation Analyzer (VIA) Validates your desktop setup - Determines available Vulkan drivers, runtime, and layers - Captures system state into HTML Run it: - After installing SDK or new drivers - When you file a bug VIA Results Overall Result spit out to Command-line (detailed in Readme file): SUCCESS: Validation completed properly ERROR: Failed to find Vulkan Driver JSON ERROR: