|
588.4.4
by Kevin DuBois
split new info into new document |
1 |
Android Technical Details {#android_technical_details}
|
2 |
===============================
|
|
3 |
||
4 |
Mir Usage of Android Drivers
|
|
5 |
----------------------------
|
|
6 |
||
|
588.4.5
by Kevin DuBois
fix capitalization |
7 |
Mir relies on the libhybris library to use the Android drivers. This allows the |
8 |
drivers to use the bionic libc while Mir itself uses the standard GNU libc. |
|
|
588.4.4
by Kevin DuBois
split new info into new document |
9 |
|
10 |
Mir Display Modes
|
|
11 |
-----------------
|
|
12 |
||
|
588.4.5
by Kevin DuBois
fix capitalization |
13 |
When you're using Mir to drive the display of the Android device, Mir has |
14 |
a default way to display, as well as a backup mode that it can try if the |
|
|
588.4.4
by Kevin DuBois
split new info into new document |
15 |
default mode isn't working. |
16 |
||
17 |
* Default Mode
|
|
|
588.4.5
by Kevin DuBois
fix capitalization |
18 |
The default display mode uses the HWC HAL module from the Android drivers. |
|
588.4.4
by Kevin DuBois
split new info into new document |
19 |
Depending on the version and device, the default mode may also use the |
20 |
framebuffer HAL module. These modules are used to determine the display |
|
21 |
information, to synchronize with vsync, and to post to the display. The HWC |
|
22 |
is not used at this time to provide overlay support. |
|
23 |
* Backup Mode
|
|
24 |
The backup mode is used when the primary display mode is unavailable (due |
|
25 |
to system problems, missing shared libraries, or similar conditions) |
|
26 |
The backup mode will only use the framebuffer HAL module. This module is a |
|
27 |
bit more limited than the HWC module, and the driver support might be a bit |
|
28 |
less thoroughly tested. It still should give you a display though. |
|
29 |
||
30 |
Mir Device Support
|
|
31 |
------------------
|
|
32 |
||
33 |
In theory, all devices with that use the normal Android drivers abstractions |
|
|
1806.3.67
by Kevin DuBois
docs: |
34 |
should run Mir. Currently, we support HWC (hardware composer) version 1.0 and |
35 |
later. The deprecated FB HAL module from android's libhardware should also work. |
|
36 |
If you are attempting to get mir to work on a new device, check out |
|
37 |
\subpage android_new_device_bringup "this page" for suggestions on |
|
38 |
troubleshooting. You can also |
|
39 |
<a href="https://bugs.launchpad.net/mir">file a bug,</a> being very specific |
|
40 |
about the chipset, GPU, and driver versions that your phone has. |