diff options
author | David 'Digit' Turner <digit@google.com> | 2009-08-28 19:36:27 +0200 |
---|---|---|
committer | David 'Digit' Turner <digit@google.com> | 2009-08-28 19:36:27 +0200 |
commit | cd059b15f2c7df69f4a087bd66900eb172e41d1c (patch) | |
tree | aa9beca50259c642b40490a84329f4b1c4e4a68d /CHANGES.TXT | |
parent | b764e25f5a227ab38ae3980578aa090a561f1fca (diff) | |
download | external_qemu-cd059b15f2c7df69f4a087bd66900eb172e41d1c.zip external_qemu-cd059b15f2c7df69f4a087bd66900eb172e41d1c.tar.gz external_qemu-cd059b15f2c7df69f4a087bd66900eb172e41d1c.tar.bz2 |
Added two new hardware properties to control AVD partition sizes.
disk.systemPartition.size (default 66MB)
disk.dataPartition.size (default 66MB)
If the emulator detects that an image file is larger than the corresponding
setting, it will do the following:
- for AVDs running from the SDK, an error message will be printed and
the emulator aborts. Note that this can only happen if there are some
serious mis-configuration of AVDs anyway.
- when launching the emulator from the Android build system, a warning
will be printed, and the partition size will be automatically adjusted
at launch.
Previously, trying to launch an over-sized system image would result in the
emulated system booting, but then failing to find certain files, depending on
how the yaffs2 disk images are built. This caused hard-to-debug issues.
Note that the option -partition-size <size> can be used to override the AVD's
setting at runtime.
Diffstat (limited to 'CHANGES.TXT')
-rw-r--r-- | CHANGES.TXT | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/CHANGES.TXT b/CHANGES.TXT index aca11fd..f04d275 100644 --- a/CHANGES.TXT +++ b/CHANGES.TXT @@ -28,6 +28,30 @@ IMPORTANT BUG FIXES: - The key-bindings for the Menu button (F2 and PageUp by default) didn't work due to a typo. +OTHER: + +- Added two new hardware properties disk.systemPartition.size and + disk.dataPartition.size to specify the size of the system and data partition + in a given AVD. + + If the emulator detects that an image file is larger than the corresponding + setting, it will do the following: + + - for AVDs running from the SDK, an error message will be printed and + the emulator aborts. Note that this can only happen if there are some + serious mis-configuration of AVDs anyway. + + - when launching the emulator from the Android build system, a warning + will be printed, and the partition size will be automatically adjusted + at launch. + + Previously, trying to launch an over-sized system image would result in the + emulated system booting, but then failing to find certain files, depending on + how the yaffs2 disk images are built. This caused hard-to-debug issues. + + Note that the option -partition-size <size> can be used to override the AVD's + setting at runtime. + ============================================================================== Changes between 1.11 and 1.10 |