Disable checks for good.
* half of them would not run anyway because they require X11
* falkon-cookietest hangs for more than 30 minutes with 100% CPU usage
while cross compiling for armhf
We already have it limited by the ID_PART_ENTRY_NAME, it is very less
likely that someone will have sdcard with the partition names which are
similar to modem partition.
This fixes rmtfs for @MartijnBraam who for some reason have internal mmc
as mmcblk1 and not 0.
Plasma Mobile uses the telepathy-ofono through telepathy,
telepathy-ofono was developed by canonical for ubuntu touch and it is
also used by dialer-app of ubports.
telepathy-ofono is alternative to telepathy-ring.
This is basically too old stuff from meego times, and is added only
because telepathy-ofono needs it for now, I will talk with ubports
people to get telepathy-ofono ported to libqofono so we can dump this 6
year old unmaintained library.
(patches to make it build with qt5 and modern compiler are taken from
ubuntu packaging)
This patchset is based on the branch on the sysmocom.de git,
https://git.sysmocom.de/ofono/log/?h=lynxis/voicecall
The original branch was based on old ofono so this patches are manually
merged to ofono 1.21 and tested on debian initially.
This makes the flasher work when no flash_method attribute exists on
the args variable, which happens when it is invoked through the
pmbootstrap export --odin command. This is a regression introduced
in b29cc877a7
This fixes#1527
* linux-samsung-p4wifi: Use libressl-dev
* linux-samsung-p4wifi: Update to kernel based on mainline tegra_defconfig
Previously it was based on the config from a mainline-ish kernel for
Android. The remaining Android specific patches have been dropped.
It is now mainline with out-of-tree drivers and corresponding hardware
specific patches/fixes/hacks.
armhf tends to be outdated, just like it is right now. The Alpine
aports have binutils-2.30-r2, and the x86_64 version has that version
as well. But the armhf version is still at -r1, which caused the test
case to fail.
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
Oliver Smith
George Hopkins
yangxuan8282
Bhushan Shah
Martijn Braam
Mayeul Cantan
Daniele Debernardi
Decatf
Klaus
Sicelo
Bart Ribbers
Filip Matijević
george99g
Duncan Guthrie