| 4732aee0622005bc612f75d0319e6e3a057301b4 |
|
30-Apr-2012 |
Vladimir Chtchetkine <vchtchetkine@google.com> |
Fix Windows build
Change-Id: I732fa0d756656ad9976eddd06b16644e208aa512
/external/qemu/android/sdk-controller-socket.c
|
| 7136b053b7fc7840ec64e01d1d19ab822e1f949a |
|
10-Apr-2012 |
Vladimir Chtchetkine <vchtchetkine@google.com> |
Use new SdkController communication protocol for emulation ports
android/sdk-control-socket.* has replaced android/android-device.* as the back-bone
of communicating with SDK controller on the device. The major differences are:
- New communication protocol uses just one (async) socket connection to communicate
with the device (the old one used two sockets: one sync, and another - async).
- New communication protocol connects to one TCP port (1970 in this CL) for all emulation
ports. Channel multiplexing is done by using port names, and assigning a separate socket
for communication inside each separate port. The old protocol had separate TCP ports for
each emulation ports (1968 for sensors, and 1969 for multi-touch)
Change-Id: I779fcbdfba2f9b4c433a9d76a567975708b00469
/external/qemu/android/sdk-controller-socket.c
|
| c8aa2c570d30098da59f1967d5158024ed28570d |
|
06-Apr-2012 |
Vladimir Chtchetkine <vchtchetkine@google.com> |
Implements SDKCtlSocket that implements communication protocol wih SdkController
In addition, this CL contains some minor tweaks to async-socket, and
async-socket-connector that improve tracebility.
Change-Id: Ib1309b19dcd02e96379155fea7015019d93160e7
/external/qemu/android/sdk-controller-socket.c
|