mszyprow|home has quit [Ping timeout: 240 seconds]
chewitt has joined #linux-exynos
_whitelogger has joined #linux-exynos
genii has quit [Quit: See you soon.]
Putti has quit [Ping timeout: 240 seconds]
GrimKriegor_ has quit [Quit: ZNC - https://znc.in]
GrimKriegor has joined #linux-exynos
GrimKriegor has quit [Changing host]
GrimKriegor has joined #linux-exynos
dllud has quit [Quit: ZNC 1.7.4 - https://znc.in]
dllud has joined #linux-exynos
mszyprow|home has joined #linux-exynos
afaerber has quit [Remote host closed the connection]
Putti has joined #linux-exynos
wwilly__ has joined #linux-exynos
wwilly_ has quit [Ping timeout: 240 seconds]
dlan has quit [Ping timeout: 240 seconds]
dlan has joined #linux-exynos
dlan has joined #linux-exynos
dlan has quit [Changing host]
_whitelogger has joined #linux-exynos
_whitelogger has joined #linux-exynos
chewitt has quit [Quit: Adios!]
genii has joined #linux-exynos
wwilly__ is now known as wwilly
mszyprow|home has quit [Ping timeout: 240 seconds]
<Putti> We think the graphics corruption on i9305 / exynos4412 might be related to another issue we noticed started happening after we updated kernel: the s-boot "Samsung Galaxy" logo gets purple/pink colored before the display gets initialized by kernel.
<Putti> so some change in kernel that is less than 1 year old might be causing this
<Putti> disabling IOMMU gets almost totally rid of the graphics corruption with the sboot logo, before it was corrupted for maybe 2 seconds but now it flashes quickly corrupt/purple just some tens of milliseconds before the 4 tux logos show up from the kernel meaning the display driver is initialized.
mszyprow|home has joined #linux-exynos
wwilly_ has joined #linux-exynos
wwilly has quit [Ping timeout: 240 seconds]
<Viciouss> Putti: I gave up on Android for now, focusing on the kernel driver part as it is already a lot to digest there in the time I can put into it. I had hwc.drm.use_overlay_planes=1 active in my configuration and it worked, I noticed some pixels with wrong color on the background but only if no app was open
<Viciouss> I've never had any issues with the Samsung logo
<Putti> Viciouss, which device did you use that worked?
<Viciouss> I used card0 for both hwc and gralloc
<Putti> Viciouss, also unless you use the lima render node for gralloc then it appears prime is not used
<Putti> aha, so that's it
<Putti> the prime stuff was not tested
<Putti> s/not tested/not used in your case/
<Putti> I was reading through some commits from icenowy and the prime buffer imports don't seem to work on Allwinner SoC either
<Putti> actually, now I'm not totally sure if that would not work. Will re-test your setup.
<freekurt> i'm in over my head with this discussion, but i saw this issue in the glodroid issue tracker about drm_hwcomposer, gbm_gralloc, KMS driver, and card0. https://github.com/GloDroid/glodroid_manifest/issues/31 not sure if it helps, but if it seems at all relevant to Replicant work, maybe it is worth adding a question or comment in that thread about this too since i think they are also working with Mali400.
<Putti> TBH, I don't know if we should use card or render node for gralloc, maybe the reason why HW plane composition is not done is something else, and card node would be the right one.
<Putti> everything works fine with card0 except the hw plane compositions don't seem to happen
mszyprow|home has quit [Ping timeout: 272 seconds]
genii has quit [Quit: See you soon.]
_whitelogger has joined #linux-exynos