Home · All Namespaces · All Classes · Grouped Classes · Modules · Functions

Hardware Configuration

• Introduction
• Device-specific Code
• Removable Media and Devices

Introduction

When planning to customize and install Qt Extended on a specific device there are a number of factors that must be taken into consideration:

• If the device has a touch screen, Qt Extended calibration must be enabled.
• If the device runs off batteries, Qt Extended may be required to call APM functions for power saving. See the Power Management section below for more details.
• If the device has special hardware buttons, they may need to be mapped to applications and have associated images displayed in the user interface.
• If the device has a buzzer for alarms and other beeps, Qt Extended will need to know how to use this hardware and enable it for the associated events.
• If the device has an LCD screen with a back or front light, Qt Extended will need to know how to adjust its brightness.
• If the device has any special LEDs to indicate status to the user, Qt Extended will need to know how to set the LEDs.
• If the device has or supports phone hardware, a serial device that supports GSM AT-commands should be provided, so that Qt Extended can use it.
• If the device supports sound, the sound volume should be locked to the maximum intended volume.
• If the device supports removable media or PCMCIA cards, notifications must be sent to Qt Extended when these are inserted or removed.

All the changes required to add these device specific customizations are centralized in Qt Extended and involve a small number of files (described below). This document should make it easy for OEMs and system integrators to understand how to make Qt Extended aware of any special hardware that a device might have.

Device-specific Code

Device-specific code is implemented in custom.h/custom.cpp.

Since these files are tied to a device it is useful to have them in the device profile. If these files are not present configure will look in the traditional location, <source>/src/libraries/qtopia/custom-<xplatform>.(h|cpp). See <custom.h> for more information about these files.

Device profiles can implement their own custom.(h|cpp) files, which will override the <source>/src/libraries/qtopia/custom-<xplatform>.(h|cpp) and custom.(h|cpp) files in Qt Extended.

For reference implementations of these files, the existing files found in <source>/devices/greenphone/custom.* may be of assistance.

Removable Media and Devices

Qt Extended supports both removable media, such as SD cards, and removable hotplug devices, such as PCMCIA network cards. However, as there is no standard way in Linux for Qt Extended to detect when these devices or media are inserted or removed, it is the system integrators responsibility to detect whenever the attached PCMCIA devices or mounted filesystems change notify Qt Extended appropriately.

Integrators notify Qt Extended by sending QCop messages. QCop messages may be sent from C++ code using the QtopiaIpcEnvelope class, or from system shell scripts using the qcop command line tool.

The following table describes the events and the QCop messages that should be sent:

    qcop send QPE/Card "mtabChanged()"

    qcop send QPE/Card "stabChanged()"