Category:Devices: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
(moved parts from main page to here)
Line 5: Line 5:


This page should help you to find build instructions for Qt for your board and some information on how to get the most out of your board. In case you are interested in the process of adding a new device please see the [[AddDevice | adding a new device]].
This page should help you to find build instructions for Qt for your board and some information on how to get the most out of your board. In case you are interested in the process of adding a new device please see the [[AddDevice | adding a new device]].
== Overview ==
* [[:Category:QtonPi|QtonPi]]: The Qt5 on RaspberryPi project
* [[:Category:Hardware-FAQ|HardwareFAQ]]: Frequently Asked Questions regarding Qt on various hardware platforms.
* [[:Category:Software-FAQ|SoftwareFAQ]]: Frequently Asked Questions regarding Qt’s software depedencies.
Latest device pages:
* [[:ODROID-XU3|ODROID-XU3]]: Qt 5 on the ODROID-XU3
* [[:Chromebook2|Samsung Chromebook 2]]: Qt 5 on the ARM-based Chromebook 2 under Linux


== FAQ ==
== FAQ ==

Revision as of 02:33, 22 May 2015

Devices supporting Qt

Qt runs on a variety of consumer devices and platforms across a number of different CPU architectures. This ranges from community supported devices like the Beagleboard family, Raspberry Pi to reference designs of chipset vendors like AMLogic, Broadcom, STMicroelectronics and Trident.

This page should help you to find build instructions for Qt for your board and some information on how to get the most out of your board. In case you are interested in the process of adding a new device please see the adding a new device.

Overview

  • QtonPi: The Qt5 on RaspberryPi project
  • HardwareFAQ: Frequently Asked Questions regarding Qt on various hardware platforms.
  • SoftwareFAQ: Frequently Asked Questions regarding Qt’s software depedencies.

Latest device pages:

FAQ

Device Profile Proposal

Device related considerations

Toolchain considerations

Supported Devices

Vendor Platform Type CPU GPU
AMLogic AML8726-M Tablets Cortex A9 Mali 400-M
Archos 70/101IT Tablets Cortex A8 PowerVR SGX530
BlackBerry PlayBook Tablets Dual Core Cortex A9 PowerVR SGX540
BlackBerry Z30 Consumer Dual Core 1.7 GHz Qualcomm Snapdragon S4 Pro Adreno 330
BlackBerry Z10 Consumer Qualcomm Snapdragon S4 processor Adreno 225
BlackBerry Q10 Consumer Qualcomm Snapdragon S4 processor with 1.5 GHz dual-core CPUs Adreno 225
BlackBerry Q5 Consumer Qualcomm Snapdragon S4 processor with 1.2 GHz dual-core CPUs Adreno 225
Broadcom 97420 Set-Top-Box MIPS Dual Core VideoCore
Broadcom 97425 Set-Top-Box MIPS Dual Core VideoCore
Broadcom RaspberryPi Developer ARM11 VideoCore
HardKernel ODROID-XU3 Developer Samsung Exynos 5422 (Cortex-A15 Quad and Cortex-A7 Quad) Mali-T628
Samsung Chromebook 2 (ARM) Developer Samsung Exynos (Cortex-A15 Quad + Cortex-A7) Mali-T628
STMicroelectronics ST7105 IP-TV SH430 2D GPU
STMicroelectronics ST7108 Set-Top-Box SH430 Mali 400
STMicroelectronics ST7540 IP-TV SH430 Mali 400
STEricsson Snowball Developer Cortex A9 Mali 400
Trident Shiner Set-Top-Box Cortex A9 PowerVR
Nokia Nokia N9 Consumer Cortex A8 PowerVR SGX530
TexasInstruments Beagleboard Developer Cortex A8 PowerVR SGX530
TexasInstruments Pandaboard Developer Dual Core Cortex A9 PowerVR SGX540
multiple multiple various Dual Core Cortex A9 Tegra2
Freescale i.MX 6 various Single to Quad Core Cotex A9 Vivante

Additional Vendor Notes

Texas Instruments

Android

There are a lot of rumors and statements around regarding OEM mainly (only?) supporting Android for there chipsets now/in the future. There is an idea in the room regarding how we can leverage that without having to have Java/Davlik.