Openvg 1.1 API Quick Reference Card - Page 1

Total Page:16

File Type:pdf, Size:1020Kb

Openvg 1.1 API Quick Reference Card - Page 1 OpenVG 1.1 API Quick Reference Card - Page 1 OpenVG® is an API for hardware-accelerated two-dimensional Errors [4.1] vector and raster graphics. It provides a device-independent Error codes and their numerical values are defined by the VGErrorCode enumeration and can be and vendor-neutral interface for sophisticated 2D graphical obtained with the function: VGErrorCode vgGetError(void). The possible values are as follows: applications, while allowing device manufacturers to provide VG_NO_ERROR 0 VG_UNSUPPORTED_IMAGE_FORMAT_ERROR 0x1004 hardware acceleration where appropriate. VG_BAD_HANDLE_ERROR 0x1000 VG_UNSUPPORTED_PATH_FORMAT_ERROR 0x1005 • [n.n.n] refers to sections and tables in the OpenVG 1.1 API VG_ILLEGAL_ARGUMENT_ERROR 0x1001 VG_IMAGE_IN_USE_ERROR 0x1006 specification available at www.khronos.org/openvg/ VG_OUT_OF_MEMORY_ERROR 0x1002 VG_NO_CONTEXT_ERROR 0x1007 • Default values are shown in blue. VG_PATH_CAPABILITY_ERROR 0x1003 Data Types & Number Representations Colors [3.4] The sRGB color space defines values R’sRGB, G’sRGB, B’sRGB in terms of the linear lRGB primaries. Primitive Data Types [3.2] Colors in OpenVG other than those stored in image pixels are represented as non-premultiplied sRGBA color values. openvg.h khronos_type.h range Convert from lRGB to sRGB Convert from sRGB to lRGB Image pixel color and alpha values lie in the range [0,1] (gamma mapping) (1) (inverse gamma mapping) (2) VGbyte khronos_int8_t [-128, 127] unless otherwise noted. -1 VGubyte khronos_uint8_t [0, 255] R’sRGB = γ(R) R = γ (R’sRGB) Color Space Definitions -1 The linear lRGB color space is defined in terms of the G’sRGB = γ(G) G = γ (G’sRGB) VGshort khronos_int16_t [-32768, 32767] -1 standard CIE XYZ color space, following ITU Rec. 709 B’sRGB = γ(B) B = γ (B’sRGB) VGushort khronos_uint16_t [0, 65535] using a D65 white point: VGint khronos_int32_t [-2³¹, (2³¹-1)] R = 3.240479 X –1.537150 Y – 0.498535 Z The linear grayscale (luminance) color space (which we VGuint khronos_uint32_t [0, (2³²-1)] G =-0.969256 X +1.875992 Y +0.041556 Z denote as lL) is related to the linear lRGB color space by the equations: VGbitfield khronos_uint32_t [0, (2³²-1)] B = 0.055648 X –0.204043 Y +1.057311 Z L = 0.2126 R + 0.7152 G + 0.0722 B (3) VGboolean khronos_int32_t [0, 1] Color Space Conversions R = G = B = L (4) VGfloat khronos_float_t IEEE 754 Standard In the following table, the source format is in the left column, and the destination format is in the top row. The The perceptually-uniform grayscale color space (which Number Representations [3.3] numbers indicate the numbered equations (n) from this we denote as sL) is related to the linear grayscale section that are to be applied, in left-to-right order: (luminance) color space by the gamma mapping: VG_MAXSHORT largest positive value of VGshort, Src/Dst IRGB sRGB IL sL L’ = γ(L) (5) smallest negative value is -1 (–VG_MAXSHORT – 1) IRGB — 1 3 3, 5 L = γ (L’) (6) sRGB 2 — 2, 3 2, 3, 5 VG_MAXINT largest positive value of VGint, smallest Conversion from perceptually-uniform grayscale to sRGB negative value is (–VG_MAXINT – 1) IL 4 4, 1 — 5 is performed by replication: sL 7, 2 7 6 — R’ = G’ = B’ = L’ (7) VG_MAX_FLOAT largest floating-point number Handle-based Data Types [3.6] typedef VGuint VGHandle; Object Parameter Set/Get API [5.3] VGfloat vgGetParameterf(VGHandle obj, VGint paramType) vgGetParameteri obj paramType VGFont reference to font data void vgSetParameterf(VGHandle obj, VGint paramType, VGint (VGHandle , VGint ) VGfloat val) VGint vgGetParameterVectorSize(VGHandle obj, VGint VGImage reference to image data void vgSetParameteri(VGHandle obj, VGint paramType, paramType) VGfloat val) VGMaskLayer reference to mask data void vgGetParameterfv(VGHandle obj, VGint paramType, void vgSetParameterfv(VGHandle obj, VGint paramType, VGint cnt, VGfloat * val) VGPaint reference to a paint specification VGint cnt, const VGfloat * val) void vgGetParameteriv(VGHandle obj, VGint type, VGint cnt, VGPath reference to path data void vgSetParameteriv(VGHandle obj, VGint paramType, VGint cnt, const VGint * val) VGint * val) Drawing Context [4] EGL Functions [4.2] EGL Attribute List param_name Usable EGLConfigs have EGL_OPENVG_BIT param_name EGL_MAX_SWAP_INTERVAL State Element Description set in EGL_RENDERABLE_TYPE attribute. The EGL_BUFFER_SIZE EGL_LUMINANCE_SIZE Drawing Surface Surface for drawing EGL_ALPHA_MASK_SIZE attribute contains the bit depth of the mask. attrib_list is an EGL_ALPHA_SIZE EGL_ALPHA_MASK_SIZE Matrix Mode Trans. to be manipulated array with pairs of param_name and value, EGL_BLUE_SIZE EGL_COLOR_BUFFER_TYPE Path user-to-surface Affine trans. for filled and terminating with EGL_NONE. Transformation stroked geometry See EGL Attribute List EGL_GREEN_SIZE EGL_RENDERABLE_TYPE EGL_RED_SIZE EGL_MATCH_NATIVE_PIXMAP Image user-to- Affine or projective trans. EGLBoolean eglBindAPI(EGLenum api) surface Transform for images api: use EGL_OPENVG_API. to bind OpenVG EGL_DEPTH_SIZE EGL_CONFORMANT Paint-to-user Affine transformations for EGLContext eglCreateContext( EGL_STENCIL_SIZE EGL_CONFORMANT_KHR Transformations paint applied to geometry EGLDisplay dpy, EGLConfig config, EGL_CONFIG_CAVEAT EGL_SLOW_CONFIG Glyph user-to-surface Affine transformation for EGLContext share_context, EGL_CONFIG_ID EGL_NON_CONFORMANT_CONFIG Transformation glyphs const EGLint * attrib_list) EGL_LEVEL EGL_TRANSPARENT_RGB Glyph origin (X,Y) origin of glyph EGLSurface eglCreateWindowSurface( EGL_MAX_PBUFFER_HEIGHT EGL_RGB_BUFFER Fill Rule Rule for filling paths EGLDisplay dpy, EGLConfig config, NativeWindowType win, EGL_MAX_PBUFFER_PIXELS EGL_LUMINANCE_BUFFER Quality Settings Image and rendering const EGLint * attrib_list) EGL_MAX_PBUFFER_WIDTH EGL_NO_TEXTURE quality, pixel layout EGLSurface EGL_NATIVE_RENDERABLE EGL_TEXTURE_RGB Color Transformation Color Transformation eglCreatePbufferFromClientBuffer( EGL_NATIVE_VISUAL_ID EGL_TEXTURE_RGBA Blend Mode Pixel blend function EGLDisplay dpy, EGLenum buftype, EGL_NATIVE_VISUAL_TYPE EGL_TEXTURE_2D Image Mode Image/paint combination EGLClientBufferbuffer , EGLConfigconfig , EGL_PRESERVED_RESOURCES EGL_PBUFFER_BIT const EGLint * attrib_list) Scissoring Enable/disable scissoring Pbuffer (off-screen buffer) allow rendering into EGL_SAMPLES EGL_PIXMAP_BIT Stroke Stroke parameters a VGImage. EGL_SAMPLE_BUFFER EGL_WINDOW_BIT Pixel & Screen layout Pixel layout information EGLBoolean eglMakeCurrent( EGL_SURFACE_TYPE EGL_VG_COLORSPACE_LINEAR_BIT EGLDisplay dpy, EGLSurface draw, EGL_TRANSPARENT_TYPE EGL_VG_ALPHA_FORMAT_PRE_BIT Tile fill color Color for FILL tiling mode EGLSurface read, EGLContext context) Clear color Color for fast clear Causes the given context to become current on EGL_TRANSPARENT_BLUE_VALUE EGL_OPENGL_ES_BIT EGL_TRANSPARENT_GREEN_VALUE EGL_OPENVG_BIT Filter Parameters Image filtering parameters the running thread. EGL_TRANSPARENT_RED_VALUE Paint Paint definitions EGLContext eglGetCurrentContext() EGL_NONE Forcing Drawing to Complete API [4.3] Mask Coverage mask and EGLBoolean eglDestroyContext( void vgFlush(void) enable/disable EGLDisplay dpy,EGLContext context) EGL_BIND_TO_TEXTURE_RGB Complete requests in finite time. EGL_BIND_TO_TEXTURE_RGBA Error Oldest unreported error EGLBoolean eglSwapBuffers( void vgFinish(void) EGLDisplay dpy, EGLSurface surface) EGL_MIN_SWAP_INTERVAL Complete requests. ©2010 Khronos Group - Rev. 0410 www.khronos.org/openvg OpenVG 1.1 API Quick Reference Card - Page 2 Context Parameters VG_FILL_RULE (VGFillRule) VG_STROKE_LINE_WIDTH (VGfloat) VG_SCISSORING (VGboolean) Context Parameter Set/Get API [5.2] VG_EVEN_ODD VG_NON_ZERO 1.0f VG_TRUE VG_FALSE(disabled) void vgSetf(VGParamType paramType, VG_IMAGE_QUALITY (VGImageQuality) VG_STROKE_CAP_STYLE (VGCapStyle) VG_SCREEN_LAYOUT (VGPixelLayout) VGfloat val) VG_IMAGE_QUALITY_NONANTIALIASED VG_CAP_BUTT VG_PIXEL_LAYOUT (VGPixelLayout) VG_IMAGE_QUALITY_FASTER VG_CAP_ROUND VG_PIXEL_LAYOUT_UNKNOWN* void vgSeti(VGParamType paramType, VG_IMAGE_QUALITY_BETTER VG_CAP_SQUARE VG_PIXEL_LAYOUT_RGB_VERTICAL VGint val) VG_PIXEL_LAYOUT_BGR_VERTICAL void vgSetfv(VGParamType paramType, VG_RENDERING_QUALITY (VGRenderingQuality) VG_STROKE_JOIN_STYLE (VGJoinStyle) VG_PIXEL_LAYOUT_RGB_HORIZONTAL VGint cnt, const VGfloat * val) VG_RENDERING_QUALITY_NONANTIALIASED VG_JOIN_MITER VG_PIXEL_LAYOUT_BGR_HORIZONTAL VG_RENDERING_QUALITY_FASTER VG_JOIN_ROUND * This is the default for VG_PIXEL_LAYOUT only. void vgSetiv(VGParamType paramType, VG_RENDERING_QUALITY_BETTER VG_JOIN_BEVEL VGint cnt, const VGint * val) The default for VG_SCREEN_LAYOUT is the VG_BLEND_MODE (VGBlendMode) layout of the drawing surface. paramType VG_STROKE_MITER_LIMIT (VGfloat) VGfloatvgGetf (VGParamType ) VG_BLEND_SRC 4.0f VG_FILTER_FORMAT_LINEAR (VGboolean) VGint vgGeti(VGParamType paramType) VG_BLEND_SRC_OVER VG_TRUE VG_FALSE (disabled) VG_BLEND_DST_OVER VG_STROKE_DASH_PATTERN (VGfloat *) VGint vgGetVectorSize( VG_BLEND_SRC_IN { } (array of length 0) (disabled) VG_FILTER_FORMAT_PREMULTIPLIED VGParamType paramType) VG_BLEND_DST_IN {on1, off1, on2, off2,….} (VGboolean) void vgGetfv(VGParamType paramType, VG_BLEND_MULTIPLY VG_TRUE VG_FALSE(disabled) VG_BLEND_SCREEN VG_STROKE_DASH_PHASE (VGfloat) VGint cnt, VGfloat * val) 0.0f VG_FILTER_CHANNEL_MASK (VGbitfield) VG_BLEND_DARKEN (VG_RED | VG_GREEN | VG_BLUE | VG_ALPHA) void vgGetiv(VGParamType paramType, VG_BLEND_LIGHTEN VGint cnt, VGint * val) VG_STROKE_DASH_PHASE_RESET (VGboolean) VG_BLEND_ADDITIVE VG_FALSE VG_TRUE Read-Only Context Parameters VG_IMAGE_MODE (VGImageMode) VG_MAX_SCISSOR_RECTS (VGint) Context Parameters [5.2.1]
Recommended publications
  • GLSL 4.50 Spec
    The OpenGL® Shading Language Language Version: 4.50 Document Revision: 7 09-May-2017 Editor: John Kessenich, Google Version 1.1 Authors: John Kessenich, Dave Baldwin, Randi Rost Copyright (c) 2008-2017 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast, or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specification for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be reformatted AS LONG AS the contents of the specification are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group website should be included whenever possible with specification distributions.
    [Show full text]
  • Opengl ES / Openvg / Opencl / Webgl / Etc
    KNU-3DC : Education and Training Plan 24 July 2013 Hwanyong LEE, Ph.D. Principal Engineer & Industry Cooperation Prof., KNU 3DC [email protected] KNU-3DC Introduction • Kyungpook National Univ. 3D Convergence Technology Center . Korea Government Funded Org. 23 staffs (10 Ph.D) . Research / Supporting Industry . Training and Education • Training and Education . Dassault Training Center . KIKS(Korea Institute of Khronos Study) • Constructing New Center Building . HUGE ! 7 Floors ! (2014E) 2 KNU-3DC KIKS • KIKS(Korea Institute of Khronos Study) . Leading Role in Korea for Training and Education of Khronos Standard – Collaboration with Khronos Group . Open Lecture + Develop Coursework for • OpenGL / OpenGL ES / OpenVG / OpenCL / WebGL / etc. • Opening / Sponsoring Workshop and Forum . Participating Khronos Activities • Contributor Member (Plan, now Processing) • Active participation of Khronos WG . Other Standard Activities • Make Khronos Standard into Korea National Standard. (WebGL) • W3C, ISO/IEC JTC1, IEEE 3333.X . Research and Consulting for Industry and Academy 3 KIKS Course • KIKS Course will be categorized into . Basic / Advanced / Packaged . Special Course - For instance Overview / Optimization / Consulting • Developing Courseware (for Khronos API) . OpenGL ES Basic & Advanced . OpenGL Basic & Advanced . OpenVG . OpenCL Basic & Advanced . WebGL . Etc. – new standards (Red - Started / Orange – Start at 4Q2013 / Dark Blue – Start at 2014) 4 Different View of Courses University Computer Game Image Parallel View Graphics Develop Processing … Processing JavaScript Khronos Canvas View … iPhone Android Company Web-App Parallel App App Application Develop View Develop Develop … Develop Course Development – Packaging Example • Android Application with OpenGL ES . General Android API’s – JNI, Java etc. OpenGL ES • iPhone App. Development with OpenGL ES . General iPhone APP API – cocoa, Objective-C, etc.
    [Show full text]
  • Hardware Implementation of a Tessellation Accelerator for the Openvg Standard
    IEICE Electronics Express, Vol.7, No.6, 440–446 Hardware implementation of a tessellation accelerator for the OpenVG standard Seung Hun Kim, Yunho Oh, Karam Park, and Won Woo Roa) School of Electrical and Electronic Engineering, Yonsei University, 134 Shinchon-Dong, Seodaemun-Gu, SEOUL, 120–749, KOREA a) [email protected] Abstract: The OpenVG standard has been introduced as an efficient vector graphics API for embedded systems. There have been several OpenVG implementations that are based on the software rendering of image. However, the software rendering needs more execution time and power consumption than hardware accelerated rendering. For the effi- cient hardware implementation, we merge eight pipeline stages in the original specification to four pipeline stages. The first hardware accel- eration stage is the tessellation part which is one of the pipeline stages that calculates the edge of vector graphics. In this paper, we provide an efficient hardware design for the tessellation stage and claim this would eventually reduce the execution time and hardware complexity. Keywords: OpenVG, vector graphics, tessellation, hardware acceler- ator Classification: Electron devices, circuits, and systems References [1] K. Pulli, “New APIs for mobile graphics,” Proc. SPIE - The International Society for Optical Engineering, vol. 6074, pp. 1–13, 2006. [2] Khronos Group Inc., “OpenVG specification Version 1.0.1” [Online] http://www.khronos.org/openvg/ [3] S.-Y. Lee, S. Kim, J. Chung, and B.-U. Choi, “Salable Vector Graphics (OpenVG) for Creating Animation Image in Embedded Systems,” Lecture Notes in Computer Science, vol. 4693, pp. 99–108, 2007. [4] G. He, B. Bai, Z. Pan, and X.
    [Show full text]
  • Real-Time Computer Vision with Opencv Khanh Vo Duc, Mobile Vision Team, NVIDIA
    Real-time Computer Vision with OpenCV Khanh Vo Duc, Mobile Vision Team, NVIDIA Outline . What is OpenCV? . OpenCV Example – CPU vs. GPU with CUDA . OpenCV CUDA functions . Future of OpenCV . Summary OpenCV Introduction . Open source library for computer vision, image processing and machine learning . Permissible BSD license . Freely available (www.opencv.org) Portability . Real-time computer vision (x86 MMX/SSE, ARM NEON, CUDA) . C (11 years), now C++ (3 years since v2.0), Python and Java . Windows, OS X, Linux, Android and iOS 3 Functionality Desktop . x86 single-core (Intel started, now Itseez.com) - v2.4.5 >2500 functions (multiple algorithm options, data types) . CUDA GPU (Nvidia) - 250 functions (5x – 100x speed-up) http://docs.opencv.org/modules/gpu/doc/gpu.html . OpenCL GPU (3rd parties) - 100 functions (launch times ~7x slower than CUDA*) Mobile (Nvidia): . Android (not optimized) . Tegra – 50 functions NEON, GLSL, multi-core (1.6–32x speed-up) 4 Functionality Image/video I/O, processing, display (core, imgproc, highgui) Object/feature detection (objdetect, features2d, nonfree) Geometry-based monocular or stereo computer vision (calib3d, stitching, videostab) Computational photography (photo, video, superres) Machine learning & clustering (ml, flann) CUDA and OpenCL GPU acceleration (gpu, ocl) 5 Outline . What is OpenCV? . OpenCV Example – CPU vs. GPU with CUDA . OpenCV CUDA functions . Future of OpenCV . Summary OpenCV CPU example #include <opencv2/opencv.hpp> OpenCV header files using namespace cv; OpenCV C++ namespace int
    [Show full text]
  • The Openvx™ Specification
    The OpenVX™ Specification Version 1.0.1 Document Revision: r31169 Generated on Wed May 13 2015 08:41:43 Khronos Vision Working Group Editor: Susheel Gautam Editor: Erik Rainey Copyright ©2014 The Khronos Group Inc. i Copyright ©2014 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specifica- tion for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be re-formatted AS LONG AS the contents of the specifi- cation are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group web-site should be included whenever possible with specification distributions.
    [Show full text]
  • The Openvx™ Specification
    The OpenVX™ Specification Version 1.2 Document Revision: dba1aa3 Generated on Wed Oct 11 2017 20:00:10 Khronos Vision Working Group Editor: Stephen Ramm Copyright ©2016-2017 The Khronos Group Inc. i Copyright ©2016-2017 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specifica- tion for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be re-formatted AS LONG AS the contents of the specifi- cation are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group web-site should be included whenever possible with specification distributions.
    [Show full text]
  • An Introduction to Openvg™ FTF-AUT-F0465
    An Introduction to OpenVG™ FTF-AUT-F0465 Oliver Tian | Auto FAE M A Y . 2 0 1 4 TM External Use Agenda • Trend of Graphics in Vehicle • Roadmap of Cluster • Introduction of Rainbow/Vybrid • OpenVG Scenario • Development Ecosystem • Conclusion TM External Use 1 Trend of Graphics in Vehicle TM External Use 2 The Connected Vehicle Infotainment + Communication + Security • Consumer electronics trends are dictating features in the car • Always connected, applications driven, advanced graphics • Infotainment systems becoming battleground for Auto differentiation • As more connected systems get introduced into the vehicle, the need for security is critical − Increasing external communication features (Bluetooth, TPMS, Ethernet, Wi-Fi, etc). − Future interface for vehicle-to-vehicle and vehicle-to-infrastructure. TM External Use 3 Mobility for Everyone Affordable Solutions for Emerging Markets • 100M vehicles annually forecasted before 2020, on top of motorcycle & e-bike growth • 80% of quantity growth after 2015 happening in emerging markets • Safety and emissions reduction are key for a sustainable development Source: IHS Automotive, February 2014 TM External Use 4 More, More, More for Less, Less, Less More performance, more embedded memory, more safety for less cost, less power and less development effort More • Electronic complexity • ECUs per car (50+) • MCUs per car (100+) • In-car Wi-Fi ® (7.2Mbps and 3.7Bpcs by 2017) iSuppli Less Reuse • Other markets have less critical applications • Some automotive specific challenges TM External Use 5 Today’s Car • Complex computerized control − Millions of lines of code, from multiple vendors − Dozens of distinct ECUs, from multiple vendors • Shared internal networking (e.g., CAN, FlexRay) − Increasing external communications features .
    [Show full text]
  • AN5072: Introduction to Embedded Graphics – Application Note
    Freescale Semiconductor Document Number: AN5072 Application Note Rev 0, 02/2015 Introduction to Embedded Graphics with Freescale Devices by: Luis Olea and Ioseph Martinez Contents 1 Introduction 1 Introduction................................................................1 The purpose of this application note is to explain the basic 1.1 Graphics basic concepts.............. ...................1 concepts and requirements of embedded graphics applications, 2 Freescale graphics devices.............. ..........................7 helping software and hardware engineers easily understand the fundamental concepts behind color display technology, which 2.1 MPC5606S.....................................................7 is being expected by consumers more and more in varied 2.2 MPC5645S.....................................................8 applications from automotive to industrial markets. 2.3 Vybrid.............................................................8 This section helps the reader to familiarize with some of the most used concepts when working with graphics. Knowing 2.4 MAC57Dxx....................... ............................ 8 these definitions is basic for any developer that wants to get 2.5 Kinetis K70......................... ...........................8 started with embedded graphics systems, and these concepts apply to any system that handles graphics irrespective of the 2.6 QorIQ LS1021A................... ......................... 9 hardware used. 2.7 i.MX family........................ ........................... 9 2.8 Quick
    [Show full text]
  • The Opengl ES Shading Language
    The OpenGL ES® Shading Language Language Version: 3.20 Document Revision: 12 246 JuneAugust 2015 Editor: Robert J. Simpson, Qualcomm OpenGL GLSL editor: John Kessenich, LunarG GLSL version 1.1 Authors: John Kessenich, Dave Baldwin, Randi Rost 1 Copyright (c) 2013-2015 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast, or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specification for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be reformatted AS LONG AS the contents of the specification are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group website should be included whenever possible with specification distributions.
    [Show full text]
  • MB86R24 “Triton-C” Graphics Display Controller Third-Generation Advanced 2.5D/3D Graphics Soc
    MB86R24 “Triton-C” Graphics Display Controller Third-generation Advanced 2.5D/3D Graphics SoC Description Features The high-performance MB86R24 “Triton-C” combines the latest • ARM Cortex-A9, dual-core 533 MHz (600 MHz in restricted ARM® Cortex™-A9 dual CPU core with state-of-the-art, embed- operating conditions) per core ded 2.5D and 3D graphics cores. This third-generation appli- • 2.5D graphics engine cation processor is the first device in Fujitsu’s new “Blueline” • 3D graphics engine: POWERVR, SGX543-MP1 family of high-performance GDCs. — Tile-Based Deferred Rendering (TBDR) The 3D core incorporates Imagination Technologies’ POWERVR™ — Support for OpenGL ES 2.0, OpenVG™ 1.1 and SGX543-MP1, which supports open standard API formats such OpenCL™ 1.0 as OpenGL® ES 2.0. The POWERVR core uses Tile-Based Deferred • Video capture from five independent channels Rendering (TBDR) for render processing, which reduces perfor- • Broad support for standard and automotive-specific mance loads on the CPU and GPU, and increases system capacity. peripherals The high-end SoC also combines six video-capture inputs and • Three independent parallel display controllers for display three independent parallel display outputs. up to 1920x768 • Up to 1GB of graphics memory The chip’s architecture has been optimized for the simultaneous use of all functional blocks, virtually eliminating performance gaps. The device’s harmonized structure permits the simulta- Applications neous rendering of independent 2.5D and 3D graphics, the • Dashboards capturing of multiple video streams, and the display of content • HUD (head-up display) systems to multiple sources. • CID (central information display) systems With its outstanding rendering performance and multiple stan- • RSE (rear seat entertainment) systems dard and automotive-specific peripheral interfaces, this device is appropriate for a wide range of demanding automotive and industrial applications Signage Medical Automotive and Large Vehicles Industrial The "Triton-C" is well-suited for a variety of graphics applications.
    [Show full text]
  • News Release for More Information: Neil Trevett, President, Khronos | [email protected] | Phone: +1 (408) 464 7053
    News Release For more information: Neil Trevett, President, Khronos | [email protected] | Phone: +1 (408) 464 7053 Khronos Releases OpenVX 1.1 Specification for High Performance, Low Power Computer Vision Acceleration Expanded range of processing functions; Enhanced flexibility for data access and processing; Full conformance tests available; Safety Critical specification in development May 2nd 2016 – Embedded Vision Summit, Santa Clara, CA – The Khronos™ Group, an open consortium of leading hardware and software companies, announces the immediate availability of the OpenVX™ 1.1 specification for cross platform acceleration of computer vision applications and libraries. OpenVX enables performance and power optimized computer vision algorithms for use cases such as face, body and gesture tracking, smart video surveillance, automatic driver assistance systems, object and scene reconstruction, augmented reality, visual inspection, robotics and more. Conformant OpenVX 1.0 implementations and tools are shipping from AMD, Imagination, Intel, NVIDIA, Synopsis and VeriSilicon. OpenVX 1.1 builds on this momentum by adding new processing functions for use cases such as computational photography, and enhances application control over how data is accessed and processed. An open source OpenVX 1.1 sample implementation and full conformance tests will be available before mid-2016. Details on the OpenVX specifications and Adopters Program are available at: www.khronos.org/openvx. “More and more products are incorporating computer vision, and OpenVX
    [Show full text]
  • Tms320c6a8168, Tms320c6a8167 C6000 Dsp+Arm
    TMS320C6A8168 TMS320C6A8167 www.ti.com SPRS680C –OCTOBER 2010–REVISED MARCH 2012 TMS320C6A816x C6000 DSP+ARM Processors Check for Samples: TMS320C6A8168, TMS320C6A8167 1 Device Summary 1.1 Features 1234567891011 • High-Performance C6000™ DSP+ARM® Multiply Supported up to: Processors – 2 SP x SP → SP Per Clock – ARM® Cortex™-A8 RISC Processor – 2 SP x SP → DP Every Two Clocks • Up to 1.5 GHz – 2 SP x DP → DP Every Three Clocks – C674x VLIW DSP – 2 DP x DP → DP Every Four Clocks • Up to 1.25 GHz • Fixed-Point Multiply Supports Two 32 x • Up to 12000/9000 C674x MIPS/MFLOPS 32 Multiplies, Four 16 x 16-bit Multiplies • Fully Software-Compatible with C67x+™ including Complex Multiplies, or Eight 8 x and C64x+™ 8-Bit Multiplies per Clock Cycle • ARM® Cortex™-A8 Core • C674x Two-Level Memory Architecture – ARMv7 Architecture – 32K-Byte L1P and L1D RAM/Cache • In-Order, Dual-Issue, Superscalar – 256K-Byte L2 Unified Mapped RAM/Caches Processor Core • DSP/EDMA Memory Management Unit • NEON™ Multimedia Architecture (DEMMU) – Supports Integer and Floating Point (VFPv3- – Maps C674x DSP and EMDA TCB Memory IEEE754 compliant) Accesses to System Addresses • Jazelle® RCT Execution Environment • 512K-Bytes On-Chip Memory Controller (OCMC) RAM • ARM® Cortex™-A8 Memory Architecture • SGX530 3D Graphics Engine (available only on – 32K-Byte Instruction and Data Caches the C6A8168 device) – 256K-Byte L2 Cache – Delivers up to 30 MTriangles/s – 64K-Byte RAM, 48K-Byte Boot ROM – Universal Scalable Shader Engine • TMS320C674x Floating-Point VLIW DSP – Direct3D®
    [Show full text]