forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/device/main/device-qemu-amd64/deviceinfo

28 lines
901 B
Text
Raw Normal View History

Unified linux-postmarketos kernel for qemu and n900 (#228) The creates the linux-postmarketos package which for now supports the n900 (and probably the other maemo devices) and qemu with the vexpress-a9 machine simulation. I've put the generated dtbs in /usr/share/dtb for now and set the dtb field in the deviceinfo for the n900 and my new qemu device. * Introduced linux-postmarketos-omap * Unified kernel progress * Created kernel bootable with qemu * Updated n900 deviceinfo for generic kernel * Changed qemu device to vexpress * Updated APK comments and added linux-postmarketos-dev package * Append dtb in mkinitfs * Fixed bootscript on n900 for the generic kernel * Don't detect double flavors with -dtb appending * Added graphics drivers for vexpress (qemu) * Added more drivers for qemu This adds virtio network support in qemu for the vexpress-a9 machine. The keyboard and mouse don't work yet. You can boot into weston if --no-fde is specified
2017-07-25 20:08:35 +00:00
# Reference: <https://postmarketos.org/deviceinfo>
# Please use double quotes only. You can source this file in shell scripts.
deviceinfo_format_version="0"
QEMU: fix case sensitivity, unify device names (!480) [ci:skip-vercheck]
2019-07-03 21:07:08 +00:00
deviceinfo_name="QEMU amd64"
deviceinfo_manufacturer="QEMU"
Add deviceinfo_codename variable (!114) For postmarketOS/pmaports#157 [skip ci]
2018-12-25 19:25:32 +00:00
deviceinfo_codename="qemu-amd64"
Unified linux-postmarketos kernel for qemu and n900 (#228) The creates the linux-postmarketos package which for now supports the n900 (and probably the other maemo devices) and qemu with the vexpress-a9 machine simulation. I've put the generated dtbs in /usr/share/dtb for now and set the dtb field in the deviceinfo for the n900 and my new qemu device. * Introduced linux-postmarketos-omap * Unified kernel progress * Created kernel bootable with qemu * Updated n900 deviceinfo for generic kernel * Changed qemu device to vexpress * Updated APK comments and added linux-postmarketos-dev package * Append dtb in mkinitfs * Fixed bootscript on n900 for the generic kernel * Don't detect double flavors with -dtb appending * Added graphics drivers for vexpress (qemu) * Added more drivers for qemu This adds virtio network support in qemu for the vexpress-a9 machine. The keyboard and mouse don't work yet. You can boot into weston if --no-fde is specified
2017-07-25 20:08:35 +00:00
deviceinfo_arch="x86_64"
qemu-*: cleanup, use consistent hardware (!1029) pmbootstrap now configures consistent QEMU hardware for all architectures. This means that the device package for amd64/aarch64 is now almost identical, except for the architecture and the name of the serial port. pmbootstrap always uses virtio-gpu now (but not necessarily virgl), so there is only one consistent set of initfs modules we need to configure for both architectures. Also add the xfce4 package from amd64 to aarch64, exactly the same problem with the wallpaper exists there.
2020-03-06 13:01:14 +00:00
# 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="vm"
qemu-*: cleanup, use consistent hardware (!1029) pmbootstrap now configures consistent QEMU hardware for all architectures. This means that the device package for amd64/aarch64 is now almost identical, except for the architecture and the name of the serial port. pmbootstrap always uses virtio-gpu now (but not necessarily virgl), so there is only one consistent set of initfs modules we need to configure for both architectures. Also add the xfce4 package from amd64 to aarch64, exactly the same problem with the wallpaper exists there.
2020-03-06 13:01:14 +00:00
deviceinfo_keyboard="true"
deviceinfo_external_storage="true"
qemu-*: set screen resolution to 1024x768 (!1029) For some reason, the default SDL UI has been using 1024x768 for a while now. This causes the splash screen to look weird because it is too small. Now that pmbootstrap tries to configure 1024x768 in all cases we can change the resolution for the device ports.
2020-03-06 10:51:45 +00:00
deviceinfo_screen_width="1024"
deviceinfo_screen_height="768"
qemu-amd64: configure getty on serial console (MR 1626)
2020-10-07 12:04:50 +00:00
deviceinfo_getty="ttyS0;115200"
qemu-amd64: add deviceinfo_dev_internal_storage (MR 1820) Use to simulate installation from SD to eMMC with: $ pmbootstrap qemu --second-storage
2020-12-14 18:19:48 +00:00
deviceinfo_dev_internal_storage="/dev/vdb"
deviceinfo_dev_internal_storage_repartition="true"
qemu-*: cleanup, use consistent hardware (!1029) pmbootstrap now configures consistent QEMU hardware for all architectures. This means that the device package for amd64/aarch64 is now almost identical, except for the architecture and the name of the serial port. pmbootstrap always uses virtio-gpu now (but not necessarily virgl), so there is only one consistent set of initfs modules we need to configure for both architectures. Also add the xfce4 package from amd64 to aarch64, exactly the same problem with the wallpaper exists there.
2020-03-06 13:01:14 +00:00
# Bootloader related
deviceinfo_flash_method="none"
deviceinfo_kernel_cmdline="console=tty1 console=ttyS0 PMOS_NO_OUTPUT_REDIRECT PMOS_FORCE_PARTITION_RESIZE"
deviceinfo_disable_dhcpd="true"
device-qemu-amd64: Add support for EFI boot (MR 4508) systemd-boot is used for EFI boot (when using "pmbootstrap qemu --efi"), legacy boot (seabios) is still supported as well (pmb/qemu boots the kernel directly). [ci:skip-build] already built successfully in CI
2023-07-10 07:45:18 +00:00
deviceinfo_partition_type="gpt"
deviceinfo_boot_filesystem="fat32"
deviceinfo_generate_systemd_boot="true"
Reference in a new issue Copy permalink