For some reason the ofono rules don't always work for the N900's modem.
This picks out the relevant parts of that rule and seems to successfully
set up the modem device every time now.
* pmb.helpers.run: support running processes in background
* enable QXL driver support in the linux kernel configurations so
that we can also use SPICE to connect to the VM.
QXL is a paravirtual graphics driver with 2D support
The SPICE project aims to provide a complete open source solution for remote
access to virtual machines in a seamless way.
Both DRM_QXL and DRM_BOCHS are enabled as modules.
According to [1], on Linux guests, the qxl and bochs_drm kernel modules
must be loaded in order to gain a decent performance
* qemu: add new option --spice to connect to VM using a SPICE client
If specified, 'pmbootstrap qemu' will look for some SPICE client in the
user's PATH and run qemu using the QXL driver.
Currently supported spice clients are 'spicy' and 'remote-viewer' but
adding support for more clients can be easily done.
qemu with qxl support will run on port 8077/tcp, which doesn't belong to
any well-known service and represents 'PM' in decimal.
References:
[0] https://www.linux-kvm.org/page/SPICE
[1] https://wiki.archlinux.org/index.php/QEMU#qxl
[2] https://wiki.archlinux.org/index.php/QEMU#SPICE
[3] https://github.com/postmarketOS/pmbootstrap/issues/453 (partially fixed)
* firmware-asus-flo: packaged all flo firmware
* device-asus-flo: depend on firmware-asus-flo package
* default android wifi config
* Add wifi and freedreno support
* change to console=ttyMSM0 - as per https://dflund.se/~triad/krad/nexus7-flo/
* Add current kernel config as it is currently working with wifi.
* Increase pkgrel to account for changes in the kernel config.
Quite a few things use dbus (plasma, hildon, ofono, connman,
networkmanager, etc) that I think it makes sense to just have this
started by default in pmOS rather than have every device package
implement this on their own.
In case someone shows up with a use-case, where dbus by default
is not desired, please speak up. Possible solutions are in #628.
* Started with stock kernel config (fairphone-perf_defconfig)
* Enabled DEVTMPFS
* Deactivated MSM_KGSL
* Enabled the serial console
* Enabled USB networking
'install' does not properly handle symlinks, it copies the entire file
instead of a symlink to it. This PR uses `cp -a` to preserve symlinks.
For example, with `install`, the files libc.musl-armhf.so.1 and
ld-musl-armhf.so.1 are the same size, despite the fact that in rootfs
libc.musl-armhf.so.1 is actually a symlink to ld-musl-armhf.so.1.
According to @drebrez research, the initramfs size shrunk from
1 567 930 to 1 168 591.
This adds a custom swap file service, which allows specifying a
recommended swap size in the deviceinfo file via
`deviceinfo_swap_size_recommended`. For the N900 this defaults
to 1024 MB now. As the swap file is created in the root partition,
we have encrypted swap now (unless encryption is disabled with
`--no-fde`).
This is a workaround for #429, until the iteration count can be
specified directly in cryptsetup.
* Add default iter-time option, and option to override
* set SHA1 default hash for luksFormat, add option to override
* [RX51] load omap-sham in initramfs for HW accel. sha1
* Add LG G Watch (dory) support
* Use github.com mirror instead of googlesource.com to have fixed checksum
* Fix kernel compilation and remove unnecessary initfs-hook for framebuffer settings
* Check kernel config
* Allow specifying multiple kernel packages, and also no packages
which defaults to scanning all kernel configs (it is super fast
anyway)
* Add the check to Travis CI
* Adjust existing kernel configs, so they pass the kconfig_check.
(We've had to put in a lot of defaults in the aarch64
linux-postmarketos configs, that's why the diff is a bit unclean.)
* Increase modified kernel pkgrels
* Add msm-fb-refresher package and initfs config
* Bump version for pmos-mkinitfs
* Create msm-fb-refresher openrc service
* kill refresher when initfs is done
- Revert to LineageOS 14.1 kernel
- Enable virtual terminal
- Update touchscreen settings
At the moment, display output works, but only when the following is run:
while [ ! ]; do cat /sys/class/graphics/fb0/modes >
/sys/class/graphics/fb0/mode; done.
Adding INSTALL_MOD_STRIP will cause modules to be stripped after
they are installed (option --strip-debug will be used)
In case someone isn't happy with it, please open a PR that reverts
it for your device, or start a discussion as a new issue.
* weston: upgrade to 3.0.0
* removed no_0hz_refresh_rate patch, as this is upstreamed now
* fix regression in compositor-fbdev
* weston: compile with weston-launch enabled
The following patch is required in order to replace GNU's error()
https://lists.freedesktop.org/archives/wayland-devel/2016-September/031179.html
