From 0c1370b5f1b3e8abc934ea913a4377f05f32e4a9 Mon Sep 17 00:00:00 2001 From: Yuval Adam <_@yuv.al> Date: Mon, 7 Aug 2017 22:05:24 +0300 Subject: Initial static build --- docs/wiki/deviceinfo-reference/index.html | 243 ++++++++++++++++++++++++++++++ 1 file changed, 243 insertions(+) create mode 100644 docs/wiki/deviceinfo-reference/index.html (limited to 'docs/wiki/deviceinfo-reference/index.html') diff --git a/docs/wiki/deviceinfo-reference/index.html b/docs/wiki/deviceinfo-reference/index.html new file mode 100644 index 0000000..6953072 --- /dev/null +++ b/docs/wiki/deviceinfo-reference/index.html @@ -0,0 +1,243 @@ + + + + + + postmarketOS + + + + + + + + + + + + + + + +
+
+ +

+ + 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

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
VariableDescriptionPossibles values
format_versionUsed to distinguish between different versions of this file. It is usually "0"
nameDevice model (e.g. "Google Nexus 5")
manufacturerDevice manufacturer (e.g. "LG")
dateRelease date of the device
keyboardThe device has a hardware keyboard.true, false
nonfreeComponents 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.????
dtbName of the device tree blob file. This will be necessary for the mainline kernel.
modules_initfsKernel 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_diskDoes the device have an sdcard or other external storage medium?true, false
external_disk_installAllow installing to sdcardtrue, false
flash_methodsMethod used to flash the device ([[more infodeviceinfo_flash_methods]])
archDevice architecture, must be supported by Alpine Linuxarmhf, 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)

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
VariableDescriptionPossible values
flash_offset_kernelKernel offset used for flashing
flash_offset_ramdiskRamdisk offset used for flashing
flash_offset_secondUsed for flashing
flash_offset_tagsUsed for flashing
flash_offset_baseUsed for flashingDefault: 0x10000000
flash_pagesizePage sizeUsually "2048"
flash_sparseSet this to true if your device expects a sparse system image flashed
kernel_cmdlineKernel command line
generate_bootimgSet 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_initfsFor 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
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
VariableDescriptionPossibles values
weston_pixman_type(optional) Use it as a workaround for issue #54.mostly "2" for ARGB, all values
weston_core_modulesModule(s) to load on device when using WestonSee the weston.ini manpage for a list of valid modules
weston_core_backendWeston backend to useSee 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_rulesKeyboard keymap rule to use.Valid rules are listed in /usr/share/X11/xkb/rules/.
weston_keymap_modelKeyboard 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

+ + + + + + + + + + + + + + + + + + + + +
VariableDescriptionPossibles values
screen_widthThe width of the display800, 720, 1440... anything really
screen_heightThe height of the display1280, 2560... other
+ +
+
+ + \ No newline at end of file -- cgit v1.3.1