Currently there is a limit of 500 changes per page, giving us only
those when repopicking a query. By observing the "_more_changes" field
in the response and adding the "start" parameter to the query we can
do pagination and return all changes
Test: repopick -p -Q "branch:lineage-23.0"
Result before: 500 changes
Result after: 1094 changes (correct count as of time of commit)
Change-Id: I00304bc2c87b75cef89a26838da3dd1b1f0e65db
Needed for KERNEL_CLANG_VERSION if TARGET_KERNEL_CLANG_VERSION hasn't been set by the device config
It's boring to change it on each Google change ...
Change-Id: I1d682611cbf6c60d7ae6227b0b5afde591adf471
How-to:
1. Build and install cuttlefish packages by following [1]
2. Build LineageOS image and hosttar
```
source build/envsetup.sh
breakfast cf_phone_x86_64
m hosttar updatepackage
```
3. Extract LineageOS image and hosttar
```
mkdir lineage-cvd
cd lineage-cvd
unzip <LineageOS tree>/out/target/product/vsoc_x86_64/lineage_cf_phone_x86_64-img.zip
tar xzvf <LineageOS tree>/out/host/linux-x86/cvd-host_package.tar.gz
```
4. Run it
```
HOME=$PWD ./bin/launch_cvd
```
5. Open https://127.0.0.1:8443 in browser, and enjoy
[1]: https://github.com/google/android-cuttlefish?tab=readme-ov-file#debian-packages
Change-Id: I7d69db7be99d250f02d7e76fd398ebf5c2ca7c5f
Some DTBOs might use symbols from other DTBOs and require them to be
applied before them.
Sort them based on the __symbols__ and __fixups__ nodes, by creating a
dependency graph.
Change-Id: I40acf5da6b673b636a91f75ae3f3c634f2b5c505
This depends on a kernel headers tarball path being passed in
TARGET_PREBUILT_KERNEL_HEADERS, in the style that the kleaf kernel
platform build generates.
Change-Id: Ib82659fa44ef221e73d0d129daafbaae6bad87a2
There are still lots of users for those and maintainers haven't been
very responsive, so make it a build warning and remove them in 23.0.
Change-Id: Ibf59f45921f622b8eca6df6d57e9e3557847af51
This is now required for all handheld devices to make use of the
new software credentials feature
Bug: 344511668
Test: run cts -m CtsCredentialManagerTestCases -t android.credentials.cts.CtsCredentialManagerDeviceTest
Change-Id: I7e0211ca5c7f817789d9b33a6a0a1a25054530b4
Some OEMs add their own properties to avoid merging incompatible
overlays for different devices with the same QCOM soc.
Change-Id: Ic5b38a122173d8e9ecc1f0f399411cb37acf3150
For targets that uses mainline kernel, the kernel tree usually only
contains configs on top of the upstream repository.
In such case, if we put the configs in elsewhere, we can simply just
track the upstream kernel repo, without needing to import configs.
Example usage:
TARGET_KERNEL_CONFIG_EXT := \
$(COMMON_PATH)/kconfig/platform_defconfig \
$(COMMON_PATH)/kconfig/common-addons.config
TARGET_KERNEL_CONFIG_EXT += \
$(DEVICE_PATH)/kconfig/device.config
Change-Id: I021ffb76d0c0612343cff7b5c81541c2b88ef7e6
* Many Qualcomm targets that uses boot header v0 or v1
have the DTBs appended to the end of kernel image.
* In downstream msm kernels up to msm-4.19, Appending DTBs
is handled in the kernel tree. However, on msm-5.4 and
newer msm kernels, and on mainline kernel, This is not
supported.
* Normally, DTB processing depends on how the bootloader
loads it and should not be handled in the kernel tree,
so we handle it here.
* Instead of appending all DTBs by default, Get the list of
DTBs that needs to be included from a variable, so that
we don't need to modify dts Makefile to exclude unwanted
DTBs, and we could also ensure the DTBs are appended in
a specific order.
Change-Id: I603d1ebac5ee808bad045b85f9868d572d52cb80
