DOCSLIB.ORG

PCAN-Driver for Linux

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
PCAN-Driver for Linux PCAN-driver for Linux Copyright (C) 2002 -2005 Peak System-Technik GmbH www.peak-system.com linux@peak-system.com and Klaus Hitschler klaus.hitschler@gmx.de PCAN-driver for Linux page 1 of 20 History of the document first draft Hi 13.01.2002 rescue after loss of data Hi 10.02.2002 format revision, read/write tables Hi 20.02.2002 delete typographic mistakes Hi 21.02.2002 PCAN-USB integrated Hi 09.02.2003 obfuscation of „pcan_usb_kernel.c“ is described Hi 23.02.2003 devfs, kernel-2.5 support, LGPL Hi 04.08.2003 1st revision for kernel 2.6.x Hi 02.05.2004 enlarge FAQ, corrections Hi 13.05.2004 simple correction for RPM make procedure Hi 14.08.2004 additional compiler switches Hi 19.07.2005 PCAN-driver for Linux page 2 of 20 table of documents Disclaimer..........................................................................................................................4 Characteristics of the 'pcan.o' or 'pcan.ko' driver..............................................................4 Characteristics of the 'libpcan.so' library...........................................................................5 Preliminary notes...............................................................................................................5 Installation with RPM.........................................................................................................6 Installation of source RPM........................................................................................6 Customization of 'modules.conf' or 'modprobe.conf'.................................................7 Installation of the driver ............................................................................................7 Manual installation.............................................................................................................7 Manual file unpacking ..............................................................................................7 Specifics with the driver installation for PCAN-USB ................................................8 Manual installation of the driver ...............................................................................9 Manual installation of the shared library.................................................................10 Manual installation of the header-files....................................................................10 Semi-automatic installation with translation.....................................................................11 Installation test, use of test programs..............................................................................11 Most important header files ............................................................................................13 Compilation of the driver..................................................................................................13 Use cases ...............................................................................................................13 Prerequisites for compilation of the sources...........................................................14 Support for Cross-Compilation................................................................................15 FAQs................................................................................................................................15 Appendix..........................................................................................................................19 PCAN-driver for Linux page 3 of 20 Disclaimer Part of this program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License or LGPL Lesser General Public License as published by the Free Software Foundation version 2 of the License. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA It is strictly prohibited to use the intellectual property from the provided source code for developing or producing a 'compatible' hardware. All rights are reserved by Peak- System- Technik GmbH. Characteristics of the 'pcan.o' or 'pcan.ko' driver The „pcan.o“ or „pcan.ko“ driver is supporting PCAN-PCI, PCAN-ISA, PCAN-PC/104, PCAN-Dongle as well as PCAN-USB hardware. Depending on the type of hardware (PCI, ISA, Dongle, USB) 8 channels for each type can be supported. For PCAN-ISA, PCAN-PC/104 and PCAN-Dongle the base address and the used interrupt are adjustable. If no parameters are provided then the driver uses factory defaults. A user program can communicate with the driver in two different ways: 1. ASCII formatted data can be provided or accepted over a „read()“ or „write()“ interface. This data contains information from received or transmitted telegrams or about channel initializing parameters. 2. With a „ioctl()“ interface. Through this interface user programs are able to receive and to transmit CAN-telegrams as well. However it is possible to get information about the diagnosis of the channel status and to initialize the CAN-channel. The driver can be used from more than one user program at the same time and the simultaneous use of lots of interfaces and/or CAN channels is supported. If more than one user program communicates with the same CAN-channel the input or output is shared. (e.g.: Many user programs are accidentally sharing the received telegrams.) Up from Release_20030622_x the device file system is being supported optionally. Using the devfs it's not necessary to create device files manually any more. This is taken over by the kernel in cooperation with the driver and the daemon devfsd. The device file system has to be enabled within the kernel. (From kernel version 2.6.x on the kernel developers depreciate the use of devfs so for the time being the driver is not supporting this.) The reading or writing of telegrams can block if the receive buffer doesn't contain data any more or if the write buffer is full. This behaviour can be disabled by opening the path as non-blocking. PCAN-driver for Linux page 4 of 20 The „select“-method is supported. The interface to the driver (constants and structures) is defined in the header file „pcan.h“. Characteristics of the 'libpcan.so' library The „libpcan.so“ library is providing an easier interface for using the properties of the PCAN-drivers. The library interface is similar to the ones from MS-Windows and make the porting of applications easier. There are also some calls which adapt better to the specifics of Linux. They are marked with a 'LINUX_..' as prefix. (Example: HANDLE LINUX_CAN_Open(char *szDeviceName, int nFlags);) Application Shared library Driver Picture 1. calling hierarchy The interface of the library is described within the C/C++-header file „libpcan.h“. Please note that „libpcan.h“ includes the „pcan.h“ file. The source code is under LGPL so it is for utilizing within proprietary software without any exceptions. Preliminary notes Note: Before installing the software the hardware has to be installed in or at the computer (Exception: PCAN-Dongle or PCAN-USB, see at (6*)). This manual is describing the installation process on a x86-Linux-computer with installed kernel 2.4.x. and a SuSE 8.0 system. Exceptions for kernel 2.2.x. 2.6.x and x86-RedHat systems are particularly mentioned. During the installation sometimes a console and perhaps an editor as well will be used in the „root“- mode. If you want to login as „root“ user within a console or xterm-session you can use the 'su' command or the built in menu „file/root console“. PCAN-driver for Linux page 5 of 20 To start an editor in the „root“ – mode, just invoke from the menu „system/terminals/terminal (system manager mode)“ in KDE. From the console command line you can invoke the editor „kwrite“, „kate“ or „emacs“. For some distributions the standard path doesn't include the „/sbin“ folder. Then installation commands have to typed in with „/sbin/“ ahead. Examples: /sbin/modprobe ... instead of modprobe ... /sbin/insmod ... instead of insmod ... /sbin/rmmod ... instead of rmmod ... /sbin/modinfo ... instead of modinfo ... Installation with RPM The installation comprise three files: Installation-en.pdf description in PDF format. peak-linux-driver-20040501-3.3.src.rpm the RPM-source-file. peak-linux-driver.3.3.tar.gz the packed tar-sources. (Note: The term for release or the version for file names can change.) The installation with RPM creates an installable RPM – package with standard settings for the local target system. If the standard settings don't fit you can do a manual installation. Installation of source RPM Please type in the command line (as „root“ user): rpm --rebuild peak-linux-driver-20040501-3.3.src.rpm or rpmbuild –rebuild peak-linux-driver-20040501-3.3.src.rpm if the file „peak-linux-driver-20040501-3.3.src.rpm“ is in your current directory. This invocation expects the previous installation of the gcc-compiler, the kernel-headers and the make tools. The translation with and for systems with kernel 2.6.x needs an additionally configured kernel and all of the kernel sources. At the successful end of this rebuild RPM is filing at: „/usr/src/packages/“ or „/usr/src/redhat“ a system specific binary-installation for SuSE or RedHat in this folder. e.g. /usr/src/redhat/RPMS/i386/peak-linux-driver-20040501-3.3.i386.rpm
Load more

