About These Technotes

For this release of QNX Neutrino, you'll find the following technotes here:

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.

Managing POSIX Message Queues

Describes how to manage 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, http://www.qnx.com/legal/licensing/.

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 boards.

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.

Backtraces

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

Process Performance State Manager (PPSM)

How to use the Enhanced Intel Speed Step technology, and System State S3 (Suspend to RAM) and S5 (Suspend to Disk) power management support.

Customizing language sort orders for libqdb_cldr.so

How to create custom language sort orders to use with the libqdb_cldr.so DLL.

Typographical conventions

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:

Reference	Example
Code examples	`if( stream == NULL )`
Command options	`-lR`
Commands	`make`
Environment variables	PATH
File and pathnames	`/dev/null`
Function names	exit()
Keyboard chords	Ctrl-Alt-Delete
Keyboard input	`something you type`
Keyboard keys	Enter
Program output	`login:`
Programming constants	NULL
Programming data types	`unsigned short`
Programming literals	`0xFF`, `"message string"`
Variable names	stdin
User-interface components	Cancel

Reference

Example

Code examples

if( stream == NULL )

Command options

-lR

Commands

make

Environment variables

PATH

File and pathnames

/dev/null

Function names

exit()

Keyboard chords

Ctrl-Alt-Delete

Keyboard input

something you type

Keyboard keys

Enter

Program output

login:

Programming constants

NULL

Programming data types

unsigned short

Programming literals

0xFF, "message string"

Variable names

stdin

User-interface components

Cancel

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 messages:

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.

At the top and bottom of our HTML docs, you'll see some or all of these buttons:

Use this button:	To move:
	To the previous part of the document.
	“Up” in the document: In a prose book, this typically takes you to About This Guide. In a reference book, it takes you to the listing of items that start with a given letter. For example, if you're looking at the docs for abs(), this button takes you to the listing of the functions that start with `A`.
	To the keyword index.
	To the next part of the document.

Use this button:

To move:

To the previous part of the document.

“Up” in the document:

In a prose book, this typically takes you to About This Guide.
In a reference book, it takes you to the listing of items that start with a given letter. For example, if you're looking at the docs for abs(), this button takes you to the listing of the functions that start with A.

To the keyword index.

To the next part of the document.

About These Technotes

Typographical conventions

Note to Windows users

Navigation buttons

Technical support