msm8974 kernel patches for v5.5

I have a kernel patch series for msm8974 devices ready at https://github.com/masneyb/linux. They are also available in patch form at https://github.com/masneyb/nexus-5-upstream/tree/master/out-of-tree-patches/upstream-patches/v5.5. These patches adds support for the GPU, modem, and the vibrator found on the Nexus 5 on top of the v5.5 upstream kernel. The cover letter on the patch series links gives a high-level status of the out-of-tree patches.

I'm not sure what all is different in the pmOS msm8974 kernel config vs the upstream arch/arm/configs/qcom_defconfig. I suggest including a patch to qcom_defconfig with only what's intended to be changed.

By Ghost User on 2020-01-27T11:38:11

Thanks!

Do I understand this correctly: now we can update kernel package for msm8974-based SoCs (linux-postmarketos-qcom-msm8974), basing it on torvalds/master (or linux-next/master? or some tag?) as base commit, and apply all those patches on top of it? (Then of course also add all our patches for other devices)

By Alexey Min on 2020-01-27T12:16:28

added category::upgrade label

Please let's try to keep the msm8974 "common" kind-of-mainline package based on https://gitlab.com/postmarketOS/linux-postmarketos so we don't lose a bunch of devices :) We can definitely merge patches there as needed, but I believe most of Brians patches are already merged there - if something is missing please tell me (maybe some hammerhead specific ones like vibrator?).

By Luca Weiss on 2020-01-27T20:52:09

mentioned in issue #238 (closed)

By Ghost User on 2020-01-27T21:06:32

marked this issue as related to #238 (closed)

By Alexey Min on 2020-01-27T21:14:14

@z3ntu so you're against the idea of basing "msm8974 common kernel package" on released linux 5.5 and have all our additions as patches on top of it?

Either way, I think we can at least try to rebase https://gitlab.com/postmarketOS/linux-postmarketos qcom branch on 5.5 now? New linux kernel release sounds like a good occasion for that..

By Alexey Min on 2020-01-27T21:22:04

No I'm not? But in the past we've switched the linux-postmarketos-qcom(-msm8974) package to directly using Brians repo so device support for some devices was lost in that process - I've just meant that we shouldn't do that again. I can look into rebasing the linux-postmarketos repo on 5.5 next week (this week I want to fix pinephone stuff for FOSDEM)

By Luca Weiss on 2020-01-27T21:27:42

@z3ntu: I pushed up a new v5.5 tree that adds Bluetooth support to the Nexus 5. You said that you weren't going to start working on this until next week but I'm just giving you a heads up in case you already pulled from me.

I wish that I could be at FOSDEM this weekend. I'm going to try to come out for that next year.

By Ghost User on 2020-01-29T23:47:18

I've rebased linux-postmarketos on 5.6-ish now with your patches: https://gitlab.com/postmarketOS/linux-postmarketos/-/commits/qcom-msm8974-5.5.y - I hope I didn't miss any :)

By Luca Weiss on 2020-02-14T19:13:05

Just tried qcom-msm8974-5.5.y.

I used envkernel on that branch, and dtbTool post-make.sh like this:

#!/bin/sh
dtbTool -s 2048 -p "${srcdir}/scripts/dtc/" -o \
	"${builddir}/arch/arm/boot/dt.img" \
	"${builddir}/arch/arm/boot/dts" \
	"--version=2"

Then pmbootstrap flasher flash_kernel

With serial cable: minicom.cap

failures at the end:

[    2.865238] mmcblk1rpmb: mmc1:0001 SEM16G partition 3 4.00 MiB, chardev (247:0)
[    2.874655]  mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 p29
[   32.484286] l6: disabling
[   32.484622] l7: disabling
[   32.486136] l13: disabling
[   32.488718] l21: disabling
[   32.491246] l24: disabling
ERROR: failed to mount subpartitions!
NOTE: Waiting 10 seconds for the framebuffer /dev/fb0.
If your device does not have a framebuffer, disable this with:
no_framebuffer=true in <https://postmarketos.org/deviceinfo>
ERROR: /dev/fb0 did not appear!
fbsplash: can't open '/dev/fb0': No such file or directory
Setup usb network
  /sys/class/android_usb does not exist, skipping android_usb
  Setting up an USB gadget through configfs
[   58.839712] using random self ethernet address
[   58.840075] using random host ethernet address
  No USB Device Controller available
Starting udhcpd
  Could not find an interface to run a dhcp server on
  Interfaces:
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether d2:f5:cd:6c:b8:8d brd ff:ff:ff:ff:ff:ff
ERROR: boot partition not found!
fbsplash: can't open '/dev/fb0': No such file or directory

By Craig Comstock on 2020-03-09T14:00:29

Closing, patches are integrated and upgrade to 5.6 is pending in !1090 (merged)

By Luca Weiss on 2020-03-29T12:47:37

closed

By Luca Weiss on 2020-03-29T12:47:37