DOCSLIB.ORG

Embedded Android

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

www.it-ebooks.info www.it-ebooks.info Praise for Embedded Android “This is the definitive book for anyone wanting to create a system based on Android. If you don’t work for Google and you are working with the low-level Android interfaces, you need this book.” —Greg Kroah-Hartman, Core Linux Kernel Developer “If you or your team works on creating custom Android images, devices, or ROM mods, you want this book! Other than the source code itself, this is the only place where you’ll find an explanation of how Android works, how the Android build system works, and an overall view of how Android is put together. I especially like the chapters on the build system and frameworks (4, 6, and 7), where there are many nuggets of information from the AOSP source that are hard to reverse-engineer. This book will save you and your team a lot of time. I wish we had it back when our teams were starting on the Frozen Yogurt version of Android two years ago. This book is likely to become required reading for new team members working on Intel Android stacks for the Intel reference phones.” —Mark Gross, Android/Linux Kernel Architect, Platform System Integration/Mobile Communications Group/Intel Corporation “Karim methodically knocks out the many mysteries Android poses to embedded system developers. This book is a practical treatment of working with the open source software project on all classes of devices, beyond just consumer phones and tablets. I’m personally pleased to see so many examples provided on affordable hardware, namely BeagleBone, not just on emulators.” —Jason Kridner, Sitara Software Architecture Manager at Texas Instruments and cofounder of BeagleBoard.org “This book contains information that previously took hundreds of hours for my engineers to discover. It is required reading for any new person that is working with Android on my team.” —Dr. Mark Micire, Researcher in Space and Mobile Field Robotics, Carnegie Mellon University www.it-ebooks.info “Thanks to this book, for the first time embedded system developers have access to an open and vertically integrated stack that contains everything they need to build robust and high- performing Linux-based products. Android’s revolutionary execution model transcends phones and tablets, and its application developer platform is unmatched in the industry for features and development speed. This book will give developers a valuable resource for understanding everything between the application layer and the kernel, and how to extend and change things to create an infinite variety of Androids.” —Zach Pfeffer, Tech Lead for Linaro’s Android team “Finally, a book on the Android platform from a systems perspective! There are plenty of books on creating Android applications, but for too long no single, comprehensive source for information on Android’s internals. In Embedded Android, Karim has collected a vast quantity of material that is essential and helpful for Android systems programmers and integrators (although, to be sure, application developers would benefit from a reading as well). Karim’s copious examples, references, and explanations are gleaned from his extensive experience with and analysis of Android. It’s the book I wish I had had when I walked my own trail of tears learning Android for work at Sony. With this book, I could have saved myself months learning the ins and outs of Android. No doubt this will be the canonical reference book for Android system developers for years to come.” —Tim Bird, Senior Staff Engineer, Sony Network Entertainment, and Architecture Group Chair, CE Workgroup of the Linux Foundation “Karim Yaghmour’s book is an excellent guide for those wishing to get into the burgeoning field of Android-based embedded projects and products. The book covers the full range from kernel support through licensing and trademark issues, including information on running Android systems in “headless” mode as well. This book deserves a place on every serious embedded Android developer’s bookshelf.” —Paul E. McKenney, IBM Distinguished Engineer and Linux Kernel RCU Maintainer “Although Android is officially designed for mobile and tablet segments, it’s unquestionably getting considered for many other product segments, like automotive, UI panels like HMI, wearable gadgets, and so on. This book is highly recommended, as it covers all the essential fundamentals and concepts that help developers port and develop Android-based solutions for both mobile and nonmobile product segments.” —Khasim Syed Mohammed, Lead Engineer, Texas Instruments www.it-ebooks.info “A great resource not only for embedded Android developers, but also for Android app developers to learn the wiring below the Java surface.” —Lars Vogel, CEO, vogella GmbH “Once again, Karim has hit the nail on the head. If you’re interested in porting Android to a new device or just interested in the guts of how Android runs on a piece of hardware, this is the book you’ve been searching for. This book leads you through all of the facets of build- environment setup, getting the AOSP sources, adding your hardware to the Android sources and deploying a new Android build to the hardware. It discusses the underpinnings of Android including the HAL and how to give your custom hardware support within the Android framework. In short, of all the books on Android, this is the one book that targets the Android device builder rather than Android application developer or end user. I just wish this book would have been available when I first got into Android porting. It could have saved me months of trial and error efforts.” —Mike Anderson, Chief Scientist, The PTR Group, Inc. “Embedded Android has been a great resource for our company. It is a must-have when porting Android to new hardware or integrating new features at a low level. Karim is a great instructor, and his writing captures his style well.” —Jim Steele, VP of Engineering, Sensor Platforms “Embedded Android is a must-read for anyone who wants to seriously work the Android internals and bring up Android on new platforms. It helps in navigating the extensive AOSP codebase, and understanding the overall architecture and design of the system.” —Balwinder Kaur, Senior Member, Technical Staff, Aptina Imaging “So you thought you knew about Android internals? Well, think again! Chapter after chapter, you’ll discover what’s behind the scenes and why Android is not just another embedded Linux distribution. Get yourself ready for stepping into a whirlpool, ’cause Embedded Android is a gold mine for anyone looking to do serious hacking on Google’s OS.” —Benjamin Zores, Android Platform Architect, Alcatel-Lucent www.it-ebooks.info “Definitely one of the most valuable and complete resources about the Android system stack. A must-have for every Android system engineer.” —Maxime Ripard, Android Lead, Free Electrons “When I was handed a development board running Linux, and was told to ‘get Android running on it,’ it was difficult to find much information about how to bring Android up on a new device. Luckily for me, Embedded Android became available about the same time that I was beginning development. What a lifesaver! Embedded Android gave me the kick- start I needed to understand the underpinnings of Android and what I would need to do to bring Android up on a new piece of hardware. I loved all the details and background, from the boot sequence to the build system. After having read Embedded Android, I felt I had a much better grasp of Android and how it interacted with the Linux kernel.” —Casey Anderson, Embedded Systems Architect, Trendril www.it-ebooks.info Embedded Android Karim Yaghmour www.it-ebooks.info Embedded Android by Karim Yaghmour Copyright © 2013 Karim Yaghmour. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/ institutional sales department: 800-998-9938 or [email protected]. Editors: Andy Oram and Mike Hendrickson Indexer: Bob Pfahler Production Editor: Kara Ebrahim Cover Designer: Randy Comer Copyeditor: Rebecca Freed Interior Designer: David Futato Proofreader: Julie Van Keuren Illustrator: Rebecca Demarest March 2013: First Edition Revision History for the First Edition: 2013-03-11: First release See http://oreilly.com/catalog/errata.csp?isbn=9781449308292 for release details. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Embedded Android, the image of a Moorish wall gecko, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc., was aware of a trade‐ mark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. ISBN: 978-1-449-30829-2 [LSI] www.it-ebooks.info To Anaïs, Thomas, and Vincent. May your journeys be filled with the joys of sharing and discovery. www.it-ebooks.info www.it-ebooks.info Table of Contents Preface. xi 1. Introduction. 1 History 1 Features and Characteristics 2 Development Model 5 Differences From “Classic” Open Source Projects 5 Feature Inclusion, Roadmaps, and New Releases 7 Ecosystem 7 A Word on the Open Handset Alliance 8 Getting “Android” 9 Legal Framework 10 Code Licenses 10 Branding Use 13 Google’s Own Android Apps 15 Alternative App Markets 15 Oracle versus Google 15 Mobile Patent Warfare 16 Hardware and Compliance Requirements 17 Compliance Definition Document 18 Compliance Test Suite 21 Development Setup and Tools 22 2.
Recommended publications
  • AVG Android App Performance and Trend Report H1 2016

    AVG Android App Performance and Trend Report H1 2016

    AndroidTM App Performance & Trend Report H1 2016 By AVG® Technologies Table of Contents Executive Summary .....................................................................................2-3 A Insights and Analysis ..................................................................................4-8 B Key Findings .....................................................................................................9 Top 50 Installed Apps .................................................................................... 9-10 World’s Greediest Mobile Apps .......................................................................11-12 Top Ten Battery Drainers ...............................................................................13-14 Top Ten Storage Hogs ..................................................................................15-16 Click Top Ten Data Trafc Hogs ..............................................................................17-18 here Mobile Gaming - What Gamers Should Know ........................................................ 19 C Addressing the Issues ...................................................................................20 Contact Information ...............................................................................21 D Appendices: App Resource Consumption Analysis ...................................22 United States ....................................................................................23-25 United Kingdom .................................................................................26-28
  • ART Vs. NDK Vs. GPU Acceleration: a Study of Performance of Image Processing Algorithms on Android

    ART Vs. NDK Vs. GPU Acceleration: a Study of Performance of Image Processing Algorithms on Android

    DEGREE PROJECT IN COMPUTER SCIENCE AND ENGINEERING, SECOND CYCLE, 30 CREDITS STOCKHOLM, SWEDEN 2017 ART vs. NDK vs. GPU acceleration: A study of performance of image processing algorithms on Android ANDREAS PÅLSSON KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF COMPUTER SCIENCE AND COMMUNICATION ART vs. NDK vs. GPU acceleration: A study of performance of image processing algorithms on Android ANDREAS PÅLSSON Master in Computer Science Date: June 26, 2017 Supervisor: Cyrille Artho Examiner: Johan Håstad Swedish title: ART, NDK eller GPU acceleration: En prestandastudie av bildbehandlingsalgoritmer på Android School of Computer Science and Communication iii Abstract The Android ecosystem contains three major platforms for execution suit- able for different purposes. Android applications are normally written in the Java programming language, but computationally intensive parts of An- droid applications can be sped up by choosing to use a native language or by utilising the parallel architecture found in graphics processing units (GPUs). The experiments conducted in this thesis measure the performance benefits by switching from Java to C++ or RenderScript, Google’s GPU acceleration framework. The experiments consist of often-done tasks in image processing. For some of these tasks, optimized libraries and implementations already exist. The performance of the implementations provided by third parties are compared to our own. Our results show that for advanced image processing on large images, the benefits are large enough to warrant C++ or RenderScript usage instead of Java in modern smartphones. However, if the image processing is conducted on very small images (e.g. thumbnails) or the image processing task contains few calculations, moving to a native language or RenderScript is not worth the added development time and static complexity.
  • Linux Hardware Compatibility HOWTO

    Linux Hardware Compatibility HOWTO

    Linux Hardware Compatibility HOWTO Steven Pritchard Southern Illinois Linux Users Group [email protected] 3.1.5 Copyright © 2001−2002 by Steven Pritchard Copyright © 1997−1999 by Patrick Reijnen 2002−03−28 This document attempts to list most of the hardware known to be either supported or unsupported under Linux. Linux Hardware Compatibility HOWTO Table of Contents 1. Introduction.....................................................................................................................................................1 1.1. Notes on binary−only drivers...........................................................................................................1 1.2. Notes on commercial drivers............................................................................................................1 1.3. System architectures.........................................................................................................................1 1.4. Related sources of information.........................................................................................................2 1.5. Known problems with this document...............................................................................................2 1.6. New versions of this document.........................................................................................................2 1.7. Feedback and corrections..................................................................................................................3 1.8. Acknowledgments.............................................................................................................................3
  • Apollo Twin USB Hardware Manual

    Apollo Twin USB Hardware Manual

    Apollo Twin USB Hardware Manual Manual Version 210429 www.uaudio.com A Letter from Bill Putnam Jr. Thank you for deciding to make the Apollo Twin High-Resolution Interface part of your music making experience. We know that any new piece of gear requires an investment of time and money — and our goal is to make your investment pay off. The fact that we get to play a part in your creative process is what makes our efforts meaningful, and we thank you for this. In many ways, the Apollo family of audio interface products represent the best examples of what Universal Audio has stood for over its long history; from UA’s original founding in the 1950s by my father, through our current vision of delivering the best of both analog and digital audio technologies. Starting with its high-quality analog I/O, Apollo Twin’s superior sonic performance serves as its foundation. This is just the beginning however, as Apollo Twin is the only desktop audio interface that allows you to run UAD plug-ins in real time. Want to monitor yourself through a Neve® console channel strip while tracking bass through a classic Fairchild or LA-2A compressor? Or how about tracking vocals through a Studer® tape machine with some added Lexicon® reverb?* With our growing library of more than 90 UAD plug-ins, the choices are limitless. At UA, we are dedicated to the idea that this powerful technology should ultimately serve the creative process — not be a barrier. These are the very ideals my father embodied as he invented audio equipment to solve problems in the studio.
  • TECHNICAL MANUAL of Intel H110 Express Chipset Based Mini-ITX

    TECHNICAL MANUAL of Intel H110 Express Chipset Based Mini-ITX

    TECHNICAL MANUAL Of Intel H110 Express Chipset Based Mini-ITX M/B NO. G03-NF693-F Revision: 3.0 Release date: July 19, 2017 Trademark: * Specifications and Information contained in this documentation are furnished for information use only, and are subject to change at any time without notice, and should not be construed as a commitment by manufacturer. Environmental Protection Announcement Do not dispose this electronic device into the trash while discarding. To minimize pollution and ensure environment protection of mother earth, please recycle. i TABLE OF CONTENT ENVIRONMENTAL SAFETY INSTRUCTION ...................................................................... iii USER’S NOTICE .................................................................................................................. iv MANUAL REVISION INFORMATION .................................................................................. iv ITEM CHECKLIST ................................................................................................................ iv CHAPTER 1 INTRODUCTION OF THE MOTHERBOARD 1-1 FEATURE OF MOTHERBOARD ................................................................................ 1 1-2 SPECIFICATION ......................................................................................................... 2 1-3 LAYOUT DIAGRAM .................................................................................................... 3 CHAPTER 2 HARDWARE INSTALLATION 2-1 JUMPER SETTING ....................................................................................................
  • NSA ANT Catalog PDF from EFF.Org

    NSA ANT Catalog PDF from EFF.Org

    SECRET//COMINT//REL TO USA. FVEY DEITYBOUNCE ANT Product Data (TS//SI//REL) DEITYBOUNCE provides software application persistence on Dell PowerEdge servers by exploiting the motherboard BIOS and utilizing System Management Mode (SMM) to gain periodic execution while the Operating System loads. _________________ _________________________________________ TUMI KG FORK Post Proc*t*ftg Target Systems (TS//SM/REL) DEITYBOUNCE Extended Concept ot Operations (TS//SI//REL) This technique supports multi-processor systems with RAID hardware and Microsoft Windows 2000. 2003. and XP. It currently targets Dell PowerEdge A A 1850/2850/1950/2950 RAID servers, using BIOS versions A02. A05. A 0 6 .1.1.0. " " 1.2.0. or 1.3.7. (TS//SI//REL) Through remote access or interdiction. ARKSTREAM is used to re­ flash the BIOS on a target machine to implant DEITYBOUNCE and its payload (the implant installer). Implantation via interdiction may be accomplished by non­ technical operator though use of a USB thumb drive. Once implanted. DEITYBOUNCE's frequency of execution (dropping the payload) is configurable and will occur when the target machine powers on. Status: Released / Deployed. Ready for Unit Cost: $0 Immediate Delivery POC: S32221. | Oenverl From: NSAfCSSM 1-52 Dated: 20070108 Oeclaisify On: 20320108 SECRET//COMINT//REL TO USA. FVEY TOP SECRET//COMINT//REL TO USA. FVEY IRONCHEF ANT Product Data (TS//SI//REL) IRONCHEF provides access persistence to target systems by exploiting the motherboard BIOS and utilizing System Management Mode (SMM) to 07/14/08 communicate with a hardware implant that provides two-way RF communication. CRUMPET COVERT CLOSED NETWORK NETW ORK (CCN ) (Tefgef So*col CCN STRAITBIZAKRE N ode Compute* Node r -\— 0 - - j CCN S e rv e r STRAITBIZARRE Node CCN Computer UNITCORAKt Computer Node I Futoie Nodoe UNITE ORA KE Server Node I (TS//SI//REL) IRONCHEF Extended Concept of Operations (TS//SI/REL) This technique supports the HP Proliant 380DL G5 server, onto which a hardware implant has been installed that communicates over the l?C Interface (WAGONBED).
  • Defending Against Malicious Peripherals with Cinch Sebastian Angel, the University of Texas at Austin and New York University; Riad S

    Defending Against Malicious Peripherals with Cinch Sebastian Angel, the University of Texas at Austin and New York University; Riad S

    Defending against Malicious Peripherals with Cinch Sebastian Angel, The University of Texas at Austin and New York University; Riad S. Wahby, Stanford University; Max Howald, The Cooper Union and New York University; Joshua B. Leners, Two Sigma; Michael Spilo and Zhen Sun, New York University; Andrew J. Blumberg, The University of Texas at Austin; Michael Walfish, New York University https://www.usenix.org/conference/usenixsecurity16/technical-sessions/presentation/angel This paper is included in the Proceedings of the 25th USENIX Security Symposium August 10–12, 2016 • Austin, TX ISBN 978-1-931971-32-4 Open access to the Proceedings of the 25th USENIX Security Symposium is sponsored by USENIX Defending against malicious peripherals with Cinch ⋆ Sebastian Angel, † Riad S. Wahby,‡ Max Howald,§† Joshua B. Leners,∥ ⋆ Michael Spilo,† Zhen Sun,† Andrew J. Blumberg, and Michael Walfish† ⋆ The University of Texas at Austin †New York University ‡Stanford University §The Cooper Union ∥Two Sigma Abstract Rushby’s separation kernel [129] (see also its modern de- scendants [81, 122]), the operating system is architected Malicious peripherals designed to attack their host com- to make different resources of the computer interact with puters are a growing problem. Inexpensive and powerful each other as if they were members of a distributed sys- peripherals that attach to plug-and-play buses have made tem. More generally, the rich literature on high-assurance such attacks easy to mount. Making matters worse, com- kernels offers isolation, confinement, access control, and modity operating systems lack coherent defenses, and many other relevant ideas. On the other hand, applying users are often unaware of the scope of the problem.
  • A Scalable and Reliable Mobile Code Offloading Solution

    A Scalable and Reliable Mobile Code Offloading Solution

    Hindawi Wireless Communications and Mobile Computing Volume 2018, Article ID 8715294, 18 pages https://doi.org/10.1155/2018/8715294 Research Article MobiCOP: A Scalable and Reliable Mobile Code Offloading Solution José I. Benedetto ,1 Guillermo Valenzuela ,1 Pablo Sanabria,1 Andrés Neyem ,1 Jaime Navón,1 and Christian Poellabauer 2 1 Computer Science Department, Pontifcia Universidad Catolica´ de Chile, Santiago, Chile 2Computer Science and Engineering Department, University of Notre Dame, Notre Dame, IN, USA Correspondence should be addressed to Jose´ I. Benedetto; [email protected] Received 26 September 2017; Accepted 12 December 2017; Published 9 January 2018 Academic Editor: Konstantinos E. Psannis Copyright©2018Jose´ I. Benedetto et al. Tis is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. Code ofoading is a popular technique for extending the natural capabilities of mobile devices by migrating processor-intensive tasks to resource-rich surrogates. Despite multiple platforms for ofoading being available in academia, these frameworks have yet to permeate the industry. One of the primary reasons for this is limited experimentation in practical settings and lack of reliability, scalability, and options for distribution. Tis paper introduces MobiCOP, a new code ofoading framework designed from the ground up with these requirements in mind. It features a novel design fully self-contained in a library and ofers compatibility with most stock Android devices available today. Compared to local task executions, MobiCOP ofers performance improvements of up to 17x and increased battery efciency of up to 25x, shows minimum performance degradation in environments with unstable networks, and features an autoscaling module that allows its server counterpart to scale to an arbitrary number of ofoading requests.
  • Performance Analysis of Mobile Applications Developed with Different Programming Tools

    Performance Analysis of Mobile Applications Developed with Different Programming Tools

    MATEC Web of Conferences 252, 05022 (2019) https://doi.org/10.1051/matecconf/201925205022 CMES’18 Performance analysis of mobile applications developed with different programming tools Jakub Smołka1,*, Bartłomiej Matacz2, Edyta Łukasik1, and Maria Skublewska-Paszkowska1 1Lublin University of Technology, Electrical Engineering and Computer Science Faculty, Institute of Computer Science, Nadbystrzycka 36b, 20-618 Lublin, Poland 2 Cybercom, Hrubieszowska 2, 01-209 Warsaw, Poland Abstract. This study examines the efficiency of certain software tasks in applications developed using three frameworks for the Android system: Android SDK, Qt and AppInventor. The results obtained using the Android SDK provided the benchmark for comparison with other frameworks. Three test applications were implemented. Each of them had the same functionality. Performance in the following aspects was tested: sorting a list of items using recursion by means of the Quicksort algorithm, access time to a location from a GPS sensor, duration time for reading the entire list of phone contacts, saving large and small files, reading large and small files, image conversion to greyscale, playback time of a music file, including the preparation time. The results of the Android SDK are good. Unexpectedly, it is not the fastest tool, but the time for performing most operations can be considered satisfactory. The Qt framework is overall about 34% faster than the Android SDK. The worst in terms of overall performance is the AppInventor: it is, on average, over 626 times slower than Android SDK. 1 Introduction The third part presents the results, which are then analysed. According to a recent study [1], the number of As already mentioned, currently the most popular smartphone users is forecasted to grow from 2.1 billion system for mobile devices is Android.
  • Renderscript Basic Tutorial for Android* OS

    Renderscript Basic Tutorial for Android* OS

    RenderScript Basic Tutorial for Android* OS User's Guide Compute Code Builder - Samples Document Number: 330186-002US Android RenderScript Tutorial Contents Contents ......................................................................................................................... 2 Legal Information ............................................................................................................ 3 Introduction .................................................................................................................... 4 What is RenderScript? ...................................................................................................... 4 Running and Controlling the Tutorial .................................................................................. 4 RenderScript Java* APIs ................................................................................................... 5 RenderScript Kernels ........................................................................................................ 7 Tutorial Application Structure ............................................................................................ 8 Seperating RenderScript Kernel and UI Thread Executions .................................................... 8 Android Application Lifecycle Events ................................................................................... 8 Limitations ...................................................................................................................... 9 Notes on Threading
  • Configuring the Information Environment of Microcomputers with the Microsoft Windows 10 Operating System

    Configuring the Information Environment of Microcomputers with the Microsoft Windows 10 Operating System

    Configuring the Information Environment of Microcomputers with the Microsoft Windows 10 Operating System Felix Kasparinsky[0000-0002-1048-9212] MASTER-MULTIMEDIA Ltd, Entuziastov Shosse 98-3-274, Moscow 111531, Russia [email protected] Abstract. Since 2015, microcomputers have appeared in the information envi- ronment, which are a compact system unit with minimal functionality without peripherals. The article published the results of the analysis of the use of 6 dif- ferent microcomputers in various fields of activity. The purpose of the study is to determine the limiting factors affecting the efficiency of the targeted use of microcomputers. It has been established that for scientific and educational presentations, office and trading activities, it is cur-rently advisable to use fan- less microcomputers with a perforated case and an internal WiFi antenna, at least 4 GB of operational and 64 GB of permanent memory, and a microSD (TF) memory card slot, at least 128 GB, NTFS file system), Intel HD Graphics, USB3.0 and HDMI interfaces. Based on comparative experiments, methodolog- ical recommendations were created on optimizing the configuration of the hardware-software environment of microcomputers in stationary and mobile conditions. The problems of major updates to Windows 10, as well as the com- patibility of Microsoft Store software and third-party manufacturers, are ana- lyzed. It is recommended to specialize individual microcomputers for working with 32-bit applications; accounting and cryptographic programs; as well as conducting presentations with their video. Options for optimal configuration of the Start menu of the Windows 10 desktop are suggested. It is concluded that specialization in the hardware-software configuration of modern microcomput- ers allows you to increase the efficiency of using single de-vices and their paired systems in accordance with BYOD (Bring Your Own Device).
  • Linux Hardware Compatibility HOWTO

    Linux Hardware Compatibility HOWTO

    Linux Hardware Compatibility HOWTO Steven Pritchard Southern Illinois Linux Users Group / K&S Pritchard Enterprises, Inc. <[email protected]> 3.2.4 Copyright © 2001−2007 Steven Pritchard Copyright © 1997−1999 Patrick Reijnen 2007−05−22 This document attempts to list most of the hardware known to be either supported or unsupported under Linux. Copyright This HOWTO is free documentation; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free software Foundation; either version 2 of the license, or (at your option) any later version. Linux Hardware Compatibility HOWTO Table of Contents 1. Introduction.....................................................................................................................................................1 1.1. Notes on binary−only drivers...........................................................................................................1 1.2. Notes on proprietary drivers.............................................................................................................1 1.3. System architectures.........................................................................................................................1 1.4. Related sources of information.........................................................................................................2 1.5. Known problems with this document...............................................................................................2 1.6. New versions of this document.........................................................................................................2