postmarketOS

deviceinfo reference

Most of the variables in deviceinfo have self-explanatory names and are used both when you are building postmarketOS and during runtime (it is available at /etc/deviceinfo).

All variables start with deviceinfo_ in the file - this is omitted here to save space.

device

Variable	Description	Possibles values
`format_version`	Used to distinguish between different versions of this file. It is usually "0"
`name`	Device model (e.g. "Google Nexus 5")
`manufacturer`	Device manufacturer (e.g. "LG")
`date`	Release date of the device
`keyboard`	The device has a hardware keyboard.	`true`, `false`
`nonfree`	Components of the device, that only run with closed source firmware. We have to do more research on this topic and specify a list of possible values, for now all devices have `????` here.	`????`
`dtb`	Name of the device tree blob file. This will be necessary for the mainline kernel.
`modules_initfs`	Kernel modules to include in the initramfs image. Note: modules to be loaded after the initramfs can be specified like in a `modules-load.conf` (example).
`external_disk`	Does the device have an sdcard or other external storage medium?	`true`, `false`
`external_disk_install`	Allow installing to sdcard	`true`, `false`
`flash_methods`	Method used to flash the device ([[more info	deviceinfo_flash_methods]])
`arch`	Device architecture, must be supported by Alpine Linux	`armhf`, `aarch64`

flash

These are used for flashing and booting the device, and most of them are fastboot specific. Here is a guide on how to get these values for a specific Android device (by extracting the boot.img)

Variable	Description	Possible values
`flash_offset_kernel`	Kernel offset used for flashing
`flash_offset_ramdisk`	Ramdisk offset used for flashing
`flash_offset_second`	Used for flashing
`flash_offset_tags`	Used for flashing
`flash_offset_base`	Used for flashing	Default: `0x10000000`
`flash_pagesize`	Page size	Usually "2048"
`flash_sparse`	Set this to true if your device expects a sparse system image flashed
`kernel_cmdline`	Kernel command line
`generate_bootimg`	Set this to true for fastboot device, so the `mkinitfs` command will generate a `boot.img` file after creating the `initfs`. Add `mkbootimg` as dependency to your device's APKBUILD!	`true, false`
`generate_legacy_uboot_initfs`	For the N900, we use a legacy version of the uboot bootloader right now. When setting this variable to true, the initramfs will generate an uboot legacy compatible initramfs file. Modern versions of uboot can load regular initramfs files.	`true, false`
## weston

Variable	Description	Possibles values
`weston_pixman_type`	(optional) Use it as a workaround for issue #54.	mostly `"2"` for ARGB, all values
`weston_core_modules`	Module(s) to load on device when using Weston	See the weston.ini manpage for a list of valid modules
`weston_core_backend`	Weston backend to use	See the weston.ini manpage for a list of valid backends. Note that not all of these may be compiled into Weston for Alpine Linux. If not set, this defaults to 'fbdev-backend.so'
`weston_keymap_rules`	Keyboard keymap rule to use.	Valid rules are listed in `/usr/share/X11/xkb/rules/`.
`weston_keymap_model`	Keyboard keymap model to use.	Valid models are listed in `/usr/share/X11/xkb/rules/symbols`, typically buried in a particular symbol file. For example, the model for the Nokia N900 is found in the file `/usr/share/X11/xkb/symbols/nokia_vndr/rx-51`, with a line that specifies `-model nokiarx51`. To set the keymap model for the N900, you would set `weston_keymap_model=nokiarx51` in the appropriate `deviceinfo` file

splash

Variable	Description	Possibles values
`screen_width`	The width of the display	800, 720, 1440... anything really
`screen_height`	The height of the display	1280, 2560... other