For this release of QNX Neutrino, you'll find the following
- IP Tunneling (Generic Routing Encapsulation)
- Describes how you'd set up and use GRE.
- PPPOE and Path MTU Discovery
- Describes how to work around a problem with path MTU discovery.
- Making Multiple Images
- Explains how to use mkifs to create more than one image.
- QNX Neutrino and QNX4 bootloader partitions
- Explains problems associated with using a QNX Neutrino bootloader partition to boot a QNX4 partition.
- POSIX Message Queues: Two Implementations
- Compares the traditional and alternate managers for POSIX message queues.
- Choosing the Correct MTD
Routine for the Flash Filesystem
- Choose the correct MTD routine.
- Asynchronous Messaging
- How to use asynchronous messaging.
||Asynchronous messaging is an experimental feature;
for information about the use of
experimental software, see the Commercial Software License Agreement (CSLA) or
Partner Software License Agreement (PSLA) in the Licensing area of our website,
- Reading a Kernel Dump
- How to interpret the output if your application causes a kernel fault.
- I2C (Inter-Integrated Circuit) Framework
- Describes how to create and use an I2C driver.
- SPI (Serial Peripheral Interface) Framework
- Describes the API for the SPI interface.
- Fine-tuning your network drivers
- How to tune your network drivers for increased performance or
reduced memory footprint.
- Migrating to QNX Neutrino for
ARMv6 Processor Based Boards
- Describes the migration procedure to QNX Neutrino for ARMv6 processor based
- QNX Neutrino for ARMv7
Cortex A-8 and A-9 Processors
- Describes the processes to use when setting up QNX Neutrino for boards that
support ARMv7 Cortex A-8 and Cortex A-9 processors.
- Supporting Vector Floating
Point Functionality for ARM Processors
- Describes the vector floating point functionality for ARM processors.
- How to create a Runtime Kit from the QNX Software Development Platform
- How to generate a QNX Neutrino runtime system CD.
- How to get a backtrace of calling functions.
- Freescale E500 SPE
- How to get support for using Freescale E500 SPE.
- Reloadable Image Filesystems
- How to quickly restore an IFS when you restart a system.
- Filesystems and Power Failures
- Information about maintaining hard-disk integrity during power failures
- Customizing language sort orders for libqdb_cldr.so
- How to create custom language sort orders to use with the libqdb_cldr.so DLL.
Throughout this manual, we use certain typographical conventions to
distinguish technical terms. In general, the conventions we use
conform to those found in IEEE POSIX publications. The following table
summarizes our conventions:
||if( stream == NULL )
|File and pathnames
||something you type
|Programming data types
||0xFF, "message string"
We use an arrow (→) in directions for accessing menu
items, like this:
You'll find the Other... menu item under
We use notes, cautions, and warnings to highlight important
||Notes point out something important or useful.|
||Cautions tell you about commands or procedures that may have
unwanted or undesirable side effects.|
||Warnings tell you about commands or procedures that could be
dangerous to your files, your hardware, or even yourself.|
In our documentation, we use a forward slash
(/) as a delimiter in all pathnames,
including those pointing to Windows files.
We also generally follow POSIX/UNIX filesystem conventions.
To obtain technical support for any QNX product, visit the
on our website (www.qnx.com).
You'll find a wide range of support options, including community forums.
© 1996–2018, QNX Software Systems Limited, a subsidiary of BlackBerry Limited. All rights reserved.