| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ |
|
|/ /
| |
| |
| |
| |
| | |
Perform null check before calling r->transfer_handler.
Change-Id: Ide3cd7edc7bde12a0635572bfa72f3a6dd05a926
|
|\ \ |
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
Even putenv("X=y") is bad because the "string becomes part of the
environment; changing it later will change the environment."
(http://www.kernel.org/doc/man-pages/online/pages/man3/putenv.3.html)
Change-Id: I0d57204a7020649493fb005c962951407d40fa45
|
|\ \ |
|
|/ /
| |
| |
| |
| |
| |
| | |
Windows builds and possibly others do not have putenv. Using
"#ifdef HAVE_SETENV" which is common in qemu.
Change-Id: I2cd6770a77cd192440ff4dc6a624568eb27d5558
|
|\ \
| |/
|/| |
|
|/
|
|
|
|
|
|
| |
POS34-C. Do not call putenv() with a pointer to an automatic variable as
the argument:
Change-Id: I0c973edd2cc8d6c86287ec0258bca6a06f319bfb
https://www.securecoding.cert.org/confluence/display/seccode/POS34-C.+Do+not+call+putenv()+with+a+pointer+to+an+automatic+variable+as+the+argument
|
|\ |
|
|/
|
|
|
|
|
| |
Core port related calls are no longer needed, since UI is aware of
core's base port on attachment to the core
Change-Id: Ic211fc9b02cb652009360f80917e90c44d941878
|
|\ |
|
|/
|
|
| |
Change-Id: I2feb813314163b94781ffe765eb23527b6c4a0f1
|
|\ |
|
|/
|
|
|
|
|
|
|
|
|
| |
FB and UE services overwrite the socket's read callbacks, making the console
unavare of the fact that console client gets disconnected. As the result,
console clients for FB and UE stays alive after UI has exited, making it
impossible to attach another UI. To fix this, we add socket read callbacks
to the FB and UE service that monitor the disconnection event and destroy
their console clients on such events.
Change-Id: I82e714f33ccc81bc04ca47eda6fbb8fab4a313f9
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I503aa691cada5250b76167a923d4a226d20ee41d
|
|\ \
| |/
|/| |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This change is used when using a magic skin (e.g. -skin 800x600)
or when using the full Android build system, in order to determine
a good default for the RAM size.
Change-Id: I900e28146592cdd3f0df9b3f1828b119309eea85
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| | |
This makes it easier to launch the core (qemu-android) with the same
set of options than the stand-alone emulator.
Change-Id: I55d0007f83280ffc5b9a26adc1300472013ff93d
|
|\ \
| |/
|/| |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch makes "qwerty2" the default charmap for skins that
don't specifiy one explicitely. Note that the "qwerty" charmap
is here for historical reasons only. All skins provided by all
SDK Android platforms explicitely mention "qwerty2", so this patch
will mainly impact "magic skins" like those created by an option
like "-skin 1024x768".
This gets rid of the obsolete "qwerty" charmap (it was never
used by any of the skins provided by the SDK, and is incorrect).
+ Simplify android/charmap.[hc] code.
+ Lazy-load the charmap name in hw/goldfish_events_device.c
|
|\ |
|
| |
| |
| |
| | |
Change-Id: If832bc5844945f7a2027b2f8d09393586545d8d5
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| | |
This provides a new read i/o port to return the framebuffer's format to the
kernel driver.
Change-Id: Ifd1c4d8a4dc75fa73d5f6750e0b501c34468aec5
|
|\ \
| |/ |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This modifies the emulator so support 32-bit framebuffers.
You can create such a frame-buffer using one of these methods:
- Add a "bpp 32" line to the "display" element of your skin
- Use the new 'magic' skin option format: e.g. -skin 320x480x32
Note that the result will be hideous since the kernel driver still
thinks the hardware is only 16-bits. This will be addressed in a
later patch to hw/goldfish_fb.c and to the kernel driver
($KERNEL/drivers/video/goldfishfb.c)
Change-Id: I0fc700c4a4cb8521076605324e15ed34e5d01136
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Proximity sensor is added in emulator and avd ini file is modified to
be able add a proximity seensor to a avd.
Change-Id: I4d2645c0c4861511451b606e18d2fd9b9a2d27ed
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This patch modifies the framebuffer's update callback to compute the minimum
bounding rectangle of each framebuffer update. Before that, the code only
computed the minimum and maximum Y coordinates, assuming xmin=0 and xmax=width-1.
This should help reduce un-necessary traffic/churn for our core->UI framebuffer
protocol.
Moreover, introduce the ability to support framebuffers / display surfaces with
different depths. This is a first step towards providing 32-bit framebuffers to
the guest system to slightly speed-up emulated rendering on Gingerbread and
above.
Change-Id: I6194824ce67a3b1d6d95b5d97ddec3ef459e408e
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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: I54491e3e9910591aedcd700a9a350dc7a6fa7127
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: Ib2dff72c808614cd6ded096d62717afc1c41e667
|
|\ \ \
| |/ /
|/| | |
|
|/ /
| |
| |
| | |
Change-Id: I20c83aab5fbd0c87b319ac84d7911eb09b69632b
|
|\ \ |
|
|/ /
| |
| |
| | |
Change-Id: Ib5c43306376e51a2a0866868f990ca8c8899ae7a
|
|\ \ |
|
|/ /
| |
| |
| |
| |
| |
| | |
The reason for the build breakage is still mysterious though.
Were the system headers updated during the last system update ?!?
Change-Id: Ib0ea2b54bf7ffad907752c3a82fb4bbe686425a5
|
|\ \ |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
The integration failed to update some tcg files resulting in a crash when
trying to trace stuff, and properly a few other problems.
Undo it. We will re-integrate tcg changes later.
Change-Id: I6fd3f7f442ce3bc70cb6995c04684cb1acfaa378
|
|\ \ |
|
|/ /
| |
| |
| | |
Change-Id: I523f4464cfbbd02aff93031660d2ee2f80d54921
|