ChanServ changed the topic of #msm8937-mainline to: Boot Linux on your MSM8917/37/40 and QM215 mobile! | GitHub: https://github.com/msm89x7-mainline | Logs: https://oftc.irclog.whitequark.org/msm8937-mainline | Bridged to #msm8937-mainline:kde.org on Matrix
Daanct12 has joined #msm8937-mainline
<barni2000[m]> NekoCWD @nekocwd:matrix.nekocwd.duckdns.org: i have sent a fix for msm-firmware-loader and it was merged you can check on tiare
<barni2000[m]> If it not works you should remove target dir once but first check without the removal
Daanct12 has quit [Quit: WeeChat 4.6.3]
<barni2000[m]> 0xCAFEBABE: can you get this from downstream `[ 4.217627] swb.mdss_dsi_panel_power_on:get lcd_detect id0=0,id1=1`
<barni2000[m]> ili is 0 0 tm is 0 1
<M0xCAFEBABE[m]> <barni2000[m]> "0xCAFEBABE: can you get this..." <- gpio 59 and 66 right?
<M0xCAFEBABE[m]> tho... idk if you should hardcode the behavior in panel driver
<M0xCAFEBABE[m]> * tho... idk if you should hardcode the behavior
<M0xCAFEBABE[m]> s/in/depending/, s/panel/on/, s/driver/the given value/
<barni2000[m]> dmesg will show you
<barni2000[m]> Boot into a recovery
<barni2000[m]> dmesg | grep dsi
<M0xCAFEBABE[m]> [ 7.050606] mdss_dsi_panel_config_res_properties: xiaomi_ulysse_board_id0=0, xiaomi_ulysse_board_id1=1
<M0xCAFEBABE[m]> [ 7.051624] mdss_dsi_panel_power_on: xiaomi_ulysse_ID0_status=0, xiaomi_ulysse_ID1_status=1
<M0xCAFEBABE[m]> barni2000[m]: i gave you both
<M0xCAFEBABE[m]> the one you wanted is there too
barni2000[m]1 has joined #msm8937-mainline
<barni2000[m]1> But do not you have hx display?
<M0xCAFEBABE[m]> <barni2000[m]1> "But do not you have hx display?" <- it's on my ugglite
<M0xCAFEBABE[m]> my ugg has tm
<barni2000[m]1> And where the log comes from?
<M0xCAFEBABE[m]> ugg
<barni2000[m]1> Oh, i interedted in hx i have tm and sc
<M0xCAFEBABE[m]> ok, sec
<M0xCAFEBABE[m]> id0_status=1, id1_status=0
<M0xCAFEBABE[m]> board_id0=0, board_id1=1 (btw)
<barni2000[m]1> Thx