forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/device/community/device-asus-me176c/deviceinfo

27 lines
978 B
Text
Raw Normal View History

New device: asus-me176cx (Asus MeMo Pad 7) (!123) Use upstream Linux with patches, which are needed for a lot of things. lambdadroid said he will upstream some of them, but the battery driver would need to be written from scratch, which is apparentely non-trivial. [skip ci]: kernel doesn't build under one hour (maybe too many modules are selected), but it does build eventually
2018-12-31 19:44:13 +00:00
# Reference: <https://postmarketos.org/deviceinfo>
# Please use double quotes only. You can source this file in shell scripts.
deviceinfo_format_version="0"
asus-me176c: rework packages (!699) device/device-asus-me176c: - Install me176c-factory to apply correct MAC addresses for WiFi and BT - Use FAT32 for boot partition. This allows flashing the boot partition directly as ESP (EFI System Partition). - Overall cleanup device/linux-asus-me176c: - Update kernel fork to 4.19.80 - Cleanup APKBUILD - Stop building patched ACPI DSDT table directly into kernel firmware/firmware-asus-me176c: - Package WiFi firmware firmware/firmware-asus-me176c-acpi: - New package for the patched ACPI DSDT table -> Separate from firmware-asus-me176c because it is always required, (not optional) [ci:skip-build]: runs into timeout
2019-10-10 17:10:11 +00:00
deviceinfo_name="ASUS MeMO Pad 7 (ME176C(X))"
New device: asus-me176cx (Asus MeMo Pad 7) (!123) Use upstream Linux with patches, which are needed for a lot of things. lambdadroid said he will upstream some of them, but the battery driver would need to be written from scratch, which is apparentely non-trivial. [skip ci]: kernel doesn't build under one hour (maybe too many modules are selected), but it does build eventually
2018-12-31 19:44:13 +00:00
deviceinfo_codename="asus-me176c"
asus-me176c: rework packages (!699) device/device-asus-me176c: - Install me176c-factory to apply correct MAC addresses for WiFi and BT - Use FAT32 for boot partition. This allows flashing the boot partition directly as ESP (EFI System Partition). - Overall cleanup device/linux-asus-me176c: - Update kernel fork to 4.19.80 - Cleanup APKBUILD - Stop building patched ACPI DSDT table directly into kernel firmware/firmware-asus-me176c: - Package WiFi firmware firmware/firmware-asus-me176c-acpi: - New package for the patched ACPI DSDT table -> Separate from firmware-asus-me176c because it is always required, (not optional) [ci:skip-build]: runs into timeout
2019-10-10 17:10:11 +00:00
deviceinfo_manufacturer="ASUS"
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="2014"
community/device-asus-me176c: switch to linux-edge (MR 3167) Linux 5.18 brought better support for some x86-based Android tablets, thanks to work from Hans de Goede. This includes asus-me176c: the modified ACPI table and the Linux fork is no longer necessary, it can just run linux-edge from Alpine. Drop the old Linux 5.4 fork and related packages. Instead of using the proprietary sound firmware from linux-firmware-intel, switch to using the open-source(!) "Sound Open Firmware" (SOF). NOTE: The mainline battery driver seems quite a bit less accurate than the ugly old driver ported from the downstream driver. Also, Bluetooth seems to fail on some boots now. Overall it works quite well though. :)
2022-05-28 11:36:32 +00:00
deviceinfo_modules_initfs="gpio-crystalcove intel_crystal_cove_charger 8250_dw x86-android-tablets mmc_block sdhci_acpi phy-tusb1210 dwc3 dwc3-pci goodix_ts"
New device: asus-me176cx (Asus MeMo Pad 7) (!123) Use upstream Linux with patches, which are needed for a lot of things. lambdadroid said he will upstream some of them, but the battery driver would need to be written from scratch, which is apparentely non-trivial. [skip ci]: kernel doesn't build under one hour (maybe too many modules are selected), but it does build eventually
2018-12-31 19:44:13 +00:00
deviceinfo_arch="x86_64"
# Device related
device/*: set gpu_accelerated for devices that show '3D=Y' on wiki (MR 2078) [ci:ignore-count] [ci:skip-vercheck] needed for the postmarketos-ui-* packages in this series [ci:skip-build] already built ui-* packages in CI, and device pacakges are just trivial deviceinfo change (manually built some just to verify)
2021-07-07 05:06:17 +00:00
deviceinfo_gpu_accelerated="true"
device/*: Add deviceinfo_chassis variable (MR 1246) [ci:ignore-count], [ci:skip-build]
2020-05-17 13:33:49 +00:00
deviceinfo_chassis="tablet"
New device: asus-me176cx (Asus MeMo Pad 7) (!123) Use upstream Linux with patches, which are needed for a lot of things. lambdadroid said he will upstream some of them, but the battery driver would need to be written from scratch, which is apparentely non-trivial. [skip ci]: kernel doesn't build under one hour (maybe too many modules are selected), but it does build eventually
2018-12-31 19:44:13 +00:00
deviceinfo_keyboard="false"
deviceinfo_external_storage="true"
community/asus-me176c: fix splash screen width and phosh scaling (MR 2047) Actually the display in asus-me176c has a width of 800px, which means that the splash screen isn't perfectly centered. Correct this in deviceinfo to make it show up correctly. Also, add configuration file for Phosh to reduce scaling a bit to 1.75. It's kind of subjective but scaling = 2 definitely feels too large. [ci:skip-build]: already built successfully in CI
2021-03-20 16:39:02 +00:00
deviceinfo_screen_width="800"
New device: asus-me176cx (Asus MeMo Pad 7) (!123) Use upstream Linux with patches, which are needed for a lot of things. lambdadroid said he will upstream some of them, but the battery driver would need to be written from scratch, which is apparentely non-trivial. [skip ci]: kernel doesn't build under one hour (maybe too many modules are selected), but it does build eventually
2018-12-31 19:44:13 +00:00
deviceinfo_screen_height="1280"
# Bootloader related
asus-me176c: use fastboot-bootpart flasher (!930) Flash (split) boot partition to the "APD" partition. It's a rather useless partition with media files for demo purposes. Perfect for a small(-ish) boot partition with ~300 MB.
2020-02-04 10:52:30 +00:00
deviceinfo_flash_method="fastboot-bootpart"
# "ASUS Product Demo", contains mostly useless audio/video files for demo purposes...
# With ~300 MB it is perfect as (second) EFI boot partition.
deviceinfo_flash_fastboot_partition_kernel="APD"
asus-me176c: rework packages (!699) device/device-asus-me176c: - Install me176c-factory to apply correct MAC addresses for WiFi and BT - Use FAT32 for boot partition. This allows flashing the boot partition directly as ESP (EFI System Partition). - Overall cleanup device/linux-asus-me176c: - Update kernel fork to 4.19.80 - Cleanup APKBUILD - Stop building patched ACPI DSDT table directly into kernel firmware/firmware-asus-me176c: - Package WiFi firmware firmware/firmware-asus-me176c-acpi: - New package for the patched ACPI DSDT table -> Separate from firmware-asus-me176c because it is always required, (not optional) [ci:skip-build]: runs into timeout
2019-10-10 17:10:11 +00:00
deviceinfo_boot_filesystem="fat32"
Reference in a new issue Copy permalink