Lines Matching refs:emulator

8 communication channel between the emulated system and the emulator program
10 the emulator program is using qemu pipes (see ANDROID-QEMU-PIPE.TXT for details
14 emulator without requiring special kernel support; this simplifies a lot of
21 The emulator provides 'services' to various parts of the emulated system.
44   to the emulator. It does so by:
59   will pass all messages between clients and emulator services. Thus,
63      emulator <==serial==> qemud <---> /dev/socket/qemud <-+--> client1
86   Zero-sized packets are silently discard by qemud and the emulator and
90   emulator. These are the following:
93       name to the daemon, the later sends to the emulator:
101     - The emulator can respond in case of success with:
114       the corresponding emulator service will be passed through the
118       send through channel 0 this message to the emulator:
122     - If an emulator service decides, for some reason, to disconnect
123       a client, the emulator will send to the daemon (on channel 0):
131     - Any other command sent from the daemon to the emulator will result
136 - Which exact serial port to open is determined by the emulator at startup
142 - The code to support services and their clients in the emulator is located
145   The daemon's source is in $ROOT/development/emulator/qemud/qemud.c
151   This is used by $ROOT/developement/emulator/sensors/sensors_qemu.c which
152   implements emulator-specific sensor support in the system by talking to
153   the "sensors" service provided by the emulator (if available).
178      emulator <-+--> /dev/qemu_pipe/qemud:srv1 <---> client1
182   In the pipe model each client gets connected to the emulator through a unique
191 different protocol to communicate with the emulator.
196 The old scheme also used a serial port to allow the daemon and the emulator
211     emulator <==serial==> qemud <-+--> /dev/socket/qemud_gsm <--> GSM client
232  - at startup, the emulator does query the channel numbers of all services
240    messages to the emulator instead).
252 This old scheme was simpler to implement in both the daemon and the emulator
263 The current implementation moves any service-specific code to the emulator,