Files
pmaports-rtwo/device/community/device-google-kukui/deviceinfo
T
Ingo Reitz 546a2c16f2 Revert "device-google-{asurada,cherry,corsola,kukui,trogdor}: add systemd-boot"
This reverts commit 4960460b82.

This produces an invalid depthcharge payload on devices with kernel packages that install both a .efi kernel and vmlinuz. mkinitfs runs boot-deploy with the .efi kernel (because `deviceinfo_generate_systemd_boot=true`) and depthcharge can't boot a kernel in this format

pkgrels have been bumped

Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7682>
2026-01-03 08:47:08 +01:00

35 lines
1.3 KiB
Plaintext

# Reference: <https://postmarketos.org/deviceinfo>
# Please use double quotes only. You can source this file in shell
# scripts.
deviceinfo_format_version="0"
deviceinfo_name="Google Kukui Chromebook"
deviceinfo_manufacturer="Google"
deviceinfo_codename="google-kukui"
deviceinfo_year="2020"
deviceinfo_dtb="mediatek/mt8183-kukui*"
deviceinfo_arch="aarch64"
# Device related
# chassis does not make sense here, will probably be removed (pmb#2255)
deviceinfo_chassis="convertible"
deviceinfo_external_storage="true"
deviceinfo_drm="true"
deviceinfo_disable_dhcpd="true"
# Bootloader related
deviceinfo_kernel_cmdline="quiet loglevel=2"
deviceinfo_cgpt_kpart="/boot/vmlinuz.kpart"
deviceinfo_cgpt_kpart_start="8192"
deviceinfo_cgpt_kpart_size="65536"
# We are supposed to use "kukui" board here, but lazor dts does
# not include kukui compatible which results in loading a wrong
# dtb. "mt8183" board may result in including dtbs that are for
# mt8183 but not related to Chrome OS devices which would increase
# image size. This doesn't happen for us because we provide only
# dtbs from deviceinfo_dtb variable and nothing more, so use "mt8183"
# board here.
deviceinfo_depthcharge_board="mt8183"
deviceinfo_depthcharge_compression="lzma"
deviceinfo_generate_depthcharge_image="true"