This adds a Finnish/Swedish key map for the Nokia n900.
The same keymap is used for Finnish and Swedish.
This makes the keyboard work in the console. To fix the
XkbLayout other changes are needed to pmbootstrap.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
- E1565 is original "grouper" and it's for modern devices similar to
tilapia
- PM269 is earlier produced Nexuses with different PMIC (not very often
seen)
Closes: https://gitlab.com/postmarketOS/pmaports/-/issues/647
This patch adds basic support for the Samsung Galaxy Tab E 9.6" (SM-T560).
Current status: Kernel builds successfully, flashing boot.img works along with ssh.
Update to Linux 5.8 and bring some nice improvements:
* Use geni for touch instead of CPU driven bitbang, this gives
noticeable performance gains in phosh when scrolling.
* Enable bluetooth (using firmware in updated firmware package), was
able to test bluetooth audio with bluetoothctl but phosh UI shows no
Bluetooth adapter.
* Add testing battery node using bq27541, battery always reported being
plugged in and at 100%.
* Fix UFS error spam due to a bug where writeboost is enabled for all
qcom devices - even though it isn't supported.
* Add quirk to wifi device to fix host capability request rather than
the dodgy driver edit that was used before.
* Minimise .config size to improve build times.
* Make schedutil the default governer
* Fix power button
Remove _downstream, _mainline in deviceinfo as there is only the
mainline kernel now. Fixup taken from a comment by Richard Qian in the
initial device port merge request. I've verified that the device package
builds. [ci:skip-build]
Fixes: 949effc0 ("acer-picasso: new device (Acer Iconia Tab A500) (MR 1308)")
Alpine's abuild is soon going to complain if an APKBUILD has more than
one "Maintainer:" listed. Work around it by renaming the additional
maintainers to "Co-Maintainer:". While at it, move the devicepkg reference
link to the top in device-xiaomi-santoni for consistency.
In postmarketOS, we require at least two maintainers for devices in
main, therefore it does not make sense to drop additional maintainers
from the file.
In Alpine, this change was made because pkgs.alpinelinux.org apparently
can't handle more than one maintainer. I looked into it, and it would
require a database change to add it there, so it does not seem worth the
effort. I also thought about extending abuild to add an environment
variable to skip the check, but then the package would not build with
plain abuild without using the env var.
Related: dd4cd9d606
[ci:skip-build] [ci:skip-vercheck]
[ci:skip-build]: build in CI is currently failing with 'BAD signature'
errors; probably caused by outdated Alpine packages in the dl-cdn
mirror, related to the musl-1.2 rebuild in Alpine edge.
samsung-skomer basically uses the same BCM4334 WiFi/BT chip as
samsung-golden, and the WiFi/BT firmware is also the same.
There seems to be a slightly different NVRAM file, so we package
that just to do things properly.
Signed-off-by: Danct12 <danct12@disroot.org>
(cherry picked from commit f509c39642341c7d4fb5d0d215a6cb581b4156d1)
[ci:skip-build] Takes too long. Builds fine locally
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
Remove it, to prevent the following error:
rm: can't remove '.config': No such file or directory
This must have been necessary before, because the prepare script was
different, or abuild did something differently.
Make it possible to find the kernel config with "pmbootstrap kconfig
edit". While at it, also remove redundant -C "$builddir" arguments for
make (since prepare is running in $builddir already).
Package got renamed and "provides" wasn't added, so right now
`apk upgrade -a` with firmware-rtl8723bt installed results in
`ERROR: firmware-pine64-rtl8723bt-0_git20181104-r0: trying to overwrite lib/firmware/rtl_bt/rtl8723bs_config-pine64.bin owned by firmware-rtl8723bt-0_git20181104-r0.`
Add `replaces="firmware-rtl8723bt"` so `apk` prefers this package.
[ci:skip-build]: already built successfully in CI
Right now we have all firmware packages under firmware/*.
This is problematic for mainly two reasons:
- It's not immediately clear which firmware packages we need to keep
when forking a new stable branch. (Where we delete testing devices
at the moment...) We might end up deleting firmware packages that
are actually used by one of the devices in community.
- When backporting devices to the stable we cannot just cherry-pick
the commit that moved the device to community (since it does not
contain the firmware package). Instead we need to cherry-pick
earlier commits as well, which may touch a lot of deleted files
in the testing directory.
Let's make this consistent by also placing the firmware packages in
the device/* directory. We already have the common firmware- prefix
to distinguish them from device/kernel packages, which are already
both under the device/* directory.
For most firmware packages we use a vendor- prefix to make it clear
who has provided the firmware. The firmware-rtl8723bt package is only
used for Pine64 devices and actually contains configs that are specific
to Pine64 hardware (e.g. rtl8723bs_config-pine64.bin).
Let's rename it to firmware-pine64-rtl8723bt to make this more clear.
Also cleanup the APKBUILD a bit and provide the LICENSE file in a -doc
subpackage so we can legally redistribute that firmware.
This is the downstream u-boot port for the Galaxy S2.
The load script has been slightly altered to load the kernel from the
KERNEL partition at the 512 KiB offset, instead of loading it from the
RECOVERY partition, since PostmarketOS places the second initramfs in
the RECOVERY partition.
Signed-off-by: Paul Cercueil <paul@crapouillou.net>
Newer Qualcomm SoCs (e.g. SDM845. MSM8953) seem to use a different
method to talk to the modem. There are no longer separate rpmsg/SMD
channels for QMI messags, instead the modem is also available through QRTR.
On these newer SoCs, installing msm-modem-mainline is pointless,
because the created /dev/modem device will not actually allow
communicating with the modem. However, you still need the part from
the base package (msm-modem), which installs+enables rmtfs.
To avoid confusion, rename the msm-modem-mainline subpackage to
msm-modem-rpmsg. Install only "msm-modem" on SDM845 because that
likely does not allow communication with the modem through RPMSG
anyway.
This upgrades the librem5-base config used to v21:
- better headphone support/detection
- enable runtime PM for usb/SD interface
This also removes the modemmanager subpackage, the udev rule that was
installed by that package is now in modemmanager in Alpine.
This upgrade includes:
1) enabling fb in deviceinfo: This was previously disabled for
debugging purposes, but can be re-enabled now so we get the
awesome postmarketOS splash screen!
2) fixing GPS, kinda: the device has changed, so this fixes the gpsd
config to use the correct device, and includes a udev rule to
make sure the device is owned by a group that gpsd can use
3) usbnet working with configfs
4) disables getty on /dev/ttyGS0, this was usb serial but isn't
configured now that this uses configfs
5) uses Mesa from Alpine, instead of mesa-git in pmaports. Upstream
Mesa has support for the vivante gpu, and no longer need to rely
on mesa master branch for support.
6) fix pulseaudio detection of profiles
7) update the librem5-base version used, includes a udev rule to
configure DDR freq governor as 'powersave' (reduces power, and
how much heat this thing puts out)
fixes#524fixes#526
In the Linux kernel, the ST-Ericsson NovaThor U8500 SoC is barely
ever mentioned under the "NovaThor" name, more common are names like
U8500, Ux500, ST-Ericsson, STE, ...
Let's rename the kernel package to linux-postmarketos-stericsson
to make that more clear. Also cleanup the APKBUILD a bit while we're
at it, HOSTCC is unneeded, remove unnecessary depends, ...
bq-paella allows running unsigned firmware from other devices.
We can use that advantage to replace some of the original firmware
with newer versions from other devices. The DB410c has updated WCNSS
firmware that reportedly improves WiFi/BT coexistence (i.e. behavior
when both WiFi/BT are active at the same time).
Depend on the virtual "firmware-qcom-msm8916-wcnss" package to give
the user the choice which firmware version they would like to run.
The newer version from "firmware-qcom-db410c-wcnss" is installed by
default (since it has a higher "provider_priority"), but the user
can choose to replace it by running "apk add firmware-bq-picmt-wcnss".
Following discussions in
https://gitlab.com/postmarketOS/pmaports/-/issues/398, swclock has been
removed from postmarketos-base to avoid setting time incorrectly on
devices with a hardware clock. The various raspberry pi don't have
an hardware clock. This activate swclock back.
This adds a hwdb override for the trackpad that fixes the reported size, this fixes
the acceleration profile and palm detection in libinput.
Pulse now follows alsa paths for ucm files so the path for the rk3399 ucm has been
updated to match.
The DB410c is a SBC with APQ8016 SoC. It runs on mainline without
any patches. This port makes use of the existing linux-postmarketos-qcom-msm8916
kernel package that is used for other mainline MSM8916 devices.
Tested functionality:
- USB Network, USB Host (e.g. an USB keyboard)
- Flashing (Fastboot)
- Display (HDMI)
- WiFi/BT
- GPU
- Audio (HDMI)
- FDE
Not tested:
- GPS
Note: The firmware package is called firmware-qcom-db410c (instead of arrow)
because the firmware is provided directly by Qualcomm, not Arrow.
Newer versions of alsa-lib now require a top-level ALSA UCM
configuration (/usr/share/alsa/ucm2/ucm.conf):
ALSA lib parser.c:2159:(load_toplevel_config) Unable to find the top-level configuration file '/usr/share/alsa/ucm2/ucm.conf'.
ALSA lib main.c:983:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2
alsaucm: error failed to open sound card hw:0: No such file or directory
The upstream ALSA UCM configurations are provided by Alpine's
"alsa-ucm-conf" package, so make sure to install it additionally.
What works:
- Booting
- Display
- Touch
- USB Ethernet
What doesn't:
- Sound
- Wi-Fi
- Modem
- Camera
(NOTE: If the display doesn't work, try flashing your phone back to stock, then trying again.)
bq-paella has an external speaker amplifier connected to the right
channel of the headphones output. Add an extra UCM configuration
to handle this properly.
Just got done with my second port of postmarketOS, here's the device:
Amazon Fire 7 (2019) postmarketOS
Mediatek MT8163
600x1024 display
1GB RAM
Linux 4.9.77 (downstream kernel)
Untested:
- Wi-Fi
- Audio
Pretty much everything else
Works:
- Boots
- Touchscreen
- Battery percentage seems to show in Xfce
I cannot test on most of them (at the moment), but I was involved
in porting all of them so I could "guess" certain changes at least.
[ci:skip-vercheck]: just moved and some maintainers
a5lte and a5ulte are almost identical hardware-wise, the separate
package is mainly necessary because they use different firmware
signatures.
Alexey Min agreed to do some testing occasionally :)
