Age | Commit message (Collapse) | Author |
|
Format *.cpp according to the new .clang-format-2. The following command
was used to generate this change:
$ find . \( -name \*.cpp -o -name \*.h \) -exec clang-format \
--style=file -i {} \;
Test: mm
Bug: 171699326
Change-Id: I0b5681b2c0b72770f327e6783eb90eb05250a7ac
|
|
Now that we move libboot_control to boot/1.1, the definition of
bootloader_message_ab will hide behind the implementation details for
vendor HALs. As this library isn't used in practice, we just inline the
offset here.
Bug: 131775112
Test: build
Change-Id: I64babcad6a421cab5858ab818f392eca196a0fe2
|
|
Test: treehugger
Change-Id: I6ed1afb59eed03ca5a7d06a697ac8b04e74f494d
|
|
Test: treehugger
Change-Id: I1873022abde51b71b49e8d89bdaada044530987a
|
|
Also rename boot_control_copy away from default.
boot_control_copy isn't a shipping implementation.
boot_control_bcb is the actual default.
Bug: 78793464
Test: compiles
Change-Id: I2bdbcb80605ca396dbfa69b837be381cbcc6e3e7
Merged-In: I2bdbcb80605ca396dbfa69b837be381cbcc6e3e7
|
|
See build/soong/README.md for more information.
This effectively moves some of these targets from /system/xbin to
/system/bin, as Soong is not supporting xbin. I've attempted to fix and
find any external dependencies to these paths.
Test: m anrd app-launcher bootctrl.default bootctl cpustats crypto iotop
Change-Id: I3eb58d8a260884652b5ee827ac88ece429d76448
|
|
<bootloader.h> has been exported by libbootloader_message as
<bootloader_message/bootloader_message.h>.
Test: mmma -j system/extras/boot_control_copy
Change-Id: I013bbb393906a19acd95f3c5fb8905f7aa0d7ed1
|
|
Bug: 74763691
Test: make -j64
Change-Id: I55fb951eea449c27aa0a4a5e9ab1a4dca09dbfa5
(cherry picked from commit 41afebb109a6f4b444c43622daa9707820eef6ef)
|
|
* Remove unused variables.
* Fix redefined macro warnings.
* Fix sign-compare warnings.
* Fix 'return false' in main().
* Keep existing warnings to fix later.
Bug: 66996870
Test: build with WITH_TIDY=1
Change-Id: Ib92ef5297693595fb84ed4f8e61665bda4cee312
|
|
fs_mgr_get_entry_for_mount_point() is switching to a C++ only API (using
std::string). Do a minimum conversion here to adopt that change.
Bug: 67024518
Test: make and boot sailfish
Change-Id: I191fd0043815d75a799eb4001437abb107af6e79
|
|
Bug: https://github.com/android-ndk/ndk/issues/398
Test: builds
Change-Id: Icfccc98e1ff5aaa53b288e2aba0efe2c2c77a623
|
|
fstab.device is for backward compatibility in legacy devices.
As it doesn't have fstab entries in device tree (for early mount) so we
can just use the ordinary fs_mgr_read_fstab().
For new devices having early mount, it should use
fs_mgr_read_fstab_default() instead.
Bug: 35811655
Test: boot sailfish
Change-Id: I70b64787e600d6e338e57f2a31bad188a39d433d
|
|
The fstab settings of early-mounted partitions (e.g., /vendor)
will be in kernel device tree. Switch to the new API to get the
whole settings with those in device tree:
fs_mgr_read_fstab_with_dt("/fstab.device")
The original default /fstab.{ro.hardware} might be moved to
/vendor/etc/. or /odm/etc/. Use another new API to get the default
fstab instead of using the hard-coded /fstab.{ro.hardware}.
This API also includes the settings from device tree:
fs_mgr_read_fstab_default()
Bug: 35811655
Test: build pass
Change-Id: I14bee88b9f599b7bbc2be56042684709e5946de2
|
|
It requires libbase due to fs_mgr is using <android-base/logging.h>
Bug: 34336098
Test: compile
Change-Id: I120a8f6c7e7bf052081e8c97a358384665927088
|
|
Bug: 29193360
Change-Id: I518e786eb2d45b6a71c25dc4402e3bbebef20dc6
|
|
Bug: 28705665
Change-Id: I9a8f0bd587c70ff3c60666c9f7dfba2d6e809336
|
|
Bug: http://b/26936282
Change-Id: I1b9c6c9bb06944c32abcb871279d056eea0fb11a
|
|
The build system does not use headers in LOCAL_SRC_FILES. To prevent
typos, it's becoming a warning to add something to LOCAL_SRC_FILES that
is not used.
Change-Id: I0ced87726dae5fcd4209d9ff1f83fa611817ecd3
|
|
Bug: 24571219
Change-Id: Ib7a4374974c2d0d9225caa1e43d0b78251a36bd2
|
|
Change-Id: I3816f7f5352f204795f45d782b8ec80493d78491
|
|
The getCurrentSlot() method wasn't returning the right value if
setActiveBootSlot() was called with another slot since last reboot.
Instead of peeking in the misc partition, just look at the dev_t for
/system and compare it with the dev_t for system_a and system_b.
Bug: 24201805
Change-Id: I601ab5e355e0f423637e6867d0afda97f68b57fd
|
|
This boot_control HAL implementation emulates A/B by copying the
contents of the boot partition of the requested slot to the boot
partition. It hence works with bootloaders that are not yet aware of
A/B. This code is only intended to be used for development.
Change-Id: Ifcc1ff19530f9e6db1de882807a25c785e1959de
|