libera/#maemo-leste/ Wednesday, 2021-08-25

sunshavihttps://blog.emacsen.net/blog/2021/08/23/floss-mobile-os-aug-2021/03:45
dreamersunshavi: tssk. doesn't even mention maemo-leste08:22
lelparazyd created a repository: https://github.com/maemo-leste/openvpn-network-applet11:11
uvostmlind_: we really need to get of ddk1.9 :(12:01
tmlind_uvos: yeah that thing is a big blocker :(12:02
uvoscould you update ts-buttons from the original repo next time12:03
uvosinstead of merging it12:03
uvosthere is a (minor) bug fix in there12:03
uvosi should also try again to merge it .....12:03
tmlind_ok i guess i should script it12:03
tmlind_and i need to sort out all the sucky modem gsmtty stuff..12:03
uvosso far i have not been able to get anyone to comment on it even on the input ml12:03
tmlind_heh yeah12:04
uvoswhich is annoying12:04
tmlind_hmm so what can we do get stuff working with ddk-1.17 instead of ddk-1.9?12:04
uvosno one is working on it right now12:04
uvosso in theory it should work but there are lots of bugs12:04
tmlind_heh12:05
uvosand its allways really hard to decern if its the blobs fault12:05
tmlind_you mean fmg's test app?12:05
uvoshttps://github.com/maemo-leste/bugtracker/issues/52412:05
uvosread the log here12:05
tmlind_ok12:05
uvosthere are 2 methods12:06
uvosa main problem here being that none of us know if what glamor dose it to spec or not12:06
tmlind_no idea12:07
tmlind_so we currently get noting on the screen with pvr_egl_shim?12:07
uvoswe do12:07
tmlind_oh12:07
uvosits glamors own rendering that breaks12:08
uvosand then there is wierd stuff like pvr just breaking depending on where you glfinish12:08
tmlind_sounds like it could be glamor missing some gles parts?12:08
uvosand n900 flat out not working at all12:08
uvosno it uses the egl/gbm interfaces in ways that are unclear if its compatible with gles12:09
tmlind_heh ok12:09
uvosmesa swalows this fine but who knows12:09
tmlind_can we somehow test the approach on gles without pvr on some hardware?12:10
uvosit works on radionsi12:10
tmlind_but that's not gles?12:10
uvosi forced patched glamor into gles mode12:10
uvosradionsi also supports gles ofc12:11
tmlind_ok.. may not still be gles only?12:11
uvoswell its useing libgles12:11
uvosofc the gl support in egl might make a difference12:11
tmlind_hmm but i guess if you patched it to force gles that answers the question :)12:11
uvosi have no idea really12:11
tmlind_anything else we can do to test it individually for smaller components?12:12
uvosnot really so fmg wrote his test app and it narrows it down to a call that glamor dose12:13
uvosif you reproduce glamors path in it it breaks12:13
uvosand if you do it a different way it works12:13
uvoswe dont know if the glamor path is illigal12:13
uvosor pvr is buggy12:14
Wizzupright, and I think you said that if what glamor does is illegal, we have to fix up all the places where it does it wrong12:14
uvosright12:15
uvoseven then the performance is wierd, and fmg had to introduce glfinish in random places to make it work12:15
WizzupThat does kind of sound like pvr has some problems12:16
Wizzupbut iirc we had no place to report potential issues, other than some forums, I guess?12:16
uvosno idea12:17
uvosi gues the best path is to repo it on some chip ti still has in its catalog12:17
uvosie the industrial variants of the omap412:17
tmlind_fyi, pvr ddk-1.17 with wayland works surprisingly well with the patches we carry, kind of makes me suspect the issue is in glamor12:18
uvostmlind_: well one thing is12:18
uvosthat the performance on plain drm/gbm is mutch lower than on wayland12:18
uvoswhich makes no sense12:18
uvosand is nothing we could be at fault for12:19
Wizzupuvos: which devices are that?12:19
uvosthe d4 and yes this could be an interaction with the command mode display12:20
Wizzupuvos: sorry, I mean the supported ones12:20
uvosmight be usefull to have mz617 working to ellimitae that possibility12:20
uvosAM4379 for instance12:22
uvosthere are several12:22
uvosi think tmlind_ is knowlagble on what ti processors are based on omap4 platform12:22
tmlind_i think am43 has still pvr53012:24
tmlind_for mz617, there seem to be lots of issues with drivers/gpu/drm/bridge currently, seems like many bridge drivers are having issues right now12:24
tmlind_i guess the patches to move to use drm atomic functions caused some issues for bridges12:25
uvosthats good to hear in a way12:25
tmlind_also bridges on i2c bus have extra issues with the two possible probe paths12:25
uvosat least a suspect problem is well known12:26
uvosi have not found the time yet to look at mz617 at all since i decided to get calls working first ;)12:26
tmlind_yeah best to ask around from folks using bridges for mz617 and wait a bit to let things settle12:26
tmlind_yeh me neither12:26
tmlind_i doubt anybody at ti is going to spend any time on the pvr issue we have, we need to come up with some other solutions12:27
uvoswe can probubly patch glamor to high heaven and make it work12:27
uvosbut its not fun work12:28
uvossince it feals very random when pvr decides to work an when not12:28
WizzupCould it be a problem in kernel comms somehow?12:28
tmlind_could it be some pm related issue?12:28
uvosso manny questions :P12:28
uvosi wish i knew12:28
tmlind_we need to establish some bounty for fixing this :)12:29
Wizzupwe could probably12:29
uvoswe can then have a modesetting ddx fork that we patch to load glamor-prv12:29
uvosand then have package it seperately12:29
uvosso a hacked ddx would be ok packaging wise12:29
uvos(ie you want to be able to use regular modesetting on pp)12:30
tmlind_so what happens with pvr_egl_shim on pinephone? that should be gles only, right?12:31
uvospp supports gl12:31
tmlind_oh12:31
tmlind_well wlroots needs some patches for the gles calls and i guess fmg fixed up xorg also for some gles calls12:33
tmlind_are there any glTexSubImage2D GL_TEXTURE_2D calls in glamor path?12:34
uvosyeah12:35
uvosthats what breaks12:35
uvoson egl textures12:35
uvosnot gl12:35
uvosEGL_KHR_12:35
tmlind_some calls need gles version specific handling12:35
uvosdoc?12:36
tmlind_mostly xcracer's wlroots patch12:36
tmlind_but that patch does not include EGL_KHR_, not sure if wlroots already has some handling for those?12:37
tmlind_yeah grepping wlroots for EGL_KHR_ shows some version specific handling12:38
tmlind_$ git grep -C10 EGL_KHR_ | grep check_egl_ext12:39
tmlind_render/egl.c-   if (!check_egl_ext(client_exts_str, "EGL_EXT_platform_base")) {12:39
tmlind_render/egl.c:   if (check_egl_ext(client_exts_str, "EGL_KHR_debug")) {12:39
tmlind_render/egl.c:   if (check_egl_ext(display_exts_str, "EGL_KHR_image_base")) {12:39
tmlind_render/egl.c-           check_egl_ext(display_exts_str, "EGL_EXT_buffer_age");12:39
tmlind_render/egl.c:   if (check_egl_ext(display_exts_str, "EGL_KHR_swap_buffers_with_damage")) {12:39
tmlind_render/egl.c-   } else if (check_egl_ext(display_exts_str,12:39
uvoscould you link xcracer patch too12:42
uvosor the commit id12:43
uvosif its in mainline wlroots12:43
tmlind_i think it's in the pmos bugzilla entry12:47
tmlind_that should be added to the ml bug page if not there12:47
tmlind_this one: https://gitlab.com/postmarketOS/pmaports/-/issues/93212:48
tmlind_see patch attached there, 0001-render-Don-t-use-GL_EXT_unpack_subimage-when-not-ava.patch12:50
tmlind_heh see also the comment there: ".. I've tried xfce4 but the blobs are missing an extension (GL_OES_texture_border_clamp) required by glamor for modesetting plus according to the Maemo guys there's other issues with gles2 and glamor/modesetting."12:54
uvosi need to setup an enviroment to play with this again13:00
uvosi gues i have an extra xt875 i can dedicate to the task13:00
tmlind_with wlroots, without the GL_TEXTURE_2D handling as in the patch there was no output in sway, just window frames13:20
tmlind_maybe it's possible to test on some different hardware if pvr_egl_shim works with gles3 but fail with gles2 as on these pvr using devices13:35
tmlind_like for example the pvr docs describe for GL_OES_texture_border_clamp at https://docs.imgtec.com/Architecture_Guides/Supported_Extensions_OpenGL_ES_EGL/topics/d0e7745.html13:36
tmlind_hmm so maybe that page explains why GL_CLAMP_TO_EDGE is needed for gles213:44
tmlind_i don't understand though, does these pages show how to implement the missing extensions for pvr or what?13:50
tmlind_like does the example for GL_EXT_texture_border_clamp show how to implement it? https://docs.imgtec.com/Architecture_Guides/Supported_Extensions_OpenGL_ES_EGL/topics/d0e3348.html13:51
tmlind_or is GL_EXT_texture_border_clamp just an extension name for gl?13:51
* tmlind_ confused13:51
uvosits a extension name for gles too13:52
uvosbut its only implmented for gpus > sgx13:52
tmlind_ok13:52
tmlind_note to self, some more info on CLAMP_TO_EDGE at https://www.opengl.org/archives/resources/code/samples/sig99/advanced99/notes/node64.html13:56
tmlind_heh maybe we can just file an xfce4 bug saying pvr with gles2 does not work :)14:00
uvosxD15:23
freemangordonuvos: IIRC, with the latest kernel I tried, gbm performance was ok20:06
freemangordon5.10 or 5.1120:06
freemangordoncan;t remember20:06
freemangordonok, it seems indent pointer bug is triggered by typedef-ed struct. It seems it thinks this is multiply, not declaration.20:15
freemangordonWizzup: do you know any other tool than indent?20:17
freemangordonthere is some uncrustify thingie, going to check it20:23
uvosyou cant turn off it changeing the postion of *20:43
uvos?20:43
uvoswould be an obvious option to add20:43
uvossince its totaly impossible to detemine if something is a mult or a pointer based on just one source file20:43
uvoshm which makes me wonder20:49
uvoshow dose the compiler know what this means:20:50
uvosint number = 10;20:50
freemangordonuvos: you can't turn it off20:50
uvosKlass *somepointer20:50
freemangordonuncrustify seems promising20:50
uvossome_function(number*somepointer);20:50
freemangordonit has couple of hundred options :D20:51
uvosfreemangordon: heh20:51
freemangordonbut seem syou can fine tune it, if you find the option you need, ofc ;)20:51
uvosso in the above example am i multiplying the pointer adress by 10 or am i derefencing it and mult that by 1020:52
uvoshow dose the compiler now20:52
uvos*know20:52
uvosoh right dereference would be number**somepointer20:52
uvosnvm20:53
freemangordonhttps://en.cppreference.com/w/c/language/operator_precedence20:53
freemangordon:p20:53
freemangordonbut, as I am never sure, I always put braces20:53
uvosyeah nvm its not ambiguous20:55
uvosi was confused20:55
freemangordonI think this https://github.com/uncrustify/uncrustify will do the job20:56

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!