Common config.fs/$TARGET_FS_CONFIG_GEN AID/fs configuration
file for all chipset inheriting from base.mk.
Since legacy device-specific android_filesystem_config.h and
config.fs do not co-exist, temporarily include config.fs only
if legacy file is absent. Once all legacy, device-specific
files have been deleted, config.fs can be made unconditional.
Change-Id: Ie100d0cd9db808b82d99be7139f0709390c7f3a2
On builds where A/B support is enabled the system image acts as the
rootfs. In this case we can no longer create the non-hlos image mount
points at run time as we used to. We now create them as part of the
build itself.
Change-Id: I30d98f7c50fca3ce7117b9b8d87150655bb5b440
This can be checked by looking for a rild service in system.
If it's missing, then a vendor ril service is being used, in
our case, it is qcrild.
Change-Id: I5378de6eec4ff2511a49c19c0fc474658efe338f
Partitions that use vbmeta_system can be found by looking at
avb flag in fstab from boot ramdisk.
--flags 2 makes the verification function of avb always return a
positive result.
--set_hashtree_disabled_flag builds the vbmeta images with the
HASHTREE_DISABLED bit set and as a result they don't need to manually
disable dm-verity via e.g. 'adb disable-verity'.
The rest of the configuration is taken from
https://source.android.com/devices/tech/ota/dynamic_partitions/implement#avb-configuration-changes
Change-Id: I381feef8f6fefc8449ca50d85d704b67bcc8a77e
Partition sizes can be found by query-ing sysfs.
For example, for super partition.
> ls -la /dev/block/by-name/super
lrwxrwxrwx 1 root root 16 1970-03-23 06:51 super -> /dev/block/sda17
> cat /proc/partitions | grep sda17
259 1 8388608 sda17
The size needs to be multiplied by the block size used by
/proc/partitions, which is 1024 bytes.
Logical partitions found inside the physical super partition
can be found by looking for entries with the logical flag in the
fstab inside boot ramdisk.
