From Infogalactic: the planetary knowledge core
Jump to: navigation, search
The default desktop in QNX 6.4.1
Developer BlackBerry Ltd
OS family Unix-like
Working state Current
Source model Shared source
Initial release 1982; 36 years ago (1982)
Latest release 6.6 / March 2014; 4 years ago (2014-03)
Marketing target Embedded systems
Package manager Able to use Pkgsrc framework from NetBSD project
Platforms Intel 8088, x86, MIPS, PowerPC, SH-4, ARM, StrongARM, XScale
Kernel type RTOS (Microkernel)
License Proprietary
Official website www.qnx.com

QNX (/ˌkjuː ˌɛn ˈɛks/ or /ˈkjuːnks/) is a commercial Unix-like real-time operating system, aimed primarily at the embedded systems market. The product was originally developed in the early 1980s by Canadian company Quantum Software Systems, later renamed QNX Software Systems and ultimately acquired by BlackBerry in 2010.[1] QNX was one of the first commercially successful microkernel operating systems[citation needed] and is used in a variety of devices including cars[2] and mobile phones.


As a microkernel-based OS, QNX is based on the idea of running most of the operating system kernel in the form of a number of small tasks, known as servers. This differs from the more traditional monolithic kernel, in which the operating system kernel is a single very large program composed of a huge number of "parts" with special abilities. In the case of QNX, the use of a microkernel allows users (developers) to turn off any functionality they do not require without having to change the OS itself; instead, those servers will simply not run.

The system is quite small, with earlier versions fitting on a single floppy disk.[3]

QNX Neutrino (2001) has been ported to a number of platforms and now runs on practically any modern CPU that is used in the embedded market. This includes the PowerPC, x86 family, MIPS, SH-4, and the closely inter-related family of ARM, StrongARM and XScale CPUs.

QNX offers a license for non-commercial and academic users.[4]

The BlackBerry PlayBook tablet computer designed by BlackBerry uses a version of QNX as the primary operating system. Devices from BlackBerry running the BlackBerry 10 operating system are also based on QNX.


Gordon Bell and Dan Dodge, students at the University of Waterloo in 1980, both took a standard computer science course in operating system design, in which the students constructed a basic real-time kernel. Both were convinced there was a commercial need for such a system, and moved to the high-tech planned community Kanata, Ontario, to start Quantum Software Systems that year. In 1982, the first version of QNX was released for the Intel 8088 CPU.

One of first widespread uses of the QNX real-time OS (RTOS) was in the non-embedded world, when it was selected as the operating system for the Ontario education system's own computer design, the Unisys ICON. Over the years QNX was used mostly for "larger" projects, as its 44k kernel was too large to fit inside the single-chip computers of the era. The system garnered a reputation for reliability[citation needed] and found itself in use running machinery in a number of industrial applications.

In the late-1980s, Quantum realized that the market was rapidly moving towards the POSIX model and decided to rewrite the kernel to be much more compatible at a low level. The result was QNX 4. During this time Patrick Hayden, while working as an intern, along with Robin Burgener (a full-time employee at the time), developed a new windowing system. This patented[5] concept was developed into the embeddable GUI named the QNX Photon microGUI. QNX also provided a version of the X Window System.

Toward the end of the 1990s, the company (now called QNX Software Systems) began work on a new version of QNX, designed from the ground up to be SMP capable, and to support all current POSIX APIs and any new POSIX APIs that could be anticipated while still retaining the microkernel architecture. This resulted in QNX Neutrino, released in 2001.

Along with the Neutrino kernel, QNX Software Systems became a founding member of the Eclipse consortium. The company released a suite of Eclipse plug-ins packaged with the Eclipse workbench in 2002 under the name QNX Momentics Tool Suite.

In 2004, the company announced it had been sold to Harman International Industries. Prior to this acquisition, QNX software was already widely used in the automotive industry for telematics systems. Since the purchase by Harman, QNX software has been designed into over 200 different automobile makes and models — not only in telematics systems but in infotainment and navigation units as well.[citation needed] The QNX CAR Application Platform is running in over 20 million vehicles as of mid-2011.[6] The company has since released several middleware products including the QNX Aviage Multimedia Suite, the QNX Aviage Acoustic Processing Suite and the QNX HMI Suite.

Cisco's IOS-XR (ultra high availability IOS) built about 2004-2005[7] is based on QNX software,[8] as is IOS Software Modularity introduced in 2006.[9]

In September 2007, QNX Software Systems announced the availability of some of its source code.[10]

On April 9, 2010, Research In Motion announced they would acquire QNX Software Systems from Harman International Industries.[1] On the same day, QNX source code access was restricted from the public and hobbyists.[11][12]

In September 2010, the company announced a tablet computer, the BlackBerry PlayBook, and a new operating system BlackBerry Tablet OS based on QNX to run on the tablet.[13]

On October 18, 2011, Research In Motion announced "BBX"[14] which was later renamed to BlackBerry 10 in December 2011.[15] Blackberry 10 devices build upon the BlackBerry PlayBook QNX based operating system for touch devices, but adapt the user interface for smartphones using the Qt based Cascades Native User-Interface framework.

At the Geneva Motor Show, Apple demonstrated CarPlay which provides an iOS-like user interface to head units in compatible vehicles. Once configured by the automaker, QNX can be programmed to handoff its display and certain functionality to an Apple Carplay device.[16][17]

On December 11, 2014, Ford Motor Company stated the company would be replacing Microsoft Auto with QNX.[18][2]


