| 7654e7efee943bdbaf167170a087388c54681366 |
|
11-Jul-2014 |
David 'Digit' Turner <digit@google.com> |
emulator-arm64: ARM64 wrapper for QEMU executable.
This patch adds two new binaries (emulator-arm64 and emulator64-arm64)
which act as a wrapper for QEMU-based emulation engines for ARM64
emulation (and ARM64 _only_).
The (prebuilt) qemu binary must be located under:
$PROGRAM_DIR/qemu/$SYSTEM/qemu-system-aarch64$EXE
Where:
$PROGRAM_DIR is the location of the 'emulator-arm64' binary.
$SYSTEM is a host system tag (e.g. linux-x86 or linux-x86_64)
$EXE is the host executable extension.
The program is in charge of parsing command-line arguments,
computing AVD configuration, then calling the QEMU program
with a (very long) list of configuration arguments.
See https://qemu-android.googlesource.com/qemu-ranchu/ for
scripts used to rebuild the QEMU prebuilt binary from
sources.
Change-Id: Ifcb9dd50fc5d83a864a1f957d12b1c199e0504fb
/external/qemu/android/avd/util_unittest.cpp
|
| fb8aca0ae8f679e356ee0b06fe206e9df4408f9e |
|
21-Jun-2014 |
David 'Digit' Turner <digit@google.com> |
Fix emulation of old platform images.
A previous patch introduced a regression that prevented the
emulator from properly booting older platform images.
The root cause of the problem is that old SDK platforms
(e.g. Gingerbread), do not provide a build.prop file.
For these, the target API level is extracted from the
AVD's config.ini file instead.
A series of recent changes made the emulator initialization
code overwrite this value from the one extracted from build.prop,
and unfortunately, when this file didn't exist, an API level value
of 1000 was returned.
This made the emulator misconfigure the emulation parameters,
in particular, the cache partition was configured to be ext4,
while the safety code later detected the image to be yaffs2
and refused to go-on.
This fixes the issue by avoiding the overwrite.
Change-Id: I529ff991a9e8df42957c40e1e5929c0472773b14
/external/qemu/android/avd/util_unittest.cpp
|
| e49c26a1fbc70f5c3920ee3ca8433a6cb440193d |
|
18-Jun-2014 |
Vince Harron <vharron@google.com> |
AdbdCommunicationMode: choose default from API level
propertyFile_getAdbdCommunicationMode: If API level <16, force
"ro.adb.qemud" to 0. If API level >= 16, use value from
"ro.adb.qemud" or default to 1
(commit c13daef7bdc0982084 "Use QEMU pipe for ADB communication"
was first released in API 16 system images)
Refactored integer parsing, memory management and validation code into
propertyFile_getInt
Added unit tests for propertyFile_getInt/ApiLevel/AdbdCommunication
Change-Id: I32e3e16aa4e183546936c4841d071bd709c0780e
/external/qemu/android/avd/util_unittest.cpp
|
| fd442bdd16c9debca9088780a78100a7dd1a3ca7 |
|
01-Apr-2014 |
David 'Digit' Turner <digit@google.com> |
Improve backend selection based on target AVD CPU.
This change improves the way the 'emulator' launcher program
chooses the emulation backend, based on the target AVD CPU
architecture.
+ Introduce emulator_getBackendSuffix and appropriate
unit test.
+ Use it in android/main-emulator.c
+ Remove the hack that forced a target ABI of 'x86_64' to
be mapped internally to 'x86'.
Change-Id: Ifbda9c8e4c032df5e8ca089f1e9272c844c00c32
/external/qemu/android/avd/util_unittest.cpp
|