ChanServ changed the topic of #linux-msm to:
<alfayt[m]> Btw what happened to framebuffer on sagami?
davidinux is now known as Guest7646
davidinux has joined #linux-msm
Guest7646 has quit [Ping timeout: 480 seconds]
davidinux is now known as Guest7663
davidinux has joined #linux-msm
Guest7663 has quit [Ping timeout: 480 seconds]
davidinux has quit [Quit: WeeChat 3.5]
davidinux has joined #linux-msm
davidinux has left #linux-msm [#linux-msm]
davidinux has joined #linux-msm
pevik has quit [Remote host closed the connection]
pespin has joined #linux-msm
pespin has quit []
pespin has joined #linux-msm
<Marijn[m]> alfayt: if you know...
<Marijn[m]> alfayt: Sorry I mixed up 5III and 5IV. 5III is known-working, 5IV has a panel driver that I haven't yet generated/fixed but it shouldn't have anything out of the ordinary.
<Marijn[m]> alfayt: 1III however has the exact same panel as 1IV, so the exact same ~problems~ TODO items.
<Marijn[m]> (For everyone else: 1IV/5IV is Sony's Nagara platform, 1III/5III is Sony's Sagami platform)
telent has quit [Quit: The Lounge - https://thelounge.chat]
telent has joined #linux-msm
Danct12 has quit [Quit: A-lined: User has been AVIVA lined]
Danct12 has joined #linux-msm
<mort_> every frame, that kzalloc leaks 256 bytes from the kmalloc-256 slab allocator
<mort_> I've added prints to the drm_crtc_commit_get/drm_crtc_commit_put functions, and for each allocated commit, the refcount jumps up and down a bit before reaching 1 and staying there
<mort_> https://p.mort.coffee/DVX here's the stack trace for every get and put for a particular commit
<mort_> I don't know that I'm capable of debugging this on my own...
pespin has quit [Remote host closed the connection]