<ValPackett[m]>
will look into getting the msm89x7 kernel running next, anything i should know? qcom stuff looks a bit intimidating compared to mtk lol but i think i can do it
ungeskriptet has joined #msm8937-mainline
<Danct12[m]>
looks like 2025 will be the year of msm89x7
<Danct12[m]>
good luck everyone :)
<Danct12[m]>
<ValPackett[m]> "will look into getting the..." <- should be similar to msm8916
<NekoCWD[m]>
Is there really 2 cs for blsp2_spi2 ? On my downsteam has only one
<NekoCWD[m]>
s/On/My/, s/my//
<FieryFlames[m]>
<ValPackett[m]> "will look into getting the..." <- Qcom intimidating compared to mtk? Blasphemy
<barni2000[m]>
<ValPackett[m]> "will look into getting the..." <- E5 plus is in the repo
<barni2000[m]>
maybe there are similar parts
ungeskriptet_ has joined #msm8937-mainline
ungeskriptet has quit [Ping timeout: 480 seconds]
ungeskriptet_ is now known as ungeskriptet
f_ is now known as funderscore
<ValPackett[m]>
hm. so funnily enough the panels in downstream in nora-common just come from an include of jeter-common. how do we represent this sharing here?
<barni2000[m]>
you can use the same compatible and make a 1 config for panel generations check ugg/ugglite config
<ValPackett[m]>
oh yeah ugg references ugglite panels while the outer thingy is only ugg-panel
<barni2000[m]>
lk2nd is selecting the panels
<barni2000[m]>
ugg-panel is for lk2nd
<ValPackett[m]>
yeahyeah for substituting the detected one's compatible into the mainline dt right? so the mainline dt has 'ugg-panel'
<barni2000[m]>
lk2nd will append a fallback compatible and yes ugg-panel is for mainline dt. It will look like something like this after lk2nd modifying the dt. comaptible = "panel-ugg", "xiaomi,ugg-...";
<barni2000[m]>
* lk2nd will append a fallback compatible and yes ugg-panel is for mainline dt. It will look like something like this after lk2nd modifying the dt. comaptible = "panel-ugg", "xiaomi,ugglite-...";
<ValPackett[m]>
some models like montana already have controller IC names used instead of the Motorola Number™ like `mot_inx_521` -> `montana-nt35596-inx`, was that figured out just by comparing the dsi setup sequence?
<barni2000[m]>
ValPackett[m]: i have finde the ic name in the commit message
<barni2000[m]>
s/finde/find/
<ValPackett[m]>
ohh cool
<barni2000[m]>
not all panel have detailed commit message
<ValPackett[m]>
looks like all these motorolas differ only in display panels and we'll need to separate out an msm89x7-motorola-common.dtsi before the copy&paste gets out of hand xD
<barni2000[m]>
it is including the "msm-pmi8950.dtsi" i have checked so charging and otg will be easy
<barni2000[m]>
btw there are nora wit 8920
<barni2000[m]>
s/wit/with/
<barni2000[m]>
8917+ipa = 8920
<ValPackett[m]>
oh that's the difference
<ValPackett[m]>
ayyyyyy, nora 1st boot with mostly copy&pasted dts: display works (simplefb failed 0.o "Framebuffer is not in virtual address space" so it was a blue screen and i went to see if it appeared on usb and there was the panel with the systemd log)
<ValPackett[m]>
wcnss fails to load
<ValPackett[m]>
gpu works, kmscube is rendering well and says it's using freedreno, idk why phosh showed up with a fully black screen..
<ValPackett[m]>
charger works, upower reports all the things
<ValPackett[m]>
oh i need the wifi blob that's not on the firmware partition okay
<barni2000[m]>
and you should set firmware-name = "qcom/msm8917/motorola/nora/" in wcnss_ctl node to be able to package it to the generic device package
<ValPackett[m]>
oh but we don't have the package yet?
<barni2000[m]>
we have
<barni2000[m]>
device-qcom-msm89x7
<barni2000[m]>
there is no firmware-qcom-msm89x7 yet but i will make it with 6.13 upadte
<barni2000[m]>
hannah, montana, nora, cedric will needs it