forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/device/testing/device-wileyfox-crackling/deviceinfo

39 lines
1.8 KiB
Text
Raw Normal View History

Add device: wileyfox-crackling (!485) Initial support for Wileyfox Swift - System boots - USB networking works - Display and touch works - Weston, XFCE4, Plasma Mobile works with software rendering - fb.modes added but charging-sdl still don't work - System allways reports charge level at zero [ci:skip-build]: already built successfully in CI
2019-07-08 18:20:20 +00:00
# Reference: <https://postmarketos.org/deviceinfo>
# Please use double quotes only. You can source this file in shell scripts.
deviceinfo_format_version="0"
deviceinfo_name="Wileyfox Swift"
deviceinfo_manufacturer="Wileyfox"
deviceinfo_codename="wileyfox-crackling"
device/device-*: automatically add deviceinfo_year from wiki (!1036) Download: https://wiki.postmarketos.org/index.php?title=Special:CargoExport&tables=Devices&&fields=Codename%2C+Released&&group+by=Codename&order+by=%60Codename%60%2C+%60Released%60&limit=5000&format=csv cd device for device in device-*; do year=$(grep -oP "${device#device-},\K2\d{3}" ../results.csv) [[ -n "$year" ]] || continue sed -i "s/deviceinfo_date=\"\"/deviceinfo_year=\"$year\"/" "$device/deviceinfo" done devices=$(git ls-files -m -- . | xargs dirname | sort -u | xargs echo) pmbootstrap checksum $devices
2020-03-07 16:10:22 +00:00
deviceinfo_year="2015"
wileyfox-crackling: use appended DTB instead of QCDT (!907) The Wileyfox Swift is the only mainline MSM8916 device using QCDT at the moment. The other devices do not have unique qcom,board-ids that could be used within QCDT. So far this has worked fine for the Wileyfox Swift. However, in preparation to *optionally* load the modem we now need two separate pairs of DTBs (one with modem and one without modem). This is simple to implement using appended DTBs, but not possible with QCDT. So let's stop using QCDT entirely for mainline, and use appended DTBs for wileyfox-crackling.
2020-01-15 20:20:16 +00:00
deviceinfo_dtb_mainline="qcom/msm8916-longcheer-l8150"
wileyfox-crackling: add option to enable modem (!907)
2020-01-18 11:40:15 +00:00
deviceinfo_dtb_mainline_modem="qcom/msm8916-longcheer-l8150-modem"
wileyfox-crackling: use appended DTB instead of QCDT (!907) The Wileyfox Swift is the only mainline MSM8916 device using QCDT at the moment. The other devices do not have unique qcom,board-ids that could be used within QCDT. So far this has worked fine for the Wileyfox Swift. However, in preparation to *optionally* load the modem we now need two separate pairs of DTBs (one with modem and one without modem). This is simple to implement using appended DTBs, but not possible with QCDT. So let's stop using QCDT entirely for mainline, and use appended DTBs for wileyfox-crackling.
2020-01-15 20:20:16 +00:00
deviceinfo_append_dtb_mainline="true"
wileyfox-crackling: add option to enable modem (!907)
2020-01-18 11:40:15 +00:00
deviceinfo_append_dtb_mainline_modem="true"
device-wileyfox-crackling: enable display on boot (!830) This commit adds necessary kernel modules to initramfs to enable display early on boot which allows FDE and charger-sdl to work
2019-12-24 17:43:46 +00:00
deviceinfo_modules_initfs_downstream=""
wileyfox-crackling: optimize module load order (!836) This fixes warnings on boot.
2019-12-26 11:08:31 +00:00
deviceinfo_modules_initfs_mainline="panel-booyi-otm1287 msm rmi_i2c qcom-spmi-vadc dumb-adc-battery"
wileyfox-crackling: add option to enable modem (!907)
2020-01-18 11:40:15 +00:00
deviceinfo_modules_initfs_mainline_modem="panel-booyi-otm1287 msm rmi_i2c qcom-spmi-vadc dumb-adc-battery"
Add device: wileyfox-crackling (!485) Initial support for Wileyfox Swift - System boots - USB networking works - Display and touch works - Weston, XFCE4, Plasma Mobile works with software rendering - fb.modes added but charging-sdl still don't work - System allways reports charge level at zero [ci:skip-build]: already built successfully in CI
2019-07-08 18:20:20 +00:00
deviceinfo_arch="aarch64"
# Device related
deviceinfo_keyboard="false"
deviceinfo_external_storage="true"
deviceinfo_screen_width="720"
deviceinfo_screen_height="1280"
wileyfox-crackling: add mainline kernel (!582) [ci:skip-build]: already built successfully in CI
2019-07-12 19:42:56 +00:00
deviceinfo_dev_touchscreen="/dev/input/event3"
Add device: wileyfox-crackling (!485) Initial support for Wileyfox Swift - System boots - USB networking works - Display and touch works - Weston, XFCE4, Plasma Mobile works with software rendering - fb.modes added but charging-sdl still don't work - System allways reports charge level at zero [ci:skip-build]: already built successfully in CI
2019-07-08 18:20:20 +00:00
# Bootloader related
deviceinfo_flash_method="fastboot"
wileyfox-crackling: add mainline kernel (!582) [ci:skip-build]: already built successfully in CI
2019-07-12 19:42:56 +00:00
deviceinfo_kernel_cmdline_mainline="earlycon=msm_serial_dm,0x78b0000 console=ttyMSM0,115200,n8 PMOS_NO_OUTPUT_REDIRECT"
wileyfox-crackling: add option to enable modem (!907)
2020-01-18 11:40:15 +00:00
deviceinfo_kernel_cmdline_mainline_modem="earlycon=msm_serial_dm,0x78b0000 console=ttyMSM0,115200,n8 PMOS_NO_OUTPUT_REDIRECT"
wileyfox-crackling: add mainline kernel (!582) [ci:skip-build]: already built successfully in CI
2019-07-12 19:42:56 +00:00
deviceinfo_kernel_cmdline_downstream="console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 loop.max_part=7 buildvariant=userdebug"
Add device: wileyfox-crackling (!485) Initial support for Wileyfox Swift - System boots - USB networking works - Display and touch works - Weston, XFCE4, Plasma Mobile works with software rendering - fb.modes added but charging-sdl still don't work - System allways reports charge level at zero [ci:skip-build]: already built successfully in CI
2019-07-08 18:20:20 +00:00
deviceinfo_generate_bootimg="true"
wileyfox-crackling: use appended DTB instead of QCDT (!907) The Wileyfox Swift is the only mainline MSM8916 device using QCDT at the moment. The other devices do not have unique qcom,board-ids that could be used within QCDT. So far this has worked fine for the Wileyfox Swift. However, in preparation to *optionally* load the modem we now need two separate pairs of DTBs (one with modem and one without modem). This is simple to implement using appended DTBs, but not possible with QCDT. So let's stop using QCDT entirely for mainline, and use appended DTBs for wileyfox-crackling.
2020-01-15 20:20:16 +00:00
deviceinfo_bootimg_qcdt_downstream="true"
Add device: wileyfox-crackling (!485) Initial support for Wileyfox Swift - System boots - USB networking works - Display and touch works - Weston, XFCE4, Plasma Mobile works with software rendering - fb.modes added but charging-sdl still don't work - System allways reports charge level at zero [ci:skip-build]: already built successfully in CI
2019-07-08 18:20:20 +00:00
deviceinfo_flash_offset_base="0x80000000"
wileyfox-crackling: add mainline kernel (!582) [ci:skip-build]: already built successfully in CI
2019-07-12 19:42:56 +00:00
deviceinfo_flash_offset_kernel="0x00080000"
deviceinfo_flash_offset_ramdisk="0x02000000"
Add device: wileyfox-crackling (!485) Initial support for Wileyfox Swift - System boots - USB networking works - Display and touch works - Weston, XFCE4, Plasma Mobile works with software rendering - fb.modes added but charging-sdl still don't work - System allways reports charge level at zero [ci:skip-build]: already built successfully in CI
2019-07-08 18:20:20 +00:00
deviceinfo_flash_offset_second="0x00f00000"
wileyfox-crackling: add mainline kernel (!582) [ci:skip-build]: already built successfully in CI
2019-07-12 19:42:56 +00:00
deviceinfo_flash_offset_tags="0x01e00000"
Add device: wileyfox-crackling (!485) Initial support for Wileyfox Swift - System boots - USB networking works - Display and touch works - Weston, XFCE4, Plasma Mobile works with software rendering - fb.modes added but charging-sdl still don't work - System allways reports charge level at zero [ci:skip-build]: already built successfully in CI
2019-07-08 18:20:20 +00:00
deviceinfo_flash_pagesize="2048"
wileyfox-crackling: add mainline kernel (!582) [ci:skip-build]: already built successfully in CI
2019-07-12 19:42:56 +00:00
deviceinfo_flash_sparse="true"
Reference in a new issue Copy permalink