pmbootstrap#60: Use the system and userdata partition on Android with LVM.After restarting the device to find that wifi Just Worked™, it was possible to successfully scan for wireless networks and establish a connection to secured wireless APs. At this point, running /etc/init.d/networking restart, gave an error about being unable to get a MAC address. (legacy)It is possible to manually get wifi working by manually copying fw_bcmdhd.bin and nvram.txt to their kernel-specified locations and configuring /etc/network/interfaces.To connect follow the instructions on this page.
"Desktop" Linux firmware are outdated.There's a proper firmware subpackage now, wifi device should work out-of-the box.(legacy) weston with fbdev-backend.so uses pixman-type=3 (PIXMAN_TYPE_ABGR), which now does not require configuration.This uses the same initfs hook as many other devices. (legacy) /sys/class/graphics/fb0/mode is empty on boot, it must have U:800x1280p-0.In menuconfig this is located under Device Drivers -> Character devices -> Virtual terminal. (legacy) CONFIG_VT had to be enabled for graphics to work.The touchscreen input device is named elan-touchscreen.Ubuntu Nexus 7 Kernel wiki (old, last updated 2012).Old Android kernels: LineageOS kernel sources Unlegacy kernel sources.It does follow official linux-next branch. Grate kernel, where tegra development ongoing.If you need a working bootloader image version 4.23 can be found, or can be 4.18 can be grabbed from the factory images for KitKat
It does not seem to affect the install process of postmarketOS, but is something to take into account.
Would be nice to have this driver work with IIO framework (TODO)ĭriver Dyna-Image A元010. (tilapia only) Disabled, but works (boolean state, on/off). Works, ALSA UCM configs are included into alsa-ucm-conf package There is 3 keys on GPIO: Power, Volume up, Volume down.īattery status and charging works as expected.
Wi-Fi works (best with IWD daemon: apk add iwd rc-update del wpa_supplicant rc-update add iwd and HOWTO), Bluetooth does work as well (tested with BT 4.2 and 5.0 devices). Older downstream kernels was smaller, so no issue there. but when is kernel larger than approx 4MB, initfs must be packed directly inside kernel (not into boot.img as usual), otherwise kernel won't boot. This status apply for tilapia (Bach revision). There is multiple hardware revisions, so this status may not apply to all of them.