These changes enable the flashlight LED driver (fled_rt5033), and add
support for switching the light on and off from userspace.
In more detail:
* CONFIG_FLED_RT5033 enables the flashlight driver
* CONFIG_VIDEO_EXYNOS_FIMC_IS is required for the flashlight driver to
compile (there seems to be a lot of cross-dependency between the two
drivers)
* patch 0001 fixes the use of usleep (which no longer exists), to make
the kernel compile with those settings
With these changes, /sys/class/flashlight/rt-flash-led shows up in
sysfs, but it's only possible to control the brightness of the LED,
not to switch it on.
Patch 0002 is what actually makes the flashlight usable: it makes
the /sys/class/flashlight/rt-flash-led/mode file writable.
Writing "Torch" there enables the flashlight, writing "Off" disables
it again. "Mixed" mode works like "Torch" as well. I have not figured
out yet how to trigger the camera flash, so setting the mode to
"Flash" is possible, albeit pointless.
For testing changes for device categorization, it is useful to have
a device in each of the categories. The PinePhone is close to being
moved to main/, but it doesn't fulfill all requirements yet.
The QEMU "device ports" are very simple since QEMU currently only
emulates a rather limited set of hardware features. All available features
are working correctly (especially after the recent rework of the QEMU
packages). I suppose it is also usable as a "daily driver", at least for
its intended purpose (a virtual machine for testing postmarketOS changes). :)
Given that everyone can run QEMU, everyone could potentially maintain
it. For now I have added myself as maintainer since I did most of the
recent cleanup. Add drebrez as second maintainer.
Overall it seems useful to have qemu-* in main/, especially because
it is now the device that is selected by default in pmbootstrap.
linux-samsung-kminilte: adjust paths where the bcmdhd driver expects firmware
device-samsung-kminilte: add "nonfree-firmware" subpackage
firmware-samsung-kminilte: new package
firmware post-install actions:
- enable "deferred-initcalls" in sysinit for wlan0 to be available
- force wpa_supplicant to use wlan0 instead of p2p0
(both based on script from device-samsung-klte package)
[ci:skip-build]: already built successfully in CI
- disable CONFIG_CRYPTO_SHA256_ARM, since it causes the build to fail with:
arch/arm/crypto/sha256-core.S:1831: Error: thumb conditional instruction should be in IT block
This updates google-crosshatch's downstream kernel to Lineage 17.1's
version (4.9.200, shared with Lineage's Pixel 3a port).
The newer kernel is needed because this device's kernel requires a
matching dtbo partition. The previous kernel would fail to boot with an
Android 10 dtbo partition.
Two patches were removed: Android 10's bootloader no longer passes the dm
or skip_initramfs boot arguments because of the new dynamic partitions
(https://source.android.com/devices/tech/ota/dynamic_partitions/ab_legacy).
Changes from the LineageOS kernel config:
https://gist.github.com/zhuowei/89b4135ff27e88f5a3dd3e4bf3cd31ab
Tested by booting to USB networking and debug-shell: I have not tested
flashing full pmOS using this kernel yet.
For some reason, on this kernel, when pmOS can't find system partitions
during the "Trying to mount subpartitions for 10 seconds..." stage, it
waits for 70 seconds instead of 10 seconds. I'm not sure why. It does go
to debug-shell correctly after a minute.
[ci:skip-build]: already built successfully in CI
[skip-ci]: just downloading all kernel sources takes about one hour
and ollieparanoid wants to merge it now. This already ran
successfully with [ci:skip-build] and [ci:skip-vercheck].
mesa-demos is currently broken in Alpine since it needs a rebuild.
However, a device port shouldn't force installation of something like
mesa-demos so we should remove it anyway.
* make modules_initfs same as lg-hammerhead
(fixes postmarketOS splash logos at boot)
* split out downstream-firmware and mainline-firmware
* add firmware-adreno to firmware-mainline subpkg
* prepare deviceinfo file to mainline kernel
These files are just a copy paste of the regular OnePlus 5 ones with
adjusted codename, display name and screen height.
The used kernel is linux-oneplus-msm8998 (shared with cheeseburger).
This is in preparation for adding in support for the OnePlus 5T
(dumpling) on top of the regular OnePlus 5 (cheeseburger).
Both devices use the same kernel so the name change just makes sense.
Might as well update the downstream kernel when someone (nathanchance)
is merging in updates as they come out for the linux-stable 4.4.y series
¯\_(ツ)_/¯
This fixes a bug where the package does not install some files as
expected.
For the librem5 package, this also generates the modemmanager
subpackage, which was missed in testing/review earlier.
This upgrades the package to include:
- Support for usb serial console (only in OS, not in u-boot)
- udev rule to fix phone calls with modemmanager using the
broadmobi modem in the phone
- The beginnings of usb network support (still not functional
yet)
- Enable framebuffer in the deviceinfo, pmos logo on boot!
The udev rule and module configs were gathered from upstream Purism
PureOS.
This adds new subpackages for phosh, plasma, and a new dependency on the
phone device package for wys (in Alpine Linux)
This adds subpackages for pulseaudio, phosh, and plasma mobile, and
includes some configuration files from upstream Purism for udev and
pulseaudio that help with audio a bit (though phone audio routing is
still weird/broken for now..)
The separate subpackages for phosh and plasma are necessary becuase they
each use a different modem handling daemon (modem manager and ofono,
respectively).
Add a vibration feedback, along with the LED feedback when booting.
This is suggested by TL Lim.
When trying to power up the phone with holding it in the hand, vibration
feedback is more obvious than LED.
Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
Started porting pmOS to Xiaomi Redmi Note 5 Pro (whyred).
What works so far:
- Booting
- SSH over USB
- SD card detection (haven't tried flashing to internal storage because
i'm afraid of bricking the device due to anti-rollback)
- Vibration and LEDs
- Screen
- Hardware buttons
- Touchscreen
Untested:
- WiFi
- Camera
- Audio
- Bluetooth
- GPS
- Calls, SMS, Cellular network
- Proper WiFi support (building modules, firmware package)
- Architecture change to armv7
- Fix no MAC address on USB networking
[ci:skip-build]: already built successfully in CI
The datasheet says that the AT+QDAI audio routing configuration is saved
to non-volatile memory directly, and therefore needs a modem reset to be
applied.
This commits changes the audio routing configuration script to first
check for the current configuration, and only change it if it is
different from the one wanted.
The new configuration is then sent, and modem is reset to apply
configuration.
The pkgrel bump in !1032 got lost during a rebase, rebuild the package to fix:
ERROR: Could not find dependency 'modem-qcom-msm-mainline-common' in any aports folder or APKINDEX.
The pkgrel bump in !1032 got lost during a rebase, rebuild the package to fix:
ERROR: Could not find dependency 'modem-qcom-msm-mainline-common' in any aports folder or APKINDEX.
The pkgrel bump in !1032 got lost during a rebase, rebuild the package to fix:
ERROR: Could not find dependency 'modem-qcom-msm-mainline-common' in any aports folder or APKINDEX.
Combine modem-qcom-msm-{mainline,downstream}-common to a single APKBUILD
with mainline and downstream subpackages.
Enable rmtfs service here instead of directly in the package.
[ci:skip-vercheck]: for qrtr version fix
This device is probably broken at this point, but since we want to
remove linux-postmarketos-mainline/stable it really has best chances
to work (somewhat) on linux-postmarketos-qcom-msm8974.
rxbnDE