On my device the rpmsg0 have DATA5_CNTL under name attribute instead of
rpmsg_name
```
looking at device '/devices/platform/smd/smd:modem/smd:modem.rpmsg_chrdev.0.0/rpmsg/rpmsg_ctrl1/rpmsg0':
KERNEL=="rpmsg0"
SUBSYSTEM=="rpmsg"
DRIVER==""
ATTR{dst}=="0"
ATTR{src}=="0"
ATTR{name}=="DATA5_CNTL"
```
So check for name instead of rpmsg_name.
test scripts are useful to enable/disable modem and also do ofono
related tasks, They are installed on /usr/lib/ofono/test directory and
provide much better user experience then the raw dbus-send command.
- Instead of just libqrtr, build all targets of qrtr
- install the qrtr.initd which starts qrtr services before rmtfs is
started
- in post-install enable qrtr service at boot
- depend on the firmware-lg-hammerhead-modem and
firmware-lg-hammerhead-adsp
- depend on the modem-qcom-msm-mainline-common
Currently adsp firmware is not used actually given upstream kernel
doesn't have support for adsp/sound subsystem. But it will be used
eventually.
This was done for testing locally and is not needed for any
functionality, it managed to slip into the initial qcom kernel package,
but it is not needed.
Upstream suggests to keep remoteproc drivers as modules given they
require the firmware files to be present when they are probed, instead
of putting required firmware files in initramfs due to size
restrictions. We make these drivers modules and load them from
userspace.
Changes:
* device-samsung-klte with both downstream and mainline kernel
subpackages
* linux-postmarketos-qcom updated to last commit
What works in mainline kernel:
* internal SD card
* volume and home key buttons
* usb network
Due to changes in abuild, our `gcc-armhf` etc. packages did not build
when using strict mode (i.e. `pmbootstrap build --strict gcc-armhf`)
anymore.
Changes:
* Set `CBUILDDIR=/`, so apk can read a valid package index from there
* Directly set `_cross_configure`, so it does not use CBUILDDIR anymore
* Set `BOOTSTRAP="nobuildbase"` to prevent apk from installing
`build-base-armhf` etc. (these don't exist in pmOS)
* Remove legacy code for lazy reproducible builds that wrapped
`package()`
matchbox-panel has a keyboard applet, but it was unresponsive.
This was because it sends an event to a running keyboard in daemon
mode. The solution is to start matchbox-keyboard with --daemon in
matchbox-session.
Matchbox-keyboard was not being built as a GTK+2 input method as
thought. This commit correctly enables this functionality and
matchbox-keyboard can now be used as a GTK+2 input method correctly.
* Added gtk+2.0 to depends and gtk+2.0-dev to makedepends.
* Changed --enable-gtk2-im to --enable-gtk-im in ./configure
Add modem-qcom-msm-downstream-common package that pulls in the
dependencies.
qcom_rmtfs now has udev rules to find the storage partitions. My hope
is they can be written flexibly enough to cover all devices and kernel
flavors.
This makes weston build again on x86_64. (It still won't build for
armhf and aarch64, because Alpine's mesa binary package is currently
stuck there, I'll look into that as well.) Detailed fixes:
1. New makedepends needed, because mesa-libwayland-egl does not exist
anymore (see Alpine's aports commits 257a236 and 4f8b36b):
wayland-libs-egl wayland-dev
This fixes configure errors:
checking for EGL_TESTS... no
configure: error: Package requirements (egl glesv2 wayland-client wayland-egl) were not met:
Package 'wayland-client', required by 'virtual:world', not found
Package 'wayland-egl', required by 'virtual:world', not found
2. Disable RDP backend, because Weston source is incompatible with
freerdp 2.0.0. This avoids compilation errors like this one:
libweston/compositor-rdp.c:193:5: error: 'SURFACE_BITS_COMMAND {aka struct _SURFACE_BITS_COMMAND}' has no member named 'bpp';
* linux-postmarketos-qcom: Remove composite USB gadget
* linux-postmarketos-qcom: Fix usb networking
- Enable functionfs so we're able to actually configure the USB
networking
- Enable the USB serial console for convenience, although not enabled by
default pre-composed configuration
Guide for connecting to wlan is on the wiki page for the device, wifi
chip is BCM4334. Wlan interfaces are wlan0 and p2p0. Connection seems
stable, was able to install some packages.
That didn't help either, although it did work on a test run on the
same PC that builds the real binary repository packages. Must be
a race condition, see #1458.
