| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
+ convert to QemuOpts* initialization functions.
Change-Id: I5a245ed2de068af49fdc92de8e3e834d0f49aa27
|
| |
|
|
| |
Change-Id: Ibd11e84a4d48c1d6c4a168056869a7480bc89930
|
| |
|
|
|
|
|
|
|
|
|
| |
Get rid of qemu_timer_new() implementation, and update all
callers to use qemu_timer_new_ms() or qemu_timer_new_ns()
instead.
Rename qemu_new_timer_scale() to qemu_new_timer() to follow
upstream conventions.
Change-Id: Id2c04f8597ec5026e02f87b3e2c5507920eb688e
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove one layer of indirection between the core's DisplayState
and a ProxyFramebuffer object. The main ideas behind this patch
are that:
- We don't need a QFrameBuffer object when in the core process,
each proxy can receive display updates directly from QEMU.
- The DisplayChangeListener is really lame: its can't dissociate
between several listeners that use the same callback pointers,
so introduce DisplayUpdateListener in console.h to work around
this. This is preferably to modifying DisplayChangeListener
which is going to introduce conflicts with upstream.
- Simplify a lot the console code and display-core. Note that
we can have several framebuffer clients at the same time now.
Note that QFrameBuffer is still used by both the UI program and
the standalone emulator.
Change-Id: I6d5ad6ecd9b34b9d9d1a30ea5000e875c285e84e
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes a problem where the core's framebuffer was
incorrectly initialized to a pitch of width*4 by default
(instead of width*2 when using a 16-bit framebuffer).
The reason for this was complex, but essentially, when the
machine initialization was moved before the display one in
vl-android.c, this changed the way the DisplayState was
initialized.
Also get rid of the useless and confusing "display_state"
global in vl-android.c (not the same than "display_state" in
console.c)
Change-Id: If8e2b8baf7ccaeedcb66da0174cc529521d67a60
|
| |
|
|
|
|
|
|
|
|
|
| |
The main reason for this is to clarify initialization for UI that starts core,
and UI that attaches to an existing core. In this CL I did:
- Removed -initdata option that seems obsolete (doesn't affect anything in the code)
- Passed through -timezone option that doesn't affect anything in the UI, and is needed
only in the core.
- Removed dependency on AVD info from the core (core needed only virtual device name)
Change-Id: Ie631249848a1b5b8d837c0c7b201a40ee7e4a367
|
| | |
|
| | |
|
| |
|
|
| |
Change-Id: I9fd9170f2b2e3ad7d80071888f7da2ead54c21cf
|
| |
|
|
| |
Change-Id: Ica9022695d83fb48a8c25fdb1e1f0dc1c63747ff
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change integrates many changes from the upstream QEMU sources.
Its main purpose is to enable correct ARMv6 and ARMv7 support to the
Android emulator. Due to the nature of the upstream code base, this
unfortunately also required changes to many other parts of the source.
Note that to ensure easier integrations in the future, some source files
and directories that have heavy Android-specific customization have been
renamed with an -android suffix. The original files are still there for
easier integration tracking, but *never* compiled. For example:
net.c net-android.c
qemu-char.c qemu-char-android.c
slirp/ slirp-android/
etc...
Tested on linux-x86, darwin-x86 and windows host machines.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
