08:45 <xtex[m]> Is there anything like memory layout map for msm8974?

08:48 <xtex[m]> I just tried to enable CONFIG_PSTORE and add a ramoops region to qcom-msm8974.dtsi. This worked properly on my samsung-klte (kltechnduo) device.

08:48 <xtex[m]> I am using 0x3e8e0000 for the region, which was referenced from qcom-msm8974-sony-xperia-rhine.dtsi, and worked here.

08:49 <xtex[m]> What's the difference between qcom-msm8974-6.7.y and qcom-msm8974-6.7-wip branch?

11:12 <aka_[m]> Y sounds like branch where they push stable updates

11:13 <aka_[m]> You can just you know compare commit history

13:57 <xtex[m]> Why is v6.7.0-msm8974 tagged on .y branch but v6.7.0-rc5-msm8974 on wip branch?

14:40 <z3ntu1> xtex 🅥: let's move this to #mainline:postmarketos.org , I replied to your previous message there

17:31 <lumag> z3ntu1, any update on the writeback modes?

18:06 <z3ntu1> lumag: What command output do you mean btw? Is this about "no mode for writeback" ?

18:06 <lumag> yes. And no modes in modetest -ac

18:07 <lumag> On my boards I see a list of modes for the writeback connector

18:09 <z3ntu1> lumag: dpu_wb_conn_get_modes doesn't seem to get called at all

18:10 <lumag> z3ntu1, hmm... I wonder how can that happen.

18:13 <z3ntu1> lumag: so `dpu_writeback_init` get called but that seems to be the last of writeback

18:14 <z3ntu1> at least with my current prints

18:15 <z3ntu1> and sure that libdrm 2.4.119 is new enough for writeback stuff?

18:16 <z3ntu1> or something's conditional during libdrm compilation or something stupid like that?

18:17 <lumag> z3ntu1, it's new enough :-D

18:17 <lumag> No. I'd assume it's something in drm core.

18:19 <lumag> z3ntu1, could you please run the kernel with `drm.debug=0x04 ignore_loglevel` and send me a dmesg?

19:19 <z3ntu1> lumag: I'll check a bit later

20:26 <lumag> z3ntu1, thank you!