The QNX kernel contains only CPU scheduling, interprocess communication, interrupt redirection and timers. Everything else runs as a user process, including a special process known as proc which performs process creation and memory management by operating in conjunction with the microkernel. This is made possible by two key mechanisms — subroutine-call type interprocess communication, and a boot loader which can load an image containing not only the kernel but any desired collection of user programs and shared libraries. There are no device drivers in the kernel. The network stack is based on NetBSD code.[19] Along with its support for its own, native, device drivers, QNX supports its legacy, io-net manager server, and the network drivers ported from NetBSD.[20]

QNX interprocess communication consists of sending a message from one process to another and waiting for a reply. This is a single operation, called MsgSend. The message is copied, by the kernel,[citation needed] from the address space of the sending process to that of the receiving process. If the receiving process is waiting for the message, control of the CPU is transferred at the same time, without a pass through the CPU scheduler. Thus, sending a message to another process and waiting for a reply does not result in "losing one's turn" for the CPU. This tight integration between message passing and CPU scheduling is one of the key mechanisms that makes QNX message passing broadly usable. Most Unix and Linux interprocess communication mechanisms lack this tight integration, although a user space implementation of QNX-type messaging for Linux does exist. Mishandling of this subtle issue is a primary reason for the disappointing performance of some other microkernel systems such as early versions of Mach.[citation needed]

All I/O operations, file system operations, and network operations were meant to work through this mechanism, and the data transferred was copied during message passing. Later versions of QNX reduce the number of separate processes and integrate the network stack and other function blocks into single applications for performance reasons.

Message handling is prioritized by thread priority. Since I/O requests are performed using message passing, high priority threads receive I/O service before low priority threads, an essential feature in a hard real-time system.

The boot loader is the other key component of the minimal microkernel system. Because user programs can be built into the boot image, the set of device drivers and support libraries needed for startup need not be, and are not, in the kernel. Even such functions as program loading are not in the kernel, but instead are in shared user-space libraries loaded as part of the boot image. It is possible to put an entire boot image into ROM, which is used for diskless embedded systems.

Neutrino supports symmetric multiprocessing and processor affinity, called bound multiprocessing (BMP) in QNX terminology. BMP is used to improve cache hitting and to ease the migration of non-SMP safe applications to multi-processor computers.

Neutrino supports strict priority-preemptive scheduling and adaptive partition scheduling (APS). APS guarantees minimum CPU percentages to selected groups of threads, even though others may have higher priority. The adaptive partition scheduler is still strictly priority-preemptive when the system is underloaded. It can also be configured to run a selected set of critical threads strictly realtime, even when the system is overloaded.

Transparent Distributed Processing

Due to its microkernel architecture QNX is also a distributed operating system. Dan Dodge and Peter van der Veen hold US patent 6,697,876 based on the QNX operating system's distributed processing features known commercially as Transparent Distributed Processing. This allows the QNX kernels on separate devices to access each other's system services using effectively the same communication mechanism as is used to access local services.


OpenQNX is a QNX Community Portal established and run independently. An IRC channel and Newsgroups access via web is available. Diverse industries are represented by the developers on the site.[21]

Foundry27 is a web-based QNX community established by the company. It serves as a hub to QNX Neutrino development where developers can register, choose the license, and get the source code and related toolkit of the RTOS.[22]


PC Magazine stated in April 1983 that QNX was "an extraordinary piece of software". Citing its multitasking, the review concluded that "QNX gives you the power to maximize utilization of the PC's resources".[23]

See also


  1. 1.0 1.1 "RIM to buy QNX Software". Toronto: The Globe and Mail. The Canadian Press. 9 April 2010. Retrieved 2010-04-09.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
  2. 2.0 2.1 Thom Holwerda (2014-12-11). "Ford ditches Microsoft for QNX in latest in-vehicle tech platform". OSNews. Retrieved 2014-12-11.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
  3. Samuel Sidler (2004-03-24). "QNX4 Demo Disk: An Expounding Look". OpenQNX. Retrieved 2009-03-13.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
  4. "QNX Neutrino Realtime Operating System". QNX. 2010-07-15. Retrieved 2012-10-15.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
  5. US5745759
  6. QNX CAR http://www.qnx.com/products/qnxcar/
  7. QNX Staff (2004-08-17). "QNX Delivers Extremely Reliable Microkernel for Massively Scalable Routing System". Retrieved 2012-03-16.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
  8. CRS-1 and IOS XR Operational Best Practices
  9. Brad Reese- BradReese.Com (2006-09-26). "Which OS is behind IOS?". Retrieved 2012-03-16.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
  10. QNX Press Releases: source code availability
  11. foundry27 : View Wiki Page: UpdatedQNXSourceAccessPolicyFAQ
  12. Updated QNX Source Access Policy FAQ
  13. RIM Unveils The BlackBerry PlayBook, official press release, September 27, 2010
  14. "Research in Motion announces "BBX"". Engadget. Retrieved 2013-01-20.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
  15. Arthur, Charles (2011-12-07). "BlackBerry-maker RIM forced to drop BBX name for new software". London: Guardian. Retrieved 2013-01-20.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
  16. "Apple Inc CarPlay brings iPhone features to GM, BMW, Ford and other car dashboards". Financial Post. Retrieved 2014-03-28.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
  17. "BlackBerry's QNX: Why it's so valuable to Apple, Google, auto industry". ZDNet. Retrieved 2014-10-27.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
  18. Burns, Matt (December 11, 2014). "Ford Ditches Microsoft For QNX In Latest In-Vehicle Tech Platform". TechCrunch. Retrieved February 26, 2015.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
  19. Core Networking 6.4: Neutrino’s Next Gen Networking Stack and Foundry27 [1]
  20. Foundry27: Project Networking - Driver wiki page
  21. OpenQNX Community Portal: Announce
  22. QNX Press Releases: Foundry27
  23. Morris, James B. (April 1983). "The Powerful Tools of QNX". PC Magazine. p. 269. Retrieved 21 October 2013.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>

Further reading

External links