pmaports/device/device-google-crosshatch/deviceinfo
Zhuowei Zhang 4fe8ceeee1
google-crosshatch: fix build with downstream kernel (!1016)
The downstream kernel doesn't provide a separate dtb file,
but the experimental mainline kernel does.

Previously, the deviceinfo specified a dtb file for both kernels,
and pmbootstrap ignored the missing file for downstream kernel.

pmbootstrap now errors when the dtb file is missing, so this
fixes the downstream kernel by specifying a dtb file only for
the upstream kernel.
2020-03-01 15:57:13 +03:00

38 lines
1.5 KiB
Text

# 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 Pixel 3 XL"
deviceinfo_manufacturer="Google"
deviceinfo_codename="google-crosshatch"
deviceinfo_date=""
deviceinfo_dtb_downstream=""
deviceinfo_dtb_mainline="qcom/sdm845-crosshatch"
deviceinfo_append_dtb_mainline="true"
deviceinfo_modules_initfs=""
deviceinfo_arch="aarch64"
# Device related
deviceinfo_keyboard="false"
deviceinfo_external_storage="false"
deviceinfo_screen_width="1440"
deviceinfo_screen_height="2960"
deviceinfo_dev_touchscreen=""
deviceinfo_dev_touchscreen_calibration=""
deviceinfo_dev_keyboard=""
# Bootloader related
deviceinfo_flash_method="fastboot"
deviceinfo_kernel_cmdline="console=ttyMSM0,115200n8 printk.devkmsg=on msm_rtb.filter=0x237 ehci-hcd.park=3 service_locator.enable=1 cgroup.memory=nokmem lpm_levels.sleep_disabled=1 usbcore.autosuspend=7 buildvariant=user"
deviceinfo_generate_bootimg="true"
deviceinfo_flash_offset_base="0x00000000"
deviceinfo_flash_offset_kernel="0x00008000"
deviceinfo_flash_offset_ramdisk="0x01000000"
deviceinfo_flash_offset_second="0x00f00000"
deviceinfo_flash_offset_tags="0x00000100"
deviceinfo_flash_pagesize="4096"
# Pixel 3 XL uses 4096 byte per sector UFS flash, unlike most devices.
# fdisk -l shows "Note: sector size is 4096 (not 512)"
deviceinfo_rootfs_image_sector_size="4096"
# Framebuffer doesn't work yet. For now, avoid waiting for a nonexistent framebuffer.
deviceinfo_no_framebuffer="true"