DOCSLIB.ORG

Yocto GENIVI Baseline – Overview

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

The Yocto GENIVI Baseline – Overview Automotive Linux Summit, Fall 2013 Holger Behrens, Wind River Automotive Solutions Abstract The Yocto GENIVI Baseline, a public project of the GENIVI Alliance, based on the Yocto Projects layer for In-Vehicle Infotainment, meta-ivi and the Yocto Projects reference system Poky. meta-ivi contains specific metadata to define tasks to build a Yocto GENIVI Baseline image for either ARMv7a, IA-32, or a x86-64 QEMU machine, systemd specific distribution data sets, and the additional package meta data needed to turn the Yocto Projects reference system Poky into GENIVI compliant system. This presentation gives an overview of the building block used by the GENIVI Alliance to create a software baseline that complies to its latest specification. 2 | © 2013 Wind River. All Rights Reserved. History Revisited GENIVI Baseline Horizon 2014 Gemini Foton 2013 Excalibur Discovery 2012 Cassini Borg Apollo2011 20101.0 GENIVI Alliance est. March 2009 2009 K2 A-Sample BMW, Intel, Wind River, MM K2 6.2 2008 3 | © 2013 Wind River. All Rights Reserved. History Revisited GENIVI Baseline The Yocto Project Horizon 2014 2014 Gemini Foton 2013 2013 Excalibur Discovery 2012 2012 Cassini Borg The Yocto Project announced March 2011 Apollo2011 2011 20101.0 GENIVI Alliance est. March 2009 2009 K2 A-Sample K2 6.2 2008 4 | © 2013 Wind River. All Rights Reserved. History Revisited GENIVI Baseline meta-ivi The Yocto Project Horizon 6.0 1.6 2014 2014 2014 5.0 (Gemini) 5.0 1.5 (dora) 4.0 (Foton) 4.0 1.4 (dylan) 2013 2013 2013 3.0 (Excalibur) 3.0 1.3 (danny) 2.0 (Discovery) denzil 1.2 (denzil) 2012 meta-ivi layer 2012 2012 Cassini est. April 2012 1.0 (Borg) The Yocto Project announced March 2011 Apollo2011 2011 20101.0 GENIVI Alliance est. March 2009 2009 K2 A-Sample K2 6.2 2008 5 | © 2013 Wind River. All Rights Reserved. History Revisited GENIVI Baseline meta-ivi The Yocto Project Horizon 6.0 1.6 2014 2014 2014 5.0 (Gemini) 5.0 1.5 (dora) Yocto GENIVI Baseline July 2013 4.0 (Foton) 4.0 1.4 (dylan) 2013 2013 2013 GENIVI OSS Projects 3.0 (Excalibur) 3.0 1.3 (danny) ALS 2012, September 2012 2.0 (Discovery) denzil 1.2 (denzil) 2012 meta-ivi layer 2012 2012 Cassini est. April 2012 1.0 (Borg) The Yocto Project announced March 2011 Apollo2011 2011 20101.0 GENIVI Alliance est. March 2009 2009 K2 A-Sample K2 6.2 2008 6 | © 2013 Wind River. All Rights Reserved. About Yocto GENIVI Baseline The meta-ivi based Yocto GENIVI Baseline is a GENIVI compliant Linux distribution for a variety of embedded devices. The meta-ivi project aligns itself with The Yocto Project, and the distribution is the result of making the Yocto Project reference system Poky GENIVI compliant. The Yocto Project is a Linux Foundation workgroup whose goal is to produce tools and processes that will enable the creation of Linux distributions for embedded software that are independent of the underlying architecture of the embedded software itself. The Yocto Project is an open source project whose focus is on improving the software development process for embedded Linux distributions. The Yocto Project provides interoperable tools, metadata, and processes that enable the rapid, repeatable development of Linux-based embedded systems. 7 | © 2013 Wind River. All Rights Reserved. Yocto GENIVI Basline – Inputs . Yocto Project 1.5 – Poky 10.0 – URI: git://git.yoctoproject.org/poky branch: dora . Collection of software related to In-Vehicle Infotainment systems – meta-ivi layer – URI: git://git.yoctoproject.org/meta-ivi branch: 5.0 8 | © 2013 Wind River. All Rights Reserved. Supported Machines We do smoke test the builds of the three machines that we currently support: . QEMU (ARMv7) – emulated machine: vexpressa9 . QEMU (IA-32) – emulated machine: qemux86 . QEMU (x86-64) – emulated machine: qemux86-64 Please check the Yocto GENIVI Baseline wiki regarding any community supported machines. 9 | © 2013 Wind River. All Rights Reserved. Yocto GENIVI Baseline – Building Blocks multimedia multimedia connectivity graphics graphics gnome devtools connectivity extended support extended kernel core support Poky meta-ivi 10 | © 2013 Wind River. All Rights Reserved. Building Blocks – Poky (kernel + core) kernel multimedia • kmod • linux-yocto connectivity graphics core gnome devtools • base-files • libxml2 • base-passwd • ncurses • busybox • netbase extended support • coreutils • readline • dbus • systemd / udev kernel core • eglibc • util-linux • expat • glib-2.0 Poky • kbd 11 | © 2013 Wind River. All Rights Reserved. Building Blocks – Poky (support+extended) support • acl • libgpg-error multimedia • attr • libnl • beecrypt • libpcre • curl • libtasn1 connectivity graphics • db • libusb1 • gnutls • libusb-compat • icu • popt gnome devtools • libcap • sqlite3 • libgcrypt • xuser-account extended support extended kernel core • iptables • libpam Poky • procps • quota • shadow 12 | © 2013 Wind River. All Rights Reserved. Building Blocks – Poky (devtools + gnome) devtools • e2fsprogs multimedia • elfutils • file • gcc-runtime connectivity graphics • libgcc • libjson • ossp-uuid gnome devtools • python-smartpm • rpm extended support gnome kernel core • libffi Poky 13 | © 2013 Wind River. All Rights Reserved. Building Blocks – Poky (connect.+graphics) connectivity • avahi multimedia • bluez • connman • ofono connectivity graphics • openssl • wireless-tools • wpa-supplicant gnome devtools graphics extended support • cairo • xorg-driver • drm • xorg-font kernel core • fontconfig • xorg-lib • freetype • xorg-proto • mesa • xorg-xserver Poky • wayland • xcb • xorg-app 14 | © 2013 Wind River. All Rights Reserved. Building Blocks – Poky (multimedia) multimedia • alsa multimedia • gstreamer • libsamplerate • libsndfile connectivity graphics • pulseaudio • speex gnome devtools extended support kernel core Poky 15 | © 2013 Wind River. All Rights Reserved. Building Blocks – meta-ivi distro/poky-ivi-systemd.conf gemini-image audiomanager layer-management obexd multimedia common-api graphics dlt-daemon node-startup-controller connectivity node-state-manager extended ecryptfs-utils support fuse keyutils meta-ivi GENIVI OSS Projects libical 16 | © 2013 Wind River. All Rights Reserved. Setup Build Environment . mkdir $HOME/yocto-genivi-baseline . cd $HOME/yocto-genivi-baseline . git clone git://git.yoctoproject.org/poky . cd poky; git checkout dora; cd - . git clone git://git.yoctoproject.org/meta-ivi . cd meta-ivi; git checkout 5.0; cd . source poky/oe-init-build-env . $EDITOR conf/bblayers.conf . $EDITOR conf/local.conf 17 | © 2013 Wind River. All Rights Reserved. Setup Build Environment – local.conf Add to the end of the file (conf/local.conf) INCOMPATIBLE_LICENSE = "GPLv3" DISTRO = "poky-ivi-systemd" BB_NUMBER_THREADS = “8" PARALLEL_MAKE = "-j 8" #MACHINE = "vexpressa9" #MACHINE = "qemux86-64" MACHINE = "qemux86" 18 | © 2013 Wind River. All Rights Reserved. Setup Build Environment – bblayers.conf . Add the meta-ivi and meta-ivi-bsp path to the $BUILDDIR/conf/bblayers.conf BBLAYERS variable. # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf # changes incompatibly LCONF_VERSION = "6" BBPATH = "${TOPDIR}" BBFILES ?= "" BBLAYERS ?= " \ /var/lib/jenkins/yocto-genivi-baseline/poky/meta \ /var/lib/jenkins/yocto-genivi-baseline/poky/meta-yocto \ /var/lib/jenkins/yocto-genivi-baseline/poky/meta-yocto-bsp \ /var/lib/jenkins/yocto-genivi-baseline/meta-ivi \ /var/lib/jenkins/yocto-genivi-baseline/meta-ivi/meta-ivi-bsp \ " BBLAYERS_NON_REMOVABLE ?= " \ /var/lib/jenkins/yocto-genivi-baseline/poky/meta \ /var/lib/jenkins/yocto-genivi-baseline/poky/meta-yocto \ " 19 | © 2013 Wind River. All Rights Reserved. Build Yocto GENIVI Basline Image Build gemini-image including GENIVI 5.0 (Gemini) components . bitbake gemini-image Depending on your internet connection (most all of the sources are downloaded), and the configuration of your build machine, this make take time. https://wiki.yoctoproject.org/wiki/Build_Performance 20 | © 2013 Wind River. All Rights Reserved. Parsing recipes...done. Parsing of 877 .bb files complete (0 cached, 877 parsed). 1207 targets, 78 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.20.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-12.04" TARGET_SYS = "i586-poky-linux" MACHINE = "qemux86" DISTRO = "poky-ivi-systemd" DISTRO_VERSION = "5.0.0" TUNE_FEATURES = "m32 i586" TARGET_FPU = "" meta meta-yocto meta-yocto-bsp = "dora:4d8ab87d25ea6e59dc88375813ef88ee0ac813d0" meta-ivi meta-ivi-bsp = "5.0:a18d27d3716706dcf036f88acce96900bc0641b8" NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks […] NOTE: recipe gemini-image-5.0.0-r0: task do_populate_lic: Started NOTE: recipe gemini-image-5.0.0-r0: task do_rootfs: Started NOTE: recipe gemini-image-5.0.0-r0: task do_populate_lic: Succeeded NOTE: recipe gemini-image-5.0.0-r0: task do_rootfs: Succeeded NOTE: Running noexec task 4099 of 4099 (ID: 12, /var/lib/jenkins/yocto-genivi-baseline/meta-ivi/recipes- yocto-ivi/images/gemini-image.bb, do_build) NOTE: Tasks Summary: Attempted 4099 tasks of which 342 didn't need to be rerun and all succeeded. Summary: There were 3 WARNING messages shown. 21 | © 2013 Wind River. All Rights Reserved. Yocto GENIVI Baseline – Run Emulator . QEMU (ARMv7) – emulated machine: vexpressa9 $HOME/yocto-genivi-baseline/meta-ivi/scripts/runqemu \ gemini-image vexpressa9 . QEMU (IA-32) – emulated machine: qemux86 $HOME/yocto-genivi-baseline/poky/scripts/runqemu \ gemini-image qemux86 . QEMU (x86-64) – emulated machine:
Recommended publications
  • Linux Foundation to Host Meego Workgroup

    Linux Foundation to Host Meego Workgroup

    Linux Foundation To Host MeeGo Workgroup New Open Source Software Platform Backed by Intel and Nokia will Power the Next Generation of Computing Devices SAN FRANCISCO, February 15, 2010 – The Linux Foundation, the nonprofit organization dedicated to accelerating the growth of Linux, today announced it will host the MeeGo project, the open source software platform for the next generation of computing devices. MeeGo combines Intel’s Moblin™ and Nokia’s Maemo projects into one Linux-based platform. MeeGo, announced today in a joint release by Intel and Nokia, will be deployed across many computing device types - including pocketable mobile computers, netbooks, tablets, mediaphones, connected TVs and in-vehicle infotainment systems, and brings together the leaders in computing and mobile communications as the project’s backers. MeeGo is designed for cross-device, cross-architecture computing and is built from the ground up for a new class of powerful computing devices. The workgroup will be hosted by the Linux Foundation as a fully open source project, encouraging community contributions in line with the best practices of the open source development model. The Linux Foundation expects MeeGo to be adopted widely by device manufacturers, network operators, software vendors and developers across multiple device types and for many organizations and developers to participate in the workgroup. “With MeeGo, you have the world’s leader in computing – Intel – uniting with the world’s leader in communications – Nokia – in a true open source project hosted at the Linux Foundation,” said Jim Zemlin, executive director at the Linux Foundation. “MeeGo has been built from the ground up for rich, mobile devices and will deliver choice to consumers without lock-in.
  • Creating a Custom Embedded Linux Distribution for Any Embedded

    Creating a Custom Embedded Linux Distribution for Any Embedded

    Yocto Project Summit Intro to Yocto Project Creating a Custom Embedded Linux Distribution for Any Embedded Device Using the Yocto Project Behan Webster Tom King The Linux Foundation May 25, 2021 (CC BY-SA 4.0) 1 bit.ly/YPS202105Intro The URL for this presentation http://bit.ly/YPS202105Intro bit.ly/YPS202105Intro Yocto Project Overview ➢ Collection of tools and methods enabling ◆ Rapid evaluation of embedded Linux on many popular off-the-shelf boards ◆ Easy customization of distribution characteristics ➢ Supports x86, ARM, MIPS, Power, RISC-V ➢ Based on technology from the OpenEmbedded Project ➢ Layer architecture allows for other layers easy re-use of code meta-yocto-bsp meta-poky meta (oe-core) 3 bit.ly/YPS202105Intro What is the Yocto Project? ➢ Umbrella organization under Linux Foundation ➢ Backed by many companies interested in making Embedded Linux easier for the industry ➢ Co-maintains OpenEmbedded Core and other tools (including opkg) 4 bit.ly/YPS202105Intro Yocto Project Governance ➢ Organized under the Linux Foundation ➢ Split governance model ➢ Technical Leadership Team ➢ Advisory Board made up of participating organizations 5 bit.ly/YPS202105Intro Yocto Project Member Organizations bit.ly/YPS202105Intro Yocto Project Overview ➢ YP builds packages - then uses these packages to build bootable images ➢ Supports use of popular package formats including: ◆ rpm, deb, ipk ➢ Releases on a 6-month cadence ➢ Latest (stable) kernel, toolchain and packages, documentation ➢ App Development Tools including Eclipse plugin, SDK, toaster 7
  • Linux Automotive Security “Safer and More Secure”

    Linux Automotive Security “Safer and More Secure”

    Linux Automotive Security “Safer and more secure” Authors Fulup Ar Foll [email protected] José Bollo [email protected] Abstract Cars are expensive pieces of equipment, yet they represent a huge mass market. Adding Internet connectivity to previous elements generates perfect conditions for the growth of a viable business model on attacking “Connected Cars”. It is already well understood that cars will be connected and connected cars will be attacked. While it's still too early to predict with certainty how “Connected Cars” will be impacted by security flaws, making the assumption that a car should be at least as secure as a TV, a set-top-box or a smart phone should make sense to everyone. This white paper focuses on how Linux best practices security mechanisms that could be used today and within the next couple of years to make connected cars safer and more secure. Version 1.0 January 2016 Linux Automotive Security Table of contents 1.Introduction...................................................................................................3 2.Make Sure You Run the Right Code...................................................................4 2.1.Before Booting............................................................................................4 2.2.When Booting.............................................................................................5 2.3.After Booting...............................................................................................5 3.Keeping Secrets Secret...................................................................................6
  • System Collaboration and Information Sharing Through Internet of Things

    System Collaboration and Information Sharing Through Internet of Things

    System collaboration and information sharing through Internet of Things Mälardalens Högskola School of Innovation, Design and Engineering Maja Grubisic [email protected] Tina Marsic [email protected] Thesis for the Degree of Master of Computer Science – Software Engineering 30.0 credits June, 2015. Examiner: Ivica Crnkovic Supervisors: Hongyu Pei-Breivold Mälardalens Högskola Kristian Sandström ABB AB, Corporate Research Larisa Rizvanovic ABB AB, Corporate Research Abstract The focus of this thesis is realization of system collaboration and information sharing between devices through Internet of Things. Internet of Things is a network of things, where a thing can be any device capable of acquiring an IP address. Internet of Things has been discussed in many domains. Companies are exploring the full potential of it, with the purpose of automating their services and optimizing their productivity. In this thesis we have conducted a systematic research review to investigate the existing Internet of Things solutions with respect to system collaboration and information sharing through Internet of Things. We have also implemented a prototype, using Arduino microprocessors and NUCs, to illustrate system collaboration and information sharing between the two systems. II Table of Contents 1 Introduction ............................................................................................................................................. 1 1.1 Internet of Things ........................................................................................................................
  • <Document Title>

    <Document Title>

    DATE OSS Disclosure Document th CM_CI1 11 feb 2021 OSS Licenses used in RN_AIVI Project This document is provided as part of the fulfillment of OSS license conditions and does not require users to take any action before or while using the product. Page 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS PRIVATE LIMITED. Without their consent, it may not be reproduced or given to third parties DATE OSS Disclosure Document th CM_CI1 11 feb 2021 Table of Contents Contents 1 List of used Open Source Components. ............................................................................................... 6 2 Appendix - License Text ................................................................................................................. 56 2.1 BSD-4-Clause (University of California-Specific) ............................................................. 56 2.2 Academic Free Licensev. 2.1 ............................................................................................. 57 2.3 Academic Free License v1.1 .............................................................................................. 59 2.4 Apache License 1.1 ........................................................................................................... 60 2.5 Apache License 2.0 ........................................................................................................... 62 2.6 Apple Public Source License 1.1 ....................................................................................... 65 2.7
  • Ofono Open-Source Telephony

    Ofono Open-Source Telephony

    oFono Open-source telephony R´emiDenis-Courmont Aki Niemi Nokia Devices R&D Maemo Software Maemo summit 2009 - October 10th 2009 R´emiDenis-Courmont Nokia oFono Outline 1 A brief history of Linux telephony 2 Nokia N900 3 oFono R´emiDenis-Courmont Nokia oFono A brief history of Linux telephony Nokia N900 oFono Outline 1 A brief history of Linux telephony 2 Nokia N900 3 oFono R´emiDenis-Courmont Nokia oFono voice calls Short Message Service (SMS) location supplementary services General packet radio service (GPRS) ... A brief history of Linux telephony Nokia N900 oFono What's (cellular) telephony? network status network selection SIM security (PIN, PUK. ) SIM phone book R´emiDenis-Courmont Nokia oFono A brief history of Linux telephony Nokia N900 oFono What's (cellular) telephony? network status network selection SIM security (PIN, PUK. ) SIM phone book voice calls Short Message Service (SMS) location supplementary services General packet radio service (GPRS) ... R´emiDenis-Courmont Nokia oFono designed in the seventies. originally for 300 bauds fixed serial line ASCII awkward multiplexing PPP (binary) for backward-compatibility A brief history of Linux telephony Nokia N900 oFono The standard (?) Hayes commands set ITU V.250 3GPP 27.007 better known as AT commands R´emiDenis-Courmont Nokia oFono awkward multiplexing PPP (binary) for backward-compatibility A brief history of Linux telephony Nokia N900 oFono The standard (?) Hayes commands set ITU V.250 3GPP 27.007 better known as AT commands designed in the seventies. originally for 300 bauds fixed serial line ASCII R´emiDenis-Courmont Nokia oFono A brief history of Linux telephony Nokia N900 oFono The standard (?) Hayes commands set ITU V.250 3GPP 27.007 better known as AT commands designed in the seventies.
  • Strong Momentum Continues by Egil Juliussen The

    Strong Momentum Continues by Egil Juliussen The

    GENIVI: Strong Momentum Continues By Egil Juliussen The GENIVI Alliance had its membership meeting in Shanghai in mid-October. IHS Automotive was invited as part of their analyst track and was asked to give perspectives on HMI and apps for auto infotainment. This is the fourth time we have attended and given a presentation at the GENIVI Alliance meeting. We have previously been asked to do presentations on Software Security and HTML5 Infotainment Impact. Does this mean that GENIVI is now focusing on HMI technologies and/or a HMI framework? This impression will update a previous version that was done in November 2011 and will focus on the following topics: • What is new with GENIVI? • How does GENIVI compete with other OS platforms? • What is the outlook for GENIVI success? What is new with GENIVI? The GENIVI Alliance is a non-profit organization that is developing a software platform for in-vehicle infotainment (IVI) systems that uses Open Source Software (OSS) business model. The software platform is based on the Linux operating system (Version 2.6 Kernel) and additional middleware that are needed for running automotive infotainment applications in head-units, telematics and navigation systems. The GENIVI platform can be based on any Linux distribution, but a major goal of GENIVI is to avoid fragmentation of Linux in automotive systems—hence the compliance program. To assure a high level of compatibility between Linux versions, GENIVI released its first edition of the compliance testing program in August 2011 after 14-months of development. The second version of the compliance testing program was announced this spring and the third compliance version was announced in Shanghai this October.
  • Pressemitteilung

    Pressemitteilung

    Pressemitteilung Zur sofortigen Veröffentlichung GENIVI Alliance stellt Konformitätsprogramm für Mitglieder vor Erste fünf GENIVI-konforme Lösungen anerkannt SAN RAMON, Kalifornien, USA - 2. August 2011 - The GENIVI Alliance, ein Branchenverband der Automobil- und Unterhaltungselektronikindustrie, der sich für die Entwicklung und Einführung einer offenen Referenzplattform für Infotainment in Fahrzeugen (IVI – In-Vehicle Infotainment) einsetzt, stellte heute sein neu entwickeltes Konformitätsprogramm für seine Mitgliedsunternehmen vor. Dieses Programm ist das Ergebnis 14-monatiger akribischer Forschungs- und Untersuchungsbemühungen von GENIVI-„Expertengruppen“ – mit umfassender Beteiligung aller Mitglieder – zur Aufstellung einer Bandbreite detaillierter technischer Anforderungen. Die GENIVI-Miglieder Canonical, Mentor Graphics, MontaVista und Wind River sowie die Linux Foundation sind die ersten mit „GENIVI-konform“ anerkannten Angeboten, was sie für OEM- Ausschreibungen mit GENIVI-konformen Produkten qualifiziert. „Dieses Programm verkörpert den natürlichen Ablauf innerhalb der GENIVI Alliance von zielgerichteten Anforderungen über identifizierte Komponenten, die diesen Anforderungen gerecht werden, bis hin zu einer kompakten wiederverwendbaren Plattform“, sagte Steve Crumb, Executive Director der GENIVI Alliance. „Das Programm klärt, was von Mitgliedern erwartet wird, die konforme Softwarelösungen anbieten wollen.“ „Jaguar Land Rover und andere Automobil-OEMs und GENIVI-Mitglieder geben jetzt die GENIVI-Konformität in ihren Ausschreibungen
  • Understanding D-Bus

    Understanding D-Bus

    Meetup Toulouse, May 2016 Understanding D-Bus Myl`eneJosserand [email protected] © Copyright 2004-2018, Bootlin. embedded Linux and kernel engineering Creative Commons BY-SA 3.0 license. Corrections, suggestions, contributions and translations are welcome! - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 1/1 What is this talk about? I D-Bus generality & IPC I The D-Bus principles I Differents tools and libraries with demo I Different projects using D-Bus I A short use case with Connman and Ofono - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 2/1 Understanding D-Bus D-Bus generality - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 3/1 D-Bus I Created in 2002 I Is part of the freedesktop.org project I Maintained by RedHat and the community I Is an Inter-process communication mechanism I Initiated to standardize services of Linux desktop environments - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 4/1 Inter-Process Communication (IPC) I Mechanisms allowing processes to communicate with each other I Shared memory: read/write into a defined memory location I Memory-mapped file: same as shared memory but uses a file I Pipe: two-way data stream (standard input / output) I Named pipe: same as pipe but uses a file (FIFO) I Socket: communication even on distant machines I and others - Kernel, drivers and embedded
  • Hypervisors in the Vehicle: a Standards-Based Approach to Virtualization

    Hypervisors in the Vehicle: a Standards-Based Approach to Virtualization

    Hypervisors in the vehicle: A standards-based approach to virtualization A report based on the webinar by Automotive World and GENIVI Alliance. The webinar which was broadcast in February of ! ! is still available for download " see #$%. It however had some poor audio &uality in some parts. A better recordin' is now available at #$% but some may still prefer to 'et this information in written form. The document is not an e(act transcript of the webinar) but it is close. The content and messa'e is the same, and the information is presented here to'ether with the correspondin' presentation slides from the webinar) with the followin' adjustments: , -ommon spo.en e(pressions have been e(chan'ed for more typical written lan'ua'e to reach more typical written &uality. , /inor clarifications and some lost details have been added. , A few chapters are e(tended and elaborate on details that did not 0t within the time of the webinar , For the 1&A session, more thou'htful and complete answers to 'iven &uestions can be 'iven, now that there is time to formulate the answers. Also) the section presented by Tero 3alminen from 4pen3yner'y has a 'ood &uality audio in the recordin') and is not included in te(t form in this document. The 0rst part of the presentation was done by Gunnar Andersson 5GENIVI Technical 6ead7) who is also the author of this text. We promised to address a &uestion in this webinar : 8Is there a need for a more standards-based approach for deployin' hypervisors in the vehicle?: , to ensure that automotive requirements are met, , to reduce risk and concerns amon' adopters of virtualization) , to promote portability, , and to minimize system integration effort.
  • Wind River Linux Release Notes, 5.0.1

    Wind River Linux Release Notes, 5.0.1

    Wind River Linux Release Notes, 5.0.1 Wind River® Linux RELEASE NOTES 5.0.1 Copyright © 2013 Wind River Systems, Inc. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means without the prior written permission of Wind River Systems, Inc. Wind River, Tornado, and VxWorks are registered trademarks of Wind River Systems, Inc. The Wind River logo is a trademark of Wind River Systems, Inc. Any third-party trademarks referenced are the property of their respective owners. For further information regarding Wind River trademarks, please see: www.windriver.com/company/terms/trademark.html This product may include software licensed to Wind River by third parties. Relevant notices (if any) are provided in your product installation at one of the following locations: installDir/product_name/3rd_party_licensor_notice.pdf installDir/legal-notices/ Wind River may refer to third-party documentation by listing publications or providing links to third-party Web sites for informational purposes. Wind River accepts no responsibility for the information provided in such third-party documentation. Corporate Headquarters Wind River 500 Wind River Way Alameda, CA 94501-1153 U.S.A. Toll free (U.S.A.): 800-545-WIND Telephone: 510-748-4100 Facsimile: 510-749-2010 For additional contact information, see the Wind River Web site: www.windriver.com For information on how to contact Customer Support, see: www.windriver.com/support Wind River Linux Release Notes 5.0.1 4 Apr 13 Contents 1 Overview ...................................................................................................... 1 1.1 Introduction ...................................................................................................................... 1 1.2 Navigating these Release Notes ................................................................................... 1 1.3 Features ............................................................................................................................
  • Trademarks and Licenses Trademarks and Licenses

    Trademarks and Licenses Trademarks and Licenses

    Trademarks and Licenses Trademarks and Licenses Bluetooth® Wireless Technology The Bluetooth Wireless Technology word mark and logos are registered trademarks owned by Bluetooth Wireless Technology SIG, Inc. HD Radio™ Technology Program Info Program Info provides song name, artist, station ID, and other relevant data to the receiver. Digital Sound HD Radio broadcasts deliver crystal clear digital audio quality to consumers. HD2/HD3 Adjacent to traditional main stations are HD2/HD3 Channels, providing new original formats on the FM dial. Artist Experience: Visual images, such as album art and station logos, of over-the-air broadcasts from HD Radio stations. 171 Specification Specification AV product specification Operating Temper -20 ℃ ~ +65 ℃ Common Storage Temperature -30 ℃ ~ +75 ℃ Supported Profile HFP 1.6, A2DP 1.2, AVRCP 1.5, PBAP 1.1 Supported Bluetooth 3.0 Specification Bluetooth Frequency Range 2402 MHz ~ 2480 MHz Number of Channels 79 AM ME : 522 kHz~1620 kHz SA : 522 kHz~1620 kHz Tuning Range ESA : 531 kHz~1602 kHz MX : 530 kHz~1710 kHz Sensitivity 35 dBuV Signal-to-noise ratio Minimum 45 dB Radio FM ME : 87.5 MHz~108.0 MHz SA : 87.5 MHz~108.0 MHz Tuning Range ESA : 87.5 MHz~108.0 MHz MX : 87.5 MHz~107.9 MHz Sensitivity 12 dBuV Frequency response 30 Hz ~ 10000 Hz Signal-to-noise ratio Minimum 45 dB ↟ Designs and specifications are subject to change without prior notice. WiFi Frequency Range(FCC) : 2412-2462MHz 5180-5240MHz 5745-5825MHz Frequency Range( CE ) : 2412-2472MHz 5180-5240MHz 5745-5825MHz Specification : IEEE802.11 a/b/g/n/ac Supported Bandwidth : 20MHz, 40MHz, 80MHz 172 Open Source Software Notice Open Source Software Notice This product contains the open source software detailed below.