The problem behind swapped red and blue is inverted byte order in
framebuffer driver pixel format.
This patch sets the correct byte order in the framebuffer driver,
solving the swapped red and blue problem.
[ci:skip-build]: already built successfully in CI
Initial starting point to get the device booting. The downstream kernel
repository can be improved, see discussion in the merge request.
[ci:skip-build]: already built successfully in CI
device-xiaomi-santoni: use mdss-fb-init-hack to refresh the display, and
swapfile to fix "out of memory" when loading proprietary blobs.
I have tested the kernel, USB Networking, Display, USB OTG, Wi-Fi (with
proprietary blobs) works fine, through I haven't figured out how to get
Bluetooth and among of other stuff to work. Audio works. For more
information on how to get Wi-Fi and Audio to work, check out the wiki
page for this device, I have updated it.
[ci:skip-build]: already built successfully in CI
The problem behind swapped red and blue is inverted byte order in
framebuffer driver pixel format.
This patch sets the correct byte order in the framebuffer driver.
The previous workaround patch is removed because it fixes improperly
the red-screen issue, causing the swapped red and blue problem
that this commit solves
[ci:skip-build]: already built successfully in CI
- Initial memory frequency scaling driver
- Enable eMMC 1.8v DDR signaling mode
- Limit CPU frequency to avoid overheating
- Fix crash in xf86-video-opentegra driver
[ci:skip-build]: already built successfully in CI
Also hardcode st instead of i3-sensible-terminal, because the font
parameter may not work with all terminals, and we want to use st on the
n900 anyway.
Rename the firmware so it's clear that it's specific to the platform and
not only the amami device. Sony rhine platform includes as follows:
Xperia Z1 (honami)
Xperia Z1 Compact (amami)
Xperia Z Ultra (togari)
This changes the librem5dev package to depend on the new
mesa-purism-gc7000 packages, which provide support for the vivante
gc7000 GPU in this device.
[ci:skip-build]: already built successfully
Makes dhcp work on mainline and downstream kernel.
Disables p2p0 on downstream kernel. This isn't working on either kernel
anyways. It breaks wifi on the downstream kernel.
Thanks to Robert Yang's pmbootstrap patch, we can now avoid flashing
anything to the boot and recovery partition of the Ouya. With this
patch, the latest pmbootstrap will refuse to do so with:
ERROR: 'boot' partition is blacklisted from being flashed! See the Ouya device wiki page for more information.
Applied red screen kernel patch as described in:
https://wiki.postmarketos.org/wiki/Troubleshooting:display
Effectively fixes the red screen on Weston. Added msm-fb-refresher to
APKBUILD to fix display refreshing.
The display now works properly in Weston, but unfortunately the screen
is blue in Plasma Mobile, and X11 crashes in XFCE.
[ci:skip-build]: already built successfully in CI
Updated the device-asus-grouper package to use devicepkg-dev.
I've tested the resulting image and it builds, boots and has a working
touchscreen (in Weston)
I've also noticed that the device reboots itself at times, both in the
USB ssh console and in Weston. This seems to be a known issue but I
don't know how prevalent it was before.
I don't know why build fails on gitlab, I have not changed anything
in kernel. Anyway, I don't remember why I enabled this, so I guess it's safe
to disable this option.
- Bluetooth is now working
- Audio works too (speaker/headphones/earpiece/mic - internal and headset)
- Keyboard layout for X11
- Xorg config for rotated screen
- Suspend issues fixed (tested on MATE)
- OTG bindings updated - not working yet
I didn't get it to work with NetworkManager, but it does work with
connman. Disable Kineto GAN, which caused various commands to misbehave
(just like it did on the htc-ace).
[ci:skip-build]: already built successfully in CI
This is tested to boot on google-crosshatch, following these
instructions:
$ pmbootstrap init, choose the mainline kernel
$ pmbootstrap install --no-fde
$ pmbootstrap initfs hook_add debug-shell
(enter fastboot mode on the device)
$ fastboot set_active a
$ fastboot flash dtbo_a ~/.local/var/pmbootstrap/chroot_rootfs_google-crosshatch/boot/dtbo-google-crosshatch-mainline.img
$ pmbootstrap flasher boot
And you should get telnet after a while. This kernel takes a long time
to build, so [skip ci]. I can confirm it builds locally.
Note that this patch adds the mainline dtb path to deviceinfo. But the
parameter gets ignored on the downstream kernel, so it's fine to keep it
in the shared deviceinfo.
Mainlining this device is work in progress, details at:
https://gitlab.com/postmarketOS/pmaports/issues/153
This makes the linux-postmarketos-stable kernel generate an armv7 package instead of armhf. The contents
of the package were armv7 already but now it can be correct with the new Alpine support.