Recommended publications
  • Timesys Linux Install HOWTO
    TimeSys Linux Install HOWTO Trevor Harmon <trevor@vocaro.com> 2005−04−05 Revision History Revision 1.0 2005−04−05 Revised by: TH first official release This document is a quick−start guide for installing TimeSys Linux on a typical desktop workstation. TimeSys Linux Install HOWTO Table of Contents 1. Introduction.....................................................................................................................................................1 1.1. Background.......................................................................................................................................1 1.2. Copyright and License......................................................................................................................1 1.3. Disclaimer.........................................................................................................................................2 1.4. Feedback...........................................................................................................................................2 2. Requirements...................................................................................................................................................3 3. Install the packages.........................................................................................................................................4 4. Prepare the source directories.......................................................................................................................5 5. Configure
    [Show full text]
  • The Linux Device File-System
    The Linux Device File-System Richard Gooch EMC Corporation rgooch@atnf.csiro.au Abstract 1 Introduction All Unix systems provide access to hardware via de- vice drivers. These drivers need to provide entry points for user-space applications and system tools to access the hardware. Following the \everything is a file” philosophy of Unix, these entry points are ex- posed in the file name-space, and are called \device The Device File-System (devfs) provides a power- special files” or \device nodes". ful new device management mechanism for Linux. Unlike other existing and proposed device manage- This paper discusses how these device nodes are cre- ment schemes, it is powerful, flexible, scalable and ated and managed in conventional Unix systems and efficient. the limitations this scheme imposes. An alternative mechanism is then presented. It is an alternative to conventional disc-based char- acter and block special devices. Kernel device drivers can register devices by name rather than de- vice numbers, and these device entries will appear in the file-system automatically. 1.1 Device numbers Devfs provides an immediate benefit to system ad- ministrators, as it implements a device naming scheme which is more convenient for large systems Conventional Unix systems have the concept of a (providing a topology-based name-space) and small \device number". Each instance of a driver and systems (via a device-class based name-space) alike. hardware component is assigned a unique device number. Within the kernel, this device number is Device driver authors can benefit from devfs by used to refer to the hardware and driver instance.
    [Show full text]
  • Implantación De Linux Sobre Microcontroladores
    Embedded Linux system development Embedded Linux system development DSI Embedded Linux Free Electrons Developers © Copyright 2004-2018, Free Electrons. Creative Commons BY-SA 3.0 license. Latest update: March 14, 2018. Document updates and sources: http://free-electrons.com/doc/training/embedded-linux Corrections, suggestions, contributions and translations are welcome! DSI - FCEIA http://dsi.fceia.unr.edu.ar 1/263 Derechos de copia © Copyright 2018, Luciano Diamand Licencia: Creative Commons Attribution - Share Alike 3.0 http://creativecommons.org/licenses/by-sa/3.0/legalcode Ud es libre de: I copiar, distribuir, mostrar y realizar el trabajo I hacer trabajos derivados I hacer uso comercial del trabajo Bajo las siguientes condiciones: I Atribuci´on. Debes darle el cr´editoal autor original. I Compartir por igual. Si altera, transforma o construye sobre este trabajo, usted puede distribuir el trabajo resultante solamente bajo una licencia id´enticaa ´esta. I Para cualquier reutilizaci´ono distribuci´on,debe dejar claro a otros los t´erminos de la licencia de este trabajo. I Se puede renunciar a cualquiera de estas condiciones si usted consigue el permiso del titular de los derechos de autor. El uso justo y otros derechos no se ven afectados por lo anterior. DSI - FCEIA http://dsi.fceia.unr.edu.ar 2/263 Hiperv´ınculosen el documento Hay muchos hiperv´ınculosen el documento I Hiperv´ıncluosregulares: http://kernel.org/ I Enlaces a la documentaci´ondel Kernel: Documentation/kmemcheck.txt I Enlaces a los archivos fuente y directorios del kernel: drivers/input include/linux/fb.h I Enlaces a declaraciones, definiciones e instancias de los simbolos del kernel (funciones, tipos, datos, estructuras): platform_get_irq() GFP_KERNEL struct file_operations DSI - FCEIA http://dsi.fceia.unr.edu.ar 3/263 Introducci´ona Linux Embebido Introducci´ona DSI Linux Embebido Embedded Linux Developers Free Electrons © Copyright 2004-2018, Free Electrons.
    [Show full text]
  • Linux Fast-STREAMS Installation and Reference Manual Version 0.9.2 Edition 4 Updated 2008-10-31 Package Streams-0.9.2.4
    Linux Fast-STREAMS Installation and Reference Manual Version 0.9.2 Edition 4 Updated 2008-10-31 Package streams-0.9.2.4 Brian Bidulock <bidulock@openss7.org> for The OpenSS7 Project <http://www.openss7.org/> Copyright c 2001-2008 OpenSS7 Corporation <http://www.openss7.com/> Copyright c 1997-2000 Brian F. G. Bidulock <bidulock@openss7.org> All Rights Reserved. Published by OpenSS7 Corporation 1469 Jefferys Crescent Edmonton, Alberta T6L 6T1 Canada This is texinfo edition 4 of the Linux Fast-STREAMS manual, and is consistent with streams 0.9.2. This manual was developed under the OpenSS7 Project and was funded in part by OpenSS7 Corporation. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the con- ditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another lan- guage, under the same conditions as for modified versions. i Short Contents Preface ::::::::::::::::::::::::::::::::::::::::::::::::: 1 Quick Start Guide :::::::::::::::::::::::::::::::::::::::: 9 1 Introduction :::::::::::::::::::::::::::::::::::::::: 15 2 Objective ::::::::::::::::::::::::::::::::::::::::::: 17 3 Reference ::::::::::::::::::::::::::::::::::::::::::: 21 4 Development ::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Linux 2.5 Kernel Developers Summit
    conference reports This issue’s reports are on the Linux 2.5 Linux 2.5 Kernel Developers Linux development, but I certainly Kernel Developers Summit Summit thought that, in all of this time, someone would have brought this group together OUR THANKS TO THE SUMMARIZER: SAN JOSE, CALIFORNIA before. Rik Farrow, with thanks to La Monte MARCH 30-31, 2001 Yarroll and Chris Mason for sharing their Summarized by Rik Farrow Another difference appeared when the notes. first session started on Friday morning. The purpose of this workshop was to The conference room was set up with cir- provide a forum for discussion of cular tables, each with power strips for changes to be made in the 2.5 release of For additional information on the Linux laptops, and only a few attendees were Linux (a trademark of Linus Torvalds). I not using a laptop. USENIX had pro- 2.5 Kernel Developers Summit, see the assume that many people reading this vided Aeronet wireless setup via the following sites: will be familiar with Linux, and I will hotel’s T1 link, and people were busy <http://lwn.net/2001/features/KernelSummit/> attempt to explain things that might be typing and compiling. Chris Mason of unfamiliar to others. That said, the odd- <http://cgi.zdnet.com/slink?91362:12284618> OSDN noticed that Dave Miller had numbered releases, like 2.3 and now 2.5, <http://www.osdn.com/conferences/kernel/> written a utility to modulate the speed of are development releases where the the CPU fans based upon the tempera- intent is to try out new features or make ture reading from his motherboard.
    [Show full text]
  • CRUX Handbook RELEASE 2.0 CRUX Handbook: RELEASE 2.0
    CRUX Handbook RELEASE 2.0 CRUX Handbook: RELEASE 2.0 Published 2004-06-01 Copyright © 2001, 2002, 2003, 2004 Per Lidén [mailto:per@fukt.bth.se] This handbook covers the installation, configuration and administration of CRUX. Please note that this hand- book only covers topics that are specific to CRUX [http://crux.nu/]. For further information about Linux see the Linux Documentation Project [http://www.tldp.org/]. Table of Contents Preface...................................................................................................................................5 1.Introduction .........................................................................................................................1 1.1.WhatisCRUX? ......................................................................................................... 1 1.2. Why use CRUX? ........................................................................................................ 1 1.3.License ....................................................................................................................1 1.3.1.Packages ........................................................................................................ 1 1.3.2. Build Scripts ................................................................................................... 1 1.3.3. NO WARANTY .............................................................................................. 1 2. Installing CRUX ..................................................................................................................
    [Show full text]
  • Methods to Improve Bootup Time in Linux
    Methods to Improve Bootup Time in Linux Tim Bird Sony Electronics Bootup Time Working Group Chair CE Linux Forum July 21, 2004 Ottawa Linux Symposium 1 Overview Characterization of the problem space Current reduction techniques Work in progress Resources July 21, 2004 Ottawa Linux Symposium 2 Characterizing the Problem Space July 21, 2004 Ottawa Linux Symposium 3 The Problem Linux doesn’t boot very fast Current Linux desktop systems take about 90- 120 seconds to boot Most CE products must be ready for operation within seconds of boot CELF requirements: boot kernel in 500 milliseconds first available for use in 1 second July 21, 2004 Ottawa Linux Symposium 4 Boot Process Overview 1. power on 2. firmware (boot loader) starts 3. kernel decompression starts 4. kernel start 5. user space start 6. RC script start 7. application start 8. first available use July 21, 2004 Ottawa Linux Symposium 5 Delay Areas Major delay areas in startup: Firmware Kernel/driver initialization User space initialization RC Scripts Application startup July 21, 2004 Ottawa Linux Symposium 6 Overview of delays (on a sample desktop system) Startup Area Delay Firmware 15 seconds Kernel/driver initialization 7 seconds RC scripts 35 seconds X initialization 9 seconds Graphical Environment start 45 seconds Total: 111 seconds For laptop with Pentium III at 600 MHZ July 21, 2004 Ottawa Linux Symposium 7 Firmware July 21, 2004 Ottawa Linux Symposium 8 Firmware/Pre-kernel delays X86 firmware (BIOS) is notorious for superfluous delays (memory checking, hardware probing, etc.)
    [Show full text]
  • EVMS User Guide
    EVMS User Guide Joy Goodreau IBM Kylie Smith IBM Christine Lorenz IBM Copyright © 2003 IBM March 31, 2003 Special Notices The following terms are registered trademarks of International Business Machines corporation in the United States and/or other countries: AIX, OS/2, System/390. A full list of U.S. trademarks owned by IBM may be found at http://www.ibm.com/legal/copytrade.shtml. Intel is a trademark or registered trademark of Intel Corporation in the United States, other countries, or both. Windows is a trademark of Microsoft Corporation in the United States, other countries, or both. Linux is a trademark of Linus Torvalds. Other company, product, and service names may be trademarks or service marks of others. UNIX is a registered trademark of The Open Group in the United States and other countries. This document is provided "AS IS," with no express or implied warranties. Use the information in this document at your own risk. License Information This document may be reproduced or distributed in any form without prior permission provided the copyright notice is retained on all copies. Modified versions of this document may be freely distributed provided that they are clearly identified as such, and this copyright is included intact. EVMS User Guide Table of Contents Preface..................................................................................................................................................................1 Chapter 1. What is EVMS?................................................................................................................................3
    [Show full text]
  • Reducing Startup Time in Embedded Linux Systems
    Reducing Startup Time in Embedded Linux Systems Tim Bird Chair – Bootup Times Working Group CE Linux Forum December, 2003 Copyright 2003, CE Linux Forum 1 Member Companies Overview • Characterization of the problem space • Current reduction techniques • Work in progress • CE Linux Forum December, 2003 Copyright 2003, CE Linux Forum 2 Member Companies Characterizing the Problem Space December, 2003 Copyright 2003, CE Linux Forum 3 Member Companies The Problem • Linux doesn’t boot very fast – Current Linux desktop systems take about 90-120 seconds to boot • This is clearly not suitable for consumer electronics products December, 2003 Copyright 2003, CE Linux Forum 4 Member Companies Delay Taxonomy • Major delay areas in startup: – Firmware – Kernel/driver initialization – User space initialization – Application startup • Scope of problem – Device-specific – Systemic December, 2003 Copyright 2003, CE Linux Forum 5 Member Companies Overview of delays Startup Area Delay Firmware 15 seconds Kernel/ driver initialization 9 seconds RC scripts 35 seconds X initialization 9 seconds Graphical Environment start 45 seconds Total: 113 seconds For laptop with Pentium III at 600 MHZ December, 2003 Copyright 2003, CE Linux Forum 6 Member Companies Firmware delays • X86 firmware (BIOS) is notorious for superfluous delays (memory checking, hardware probing, etc.) – Many of these operations are duplicated by the kernel when it starts • Large delay for spinup of hard drive • Delay to load and decompress kernel December, 2003 Copyright 2003, CE Linux Forum 7 Member Companies Typical HD Time-to-Ready Brand Size Time to Ready Maxtor 3.5” 7.5 seconds Seagate 3.5” 6.5 - 10 seconds * Hitachi 3.5” 6 - 10 seconds * Hitachi 2.5” 4 - 5 seconds Toshiba 2.5” 4 seconds Hitachi 1.0” 1 - 1.5 seconds microdrive * Depends on number of platters During retries, these times can be extended by tens of seconds, but this is rare.
    [Show full text]
  • Silicon Graphics Visual Workstation Environment (VWE) Start Here
    Silicon Graphics Visual Workstation Environment (VWE) Start Here 007-4203-002 COPYRIGHT © 2000 Silicon Graphics, Inc. All rights reserved; provided portions may be copyright in third parties, as indicated elsewhere herein. No permission is granted to copy, distribute, or create derivative works from the contents of this electronic documentation in any manner, in whole or in part, without the prior written permission of Silicon Graphics, Inc. LIMITED RIGHTS LEGEND The electronic (software) version of this document was developed at private expense; if acquired under an agreement with the USA government or any contractor thereto, it is acquired as “commercial computer software” subject to the provisions of its applicable license agreement, as specified in (a) 48 CFR 12.212 of the FAR; or, if acquired for Department of Defense units, (b) 48 CFR 227-7202 of the DoD FAR Supplement; or sections succeeding thereto. Contractor/manufacturer is Silicon Graphics, Inc., 1600 Amphitheatre Pkwy 2E, Mountain View, CA 94043-1351. TRADEMARKS AND ATTRIBUTIONS Silicon Graphics, IRIS, IRIX, and OpenGL are registered trademarks, and SGI, the SGI logo, IRIS Performer, Open Inventor, and VPro are trademarks of Silicon Graphics, Inc. Adaptec is a trademark of Adaptec, Inc. Cisco is a trademark of Cisco Systems, Inc. Intel is a registered trademark of Intel Corporation. Linux is a registered trademark of Linus Torvalds, used with permission by Silicon Graphics, Inc. Mylex is a trademark of International Business Machines Corporation. QLogic is a trademark of QLogic Corporation. Red Hat is a registered trademark and RPM is a trademark of Red Hat, Inc. SuSE is a trademark of SuSE Inc.
    [Show full text]
  • Systemimager® V3.0.1 Manual
    SystemImager® v3.0.1 Manual Brian Elliott Finley dann frazier Austin Gonyou Ari Jort Jason R. Mastaler Greg Pratt Ben Spade Denise Walters Curtis Zinzilieta SystemImager® v3.0.1 Manual by Brian Elliott Finley dann frazier Austin Gonyou Ari Jort Jason R. Mastaler Greg Pratt Ben Spade Denise Walters Curtis Zinzilieta Published $Date: 2003/02/19 05:58:26 $ SystemImager was created by Brian Elliott Finley, who continues to maintain it as the Sys- temImager team lead. Its initial implementation was known as Pterodactyl, which was used for software and password updates to Solaris boxes of varying hardware and OS versions across a nationwide enterprise network. Many SystemImager design decisions were based on per- ceived shortcomings in other automated install tools for systems such as Solaris, RedHat Linux, and Windows. Eventually, SystemImager evolved into the Linux-specific autoinstall and soft- ware distribution tool that it is today. Be sure to view the CREDITS file for a listing of other people who have contributed code or documentation that has been incorporated into SystemImager. Many thanks go to these peo- ple, as their relentless pursuit in the discovery bugs and the occasional code contribution are invaluable. Trademark Notices SystemImager® is a registered trademark of Brian Finley. Linux® is a registered trademark of Linus Torvalds. Debian® is a registered trademark of Software in the Public Interest, Inc. Red Hat® is a registered trademark of Red Hat, Inc. in the United States and other countries. Solaris® is a registered trademark
    [Show full text]
  • Developing Mobile Devices Based on Linux
    Developing Mobile Devices based on Linux Tim Riker Texas Instruments Tim@Rikers.org, http://Rikers.org/ Abstract ilar. This advantage truly comes to light when a community is formed around the product. This This presentation will cover available com- community can focus on enhancing the product ponents of embedded solutions that leverage without direct development cost to the manu- Linux. We discuss bootloaders, Linux kernel facturer. When planning the product lifetime, configuration, BusyBox, glibc, uClibc, GUI thought should be given to seeding hardware choices such as Qtopia, TinyX, GPE, Kon- to key community members so that community queror, Dillo, and similar packages that make support is available early in the product life cy- up a commercial-grade consumer device. This cle. presentation is aimed at those who are just get- ting into Linux on mobile or other embedded 2 Special Needs of Mobile Devices devices. Mobile devices have features not often seen 1 Why Linux? in desktop or server systems. Most use flash storage instead of traditional hard disk media. Linux is a stable, tested platform for produc- NOR flash is a common choice for average- tion use. The most often-used environment for sized storage, but becomes more expensive Linux is as a server for key business services. with larger systems. It is relatively easy to han- Is it well suited for embedded use on mobile dle from a software perspective, and is com- devices? It is. Linux has a low total cost of monly available as a direct memory mapped ownership as compared to other options. There device.
    [Show full text]