Changes

Jump to: navigation, search

Glossary

1,158 bytes added, 14:30, 5 July 2019
m
--no-fde removed (deprecated)
If you found a technical term related to this project, that you had to research to understand, please add it here (alphabetically sorted).
See also:
=== [https://alpinelinux.org/ Alpine Linux] ===
The minimal Linux distribution, that which postmarketOS is based onupon. Actually, pmOS only adds a few packages on top of it, and provides the installer and development environment - that is the plan, to keep following upstream as close closely as possible. Alpine developers do not see their distribution as "GNU/Linux". That being said, it works a lot like a typical Desktop Linux distribution. You have your package manager, the typical shell commands, you can install typical Linux software, and so on.
=== android-msm ===
The Google provided -modified Linux version 3.4 kernel as base for all Qualcomm devices.
=== apk ===
* Android app format
* Alpine Linux package (also ends in <code>.apk</code>, but totally incompatible!), which are actually gzipped tar files
* [https://wiki.alpinelinux.org/wiki/Alpine_Linux_package_management Alpine Linux package manager (apk)]
=== boot.img ===
'''Variations:'''
* Some old SamsungsSamsung devices: <code>boot.img</code> is just a kernel with a baked in <code>initramfs</code> ([[deviceinfo_flash_methods#Isorec_or_bootimg.3F|more]])
* qcdt: <code>boot.img</code> has a <code>dtb</code> appended (instead of appending it to the kernel, [[deviceinfo_bootimg_qcdt|more]])
=== dtb ===
The binary device tree([[dtb]]), this is a file containing a description of the hardware in the device , since phones don't have discoverable busses like x86 platforms. These are created from dts files in the kernel repository and produce a file called <code>zImage-dtb</code> for some Android kernels (older Android kernels do not generate a <code>dtb</code> file at all and have hardcoded the information directly in the kernel source). In mainline kernels, <code>dtb</code> files for all supported boards are created at once.
=== dri ===
[https://en.wikipedia.org/wiki/Direct_Rendering_Infrastructure Direct Rendering Infrastructure], the modern Linux kernel API for drawing to the screen.
=== drm/kms ===
=== Direct Rendering Manager/Kernel Mode Setting is a slightly more complicated API than fbdev (and it replaces all fbdev functionality), it still provides a framebuffer but also has options to integrate hardware acceleration for 2D and 3D. All opensource fbdev drivers should be portable to a drm/kvm ===driver.
This is a slightly more complicated API than fbdev (and it replaces all fbdev functionality), it still provides a framebuffer but also has options to integrate hardware acceleration for 2D and 3D. All opensource fbdev drivers should be portable to a drm driver.=== FDE ===
=== FDE ===Full Disk Encryption, the rootfs created by pmbootstrap is fully encrypted with [https://en.wikipedia.org/wiki/LUKS luks], preventing the phone data from being retrieved without the password if the device is turned off. This can be enabled with <code>--fde</code> .
Full Disk Encryption, by default the rootfs created by pmbootstrap is fully encrypted with luks, preventing the phone data to be retrieved without password if the === fdt ===Flat device tree. This is turned offjust another name for [[Glossary#dtb|dtb]][https://elinux.org/Device_Tree_Reference#FDT_format]. This can optionally be disabled with <code>--no-fdeunpackbootimg</code> generates files ending in <code>.fdt</code> for debugging purposes.
=== fbdev / framebuffer ===
[https://en.wikipedia.org/wiki/Linux_framebuffer Linux framebuffer] a (more or less?) deprecated API from the Linux kernel, that allows drawing to the screen. Newer drivers use the DRI API instead (see above). Android devices usually have drivers for framebuffer, instead of DRI.
=== IDA ===
The proprietary software [https://en.wikipedia.org/wiki/IDA_Pro Interactive Disassembler] is state of the art in the reverse engineering scene. It can be used to reverse engineer all kinds of blobs where the source code is not available, such as closed-source [[firmware]].Disassembling is hard, and there's a high learning curve involved. It also features a decompiler, which produces (non-working) C code for better understanding. === isorec === [https://forum.xda-developers.com/galaxy-s2/orig-development/isorec-isolated-recovery-galaxy-s2-t3291176]
=== lk (little kernel) ===
''[https://github.com/littlekernel/lk <code>lk</code>] is the kernel where which fastboot runs on - at . At least all new-ish qualcomm Qualcomm devices is using use <code>lk</code> and new-ish mediatek devices too''
=== OpenRC ===
=== Weston ===
[https://github.com/wayland-project/weston Weston] is the reference implementation of a [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland ] compositor. It has various backends that lets it run on Linux kernel modesetting and evdev input as well as under X11. We have chosen Weston as a demo because we didn't want to use X11, as this is slowly dying. Also there's libweston, which might come in handy later (you can write your own desktop environment and inherit the hardware compatibility from weston). Weston is nice as a demo and useful at this moment of the development, but not usable as phone interface, so we'll need different desktop environments packaged sooner or later. See [https://github.com/postmarketOS/pmbootstrap/issues/62 issue #62] === pmic === This stands for power management integrated circuit. It is the chip that controls the power to the various components of the phone. === qmi === Qualcomm Modem Interface. The internal interface inside Qualcomm SoCs that connect the modem and the application processor. === slpi === Sensor Low Power Interface. The interface that connect sensors like the accelerometer to the application processor in Qualcomm Socs
We have chosen Weston as demo because we didn't want to use X11, as this is slowly dying. Also there's libweston, which might come in handy later (you can write your own desktop environment and inherit the hardware compatibility from weston). Weston is nice as demo useful at this moment of the development, but not usable as phone interface, so we'll need different desktop environments packaged sooner or later. See [https[Category://github.com/postmarketOS/pmbootstrap/issues/62 issue #62Technical Reference]]
68
edits

Navigation menu