10:59 <TangTang[m]> Thank you very much, the screen is working normally now

13:25 <Adrian[m]> did some work on u-boot :p

14:07 <uvraj[m]> neat

15:44 <uvraj[m]> What additions are required to add support for a new device to u-boot? I've been trying to port it to my Mi Note 10 Lite (toco), to no avail however.... (full message at <https://matrix.org/oftc/media/v1/media/download/AX33LUXbJTze_tWHBjkRcZku_PQZNHrIkhlo365DLiwMMf1AgSX0qph_N4q6lbVTFQmdMIwbQUeXTfa9bomBdNRCeWcsWAywAG1hdHJpeC5vcmcveG5XdnJ4SWpGaGhqRHFEeEZHTmpwQUxv>)

15:45 <uvraj[m]> s/DTB/DTS/

15:52 <Adrian[m]> that's pretty much how you do it, yes

15:52 <Adrian[m]> if it does not boot you either aren't using correct offsets or your devicetree is actually not correct

15:58 <uvraj[m]> I see. that's a bit dubious, since the mainline kernel works just fine with the device tree

16:06 <Adrian[m]> tip: disable your uart8 node

16:07 <Adrian[m]> for some reason I haven't figured out yet, it's broken on sweet, tucana and others, probably because it's in an incorrect state

16:08 <Adrian[m]> maybe https://lore.kernel.org/linux-arm-msm/20250408-msm-serial-earlycon-v1-1-429080127530@linaro.org/ fixes this

16:08 <Adrian[m]> but in u-boot it hard breaks boot

16:24 <f_> adrian: why ventoy ;p

16:24 <adrian> was the one thing that people will immediately believe me to have booted off of a usb stick, if i had sent a pmOS screenshot that wouldn't have implied it that directly ^^

16:24 <WaldemarTommetheythem[m]> wait, I just realized that there is no other power source. Which device is this?

16:25 <adrian> the power source is the usb-port, duh

16:25 <WaldemarTommetheythem[m]> :P I meant an external power source

16:25 <f_> adrian: smart

16:25 <f_> you could've done install ubuntu grub menu though :D

16:25 <adrian> right, i could've

16:26 <adrian> i want to make a postmarketOS-LIVE.iso for the shitpost now

16:26 <f_> brb installing ubuntu desktop on my SM7150 /j

16:33 <uvraj[m]> holy fuck it works

16:33 <uvraj[m]> thanks adrian

16:36 <f_> mind a PM adrian ?

16:36 <adrian> not at all :)

16:47 <ungeskriptet> Test

16:48 <adrian> test

16:51 <f_> test

16:51 <jojo_autoboy[m]> i wonder if you guys would accept patches from chromiumos which makes the phone run a bit better lol

17:15 <adrian> send them to the mailing-list rather than to us, unless it's config changes

17:20 <jojo_autoboy[m]> well actually on further testing using a config also from chromiumos seems to help a stuttering issue i'm having

17:20 <jojo_autoboy[m]> though this is on the 7125 so not sure if the 7150 also stutters like this

17:20 <jojo_autoboy[m]> mostly in firefox it's quite bad

17:21 <jojo_autoboy[m]> but it's a large diff so no idea what exactly could be causing it

17:52 <TangTang[m]> I tried to add the screen panel driver to the j706f, I checked the android kernel cmdline msm_drm.dsi_display0=dsi_rm69380_edo_amoled_cmd_display, generated using linux-mdss-dsi-panel-driver-generator, but the screen doesn't work, I also tried the driver for the lenovo-j716f (panel-raydium-rm69380.c) which is already in the mainline kernel, and it seems to have a similar panel, but the result is the same flickering yellow screen.

18:04 <JIaxyga[m]> <TangTang[m]> "2025-04-12-22-18-51-419.mp4" <- looks like dual dsi

18:06 <ungeskriptet[m]> Yeah, it's dual dsi

18:08 <ungeskriptet[m]> @tang2025:matrix.org You don't have to generate a new driver

18:08 <ungeskriptet[m]> You need to add your panel init sequence to the existing driver

18:08 <ungeskriptet[m]> TB-J716F and TB-J706F panels differ slightly

18:09 <ungeskriptet[m]> @tang2025:matrix.org I have TB-J716F by the way :)

18:10 <ungeskriptet[m]> Also make sure your dual DSI is set up properly

18:12 <ungeskriptet[m]> @tang2025:matrix.org https://github.com/mainlining/linux/blob/david/sm8250/master/arch/arm64/boot/dts/qcom/sm8250-lenovo-j716f.dts#L725

18:12 <ungeskriptet[m]> This works on TB-J716F

18:13 <ungeskriptet[m]> Essentially, you just need to add lenovo,j706f-edo-rm69380 to the panel driver with you init sequence

18:13 <ungeskriptet[m]> Take a look at how other driver implement multiple init sequences

18:15 <ungeskriptet[m]> Also you would be nice if you could try working on getting the cs35l41 amplifiers working

18:16 <ungeskriptet[m]> I'm getting some stupid error on TB-J716F

18:19 <ungeskriptet[m]> s/you/it/

19:01 <adrian> jojo_autoboy: if there's some config options you want to enable, send a PR

19:02 <jojo_autoboy[m]> well i need to figure out said config options first

19:03 <jojo_autoboy[m]> or could just be a symptom of something else

19:03 <jojo_autoboy[m]> but i guess no one else here experiences this?

19:58 <z3ntu|m> ungeskriptet: regarding https://gitlab.postmarketos.org/postmarketOS/matrix-irc-bridge-request/-/issues/1 if you remove the matrix.org IRC bridge then I can set up the new one

19:58 <ungeskriptet> Sure, let me do it

20:05 <ungeskriptet> i can't find the integration manager, wtf

20:07 <z3ntu> should be working now

20:07 <z3ntu|s> yep

20:09 <ungeskriptet|m> Thanks!

20:10 <adrian> nice ;)

20:14 <f_> \o/

20:16 <f_> adrian, ungeskriptet: you can set the bridge PL50 to have it sync bans/kicks across btw

20:17 <f_> other than that it should work just fine now, have fun!

20:18 <f_[m]> oh I see you already set it mod

20:18 <f_[m]> nice

20:19 <ungeskriptet> Yep :D

20:19 <ungeskriptet> By the way, how does the bridge work without a bot joining the IRC channel?

20:19 <f_> ungeskriptet: the same as how the matrix.org bridge does it

20:19 <f_> It looks at what the puppets receive in the channel

20:20 <ungeskriptet> Ahh right, I forgot

20:20 <f_> I think it just picks a random puppet in the channel and kinda uses it as a listener bot

20:22 <f_> only disadvantage would be: if there's no puppet in the channel, no messages bridge either ;p

20:22 <f_> but that's minor