tanakian has joined #maemo-leste
<_inky> rafael2k: and thank you too for advices and ideas.
<_inky> i think eventually we have breakthroughs with pinephone support.
<_inky> and this is very important: people come to linux phones and operating systems via pinephone.
<_inky> so maemo will actually get more users via pinephone.
<_inky> i'll ask these couple of days if i need to update from -devel to get the updates you all made.
tanakian has quit [Quit: tanakian]
BenLand100 has quit [Ping timeout: 268 seconds]
BenLand100 has joined #maemo-leste
BenLand100 has quit [Changing host]
BenLand100 has joined #maemo-leste
Pali has quit [Ping timeout: 240 seconds]
joerg has quit [Ping timeout: 240 seconds]
joerg has joined #maemo-leste
Wikiwide has joined #maemo-leste
macros_ has joined #maemo-leste
macros__ has quit [Ping timeout: 268 seconds]
<tmlind> hmm my bionic is all updated now, but not accelerated.. i have sgx-ddk-um-ti443x and xserver-xorg-video-omap installed, kernel module is initialized on boot..
<freemangordon> tmlind: check xorg.conf
<tmlind> freemangordon: don't seem to have one.. should it be under /etc/X11?
<freemangordon> no, /usr/share/X11/xorg.conf.d
<tmlind> ok
<freemangordon> there should be 99-omap
<tmlind> i have 99-omap.conf symlinked to 99-omap.conf.leste
<freemangordon> yeah
<freemangordon> that's fine
<freemangordon> could you provide xorg log, from /tmp
<tmlind> ok
<tmlind> freemangordon: http://muru.com/Xorg.0.log
<tmlind> not much there for EE errors
<tmlind> also trying to run glxgears as user user fails
<tmlind> /dev/dri is group readable/writable for video
<freemangordon> glxgears?
<freemangordon> you should run es2_gears
<tmlind> oh ok
<freemangordon> OGL is not accelerated
<freemangordon> brb
<tmlind> ok es2gears works :)
<tmlind> stellarium is not accelerated, let me recheck
<tmlind> starting stellarium as user produces: QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled
<tmlind> i can start is as root but it's not accelerated
<tmlind> fyi
<tmlind> hmm es2tri triangle is only partially visible somehow
<freemangordon> does glmark2_es2 work?
<freemangordon> tmlind: actually, does your device boot to h-d?
<tmlind> freemangordon: yeah boots now to h-d, looks like stellarium tries to start with sgx with QT_QPA_PLATFORM=eglfs stellarium
<tmlind> then segfaults
<tmlind> let me check glmark2_es2
<tmlind> hmm can't find glmark2 package..
<freemangordon> h-d is accelerated, right?
<freemangordon> glmark2 shall be compiled, there is no package
<tmlind> ok, h-d looks a bit jerky, not sure if it's accelerated
<freemangordon> hmm, weird
<tmlind> i'm pretty sure h-d is accelerated, only jerky here and there
<freemangordon> that's weird, should be smooth
<freemangordon> but well, i have d4 here, not bionic
<tmlind> should be about the same
<freemangordon> maybe lets wait for Wizzup to share his experience
<freemangordon> but swiping h-d should be smooth
<freemangordon> well, non-accelerated h-d renders with 1-2 fps, so... :)
<tmlind> yeah it's mostly smooth, sometimes starting a new app the animation is kind of jerky..
<freemangordon> ah
<freemangordon> well, for sure we have issues on omap, there is also tearing and the reported fps looks too high for what is really seens
<freemangordon> *seen
<freemangordon> but otherwise is useful
<tmlind> yup looks way better than earlier :)
<tmlind> heh looks like gdb shows stellarium segfaults at ssl libcrypto somewhere..
<tmlind> ok got stellarium running with QT_QPA_PLATFORM=eglfs stellarium
<tmlind> sorry with QT_QPA_PLATFORM=eglfs stellarium --home-planet=mars
<tmlind> some location lookup issue it seems :)
<tmlind> about 9 fps it seems
<freemangordon> :)
<freemangordon> hmm, shouldn;t it be faster?
<tmlind> i'm seeing someting like 12 fps with wayland
<freemangordon> ah
<freemangordon> well, given that compositing is non-accelerated...
<freemangordon> hmm, maybe I shall RE that part too
<freemangordon> btw, is it fullscreen?
<tmlind> yeah it's full screen
<freemangordon> hmm
<freemangordon> should be the same like WL
<freemangordon> if not faster
<tmlind> let me check again on wl
<freemangordon> with 'mars'
<tmlind> uh looks like i have some pvr issue with my wl setup right now, need to check the fps later
<tmlind> switching from stellarium to h-d window list hung xorg
<freemangordon> hmm
<freemangordon> some oops?
<tmlind> no, Xorg.0.log has many (EE) OMAP(0): ERROR: waitForBlitsCompleteOnDeviceMem: PVR2DQueryBlitsComplete failed with error code: -8 (Blit not complete)
<freemangordon> this should not result in a hang
<tmlind> keeps producing them about every 500 ms
<freemangordon> dmesg?
<freemangordon> I would say there is HW recovery trigered
<tmlind> no errors
<freemangordon> weird
<tmlind> what should i type to restart xorg?
<freemangordon> nothing
<freemangordon> I mean - you shoud restart the device
<tmlind> killall -9 Xorg at least got fb back
<freemangordon> yeah
<freemangordon> hmm, we even have tearing with modesetting without glamor
<freemangordon> this is omapdrm behaving I would say
<tmlind> weird now it's behaving after a reboot
<freemangordon> hmm?
<freemangordon> you mean there are no issues?
<tmlind> can't make QT_QPA_PLATFORM=eglfs stellarium --home-planet=mars hang after switching between app view and stellarium
<freemangordon> it should not :)
<freemangordon> I was hoping modesetting with glamor will hit > 50 fps on d4
<freemangordon> but unfortunately it hits 50fps and that's it
<freemangordon> and it suffers from the same tearing issue
<tmlind> anyways a massive upgrade to get rid of all the old buggy legacy crap with the kernels and ddk-1.9 :)
* tmlind goes to investigate fridge for the ham
<freemangordon> tmlind: any advice on how to deal with omapdrm tearing issue? I need upstream support, but I doubt Tomi will care about that
Twig has joined #maemo-leste
Wikiwide has quit [Ping timeout: 268 seconds]
<Wizzup> rafael2k: once I get home in ~8 hours I'll look at packaging this stuff, ty
<Wizzup> 08:56 < tmlind> heh looks like gdb shows stellarium segfaults at ssl libcrypto somewhere..
<Wizzup> this is openssl testing instructions (sigill)
<Wizzup> freemangordon: same for lima bug/video, will do that when I get back
<freemangordon> ok
<freemangordon> no hurry
<Wizzup> :)
<Wizzup> Just don't have the device here at the moment
<freemangordon> yay, omapdrm BO patch is in -next :)
<tmlind> freemangordon: what's the omapdrm tearing issue?
<tmlind> Wizzup: i guess that openssl issue will get fixed upstream pretty fast
<freemangordon> tmlind: h-d swiping tears terribly
<freemangordon> it is clearly visible in portrait
<freemangordon> rotate you bionic in portrait and swipe
<freemangordon> *your
<freemangordon> this happens with both omap and modesetting drivers
<freemangordon> with modesetting it happens even with no HW accel, though less visible because of low fps
<freemangordon> I wonder if it is caused by omapdrm starting another flush while still there is a flush in progress
<freemangordon> but, it happens on hdmi too
<freemangordon> hmm, actually lemme try again on hdmi
xmn has quit [Quit: ZZZzzz…]
<freemangordon> yep, there is tearing on HDMI as well
<tmlind> ok
<freemangordon> tmlind: hmm, if I lower the SGX frequency to 0x1f, tearing disappears on HDMI
<freemangordon> I guess by the time the new frame is ready the old one has already been flushed or somesuch
<tmlind> weird
<Wizzup> tmlind: I don't think it is an issue, it's just it testing for instructions with sigill signal handler
<tmlind> does reverting "drm/omap: Fix omap_gem_dma_sync_buffer() when we already have a dma_addr" make it better or worse by any chance?
<Wizzup> tmlind: as in I don't think this is a bug, you just see it in gdb, but you can type 'c' for continue
<freemangordon> tmlind: lemme try
<tmlind> so the test is to swipe the desktop background in portrait mode?
<freemangordon> yes
<tmlind> can't seem to make it happen on my bionic
<freemangordon> the same happens in landscape, but is less visible
<freemangordon> install marina theme
<tmlind> i see a bit of flicker if i drag slowly
<freemangordon> yep
<freemangordon> hmm, wait
<freemangordon> tmlind: please install marina theme
<tmlind> ok
<freemangordon> it has very sharp transition between backgrounds
<Wizzup> maybe just share the tearing test image
* Wizzup bbiab
<freemangordon> marina is in the repos
<freemangordon> and is cute, also :)
<tmlind> yup with marina i see a variant of the black squares problem dragging the desktop slowly
<tmlind> and also tearing between the desktop image borders
dsc_ has quit [Ping timeout: 256 seconds]
<freemangordon> exactly
<freemangordon> this is what I mean
dsc_ has joined #maemo-leste
<freemangordon> this happens no matter driver/acceleration
<freemangordon> thats why I think it is omapdrm
<tmlind> i'm guessing the black artifacts problem gets worse with "drm/omap: Fix omap_gem_dma_sync_buffer() when we already have a dma_addr" reverted?
<tmlind> the tearing might get better..
<freemangordon> reverting as we speak :)
<freemangordon> I see no black artifacts though
<freemangordon> sometimes I see some corrupted pixels (black) in the left top corner
<tmlind> in portrait mode, slowly keep swiping to the left until you see tiny black rectangles at top right corner
<freemangordon> ok
<freemangordon> nope
<tmlind> top left corner in landscape mode, top right corner in portrait mode
<tmlind> or is it part of the background image pixmap?
<freemangordon> nope
<freemangordon> no
<tmlind> maybe it's part of the pixmap at the top right in portrait mode at the light blue area just before the dark blue border
<freemangordon> I see nothing mis-rendered
<freemangordon> can;t see that here
<freemangordon> tmlind: sometimes bacground has some corruption, restart fixes that
<tmlind> i see it on every 4th desktop
<freemangordon> yep, that one :)
<freemangordon> it is on top-left in portrait
<tmlind> yup, so is that supposed to be there?
<freemangordon> and lives just behind six bars
<freemangordon> no
<freemangordon> this is deffinitely a corruption
<tmlind> yeah that's the black tiles artifacts problem i also see with sway
<freemangordon> could you take a picture, to confirm we are talking about the same thing
<tmlind> let me consult my camera operator
<freemangordon> :D
<freemangordon> tmlind: honestly, I don;t think this has anything to do with omapdrm
<freemangordon> this looks like a bug in pvr
<tmlind> could be
<freemangordon> oh, lemme revert that patch
<freemangordon> hmm, this patch looks to me like a reason for low fps :)
<tmlind> ok :)
<freemangordon> lets see on the dvice though
<tmlind> see the black ants at top right corner here http://muru.com/m-l-ants.jpg
<freemangordon> yes, exactly this
<freemangordon> reboot fixes it usually
<freemangordon> this happens more often if your battery is low
<tmlind> weird
<freemangordon> but I am almost sure this is either PVR or h-d/clutter bug
<tmlind> so a variation of the ants problem i see on wayland is a bit larger black rectangles in the same location, top left corner for landscape mode
<freemangordon> because this corruption is exactly behind and with the size of six squares icon
<freemangordon> could be
<freemangordon> but I almost never see that after a reboot
<freemangordon> only if I play stopping/starting xorg/h-d
<tmlind> well m-l should revert "drm/omap: Fix omap_gem_dma_sync_buffer() when we already have a dma_addr" if it causes no other issues, wayland is unusable without that patch
<freemangordon> this should be fixed in wl though
<tmlind> no idea how it should be fixed :(
<tmlind> especially if m-l also shows a similar issue on xorg
<freemangordon> it should use sync
<freemangordon> xorg uses "wait for blits"
<freemangordon> but WL can include sync objects in GL commands stream and wait for them, IIUC
<tmlind> i don't think i've seen the ants with weston
<freemangordon> ugh, I should have fixed TS buttons udev rules before reboot :(
<freemangordon> now I have to wait device to autoconnect
<tmlind> weird how the autoconnect stuff still takes few mins
<freemangordon> not on pinephone though
<tmlind> weird
<freemangordon> so it is something with d4 driver
<tmlind> i wonder if adding iw dev wlan0 scan on start up would help
<freemangordon> still tears
<freemangordon> lemme check fps
<freemangordon> oh
<freemangordon> we hit 80 fps with ease
<tmlind> nice
<tmlind> maybe check the stellarium on mars rate too?
<freemangordon> is it in repos?
<tmlind> yeah apt-get install stellarium
<tmlind> takes a while for the data files though
<freemangordon> maep renders with 45 fps though
<freemangordon> this is with 3-buffer
<tmlind> need to go for some family time now, ttyl
<freemangordon> ttyl
<freemangordon> yay! I know why fps is too low - tmlind broke it :p
Treebeard has joined #maemo-leste
Treebeard has joined #maemo-leste
Treebeard has quit [Changing host]
BenLand100 has quit [Ping timeout: 240 seconds]
Treebeard is now known as BenLand100
<freemangordon> tmlind: fps ~9
<freemangordon> but, nothing moves, is that normal?
<freemangordon> oh, ok, we hit 80 fps without 3-buffer
<freemangordon> I think we shall disable it by default
<freemangordon> at least on d4 it doesn;t seem we need 3-buffer
<rafael2k> Wizzup: tks
<rafael2k> Wizzup: ofono will be pretty easy
<rafael2k> Wizzup: kernel wise, I want some help with git, and also some suggestion if I should just add the line in rules to install kernel, initrd and dts to /boot, or may be use a postinst scrit...
<freemangordon> wow, firefox renders as mad!
<freemangordon> hmm, why there is no sound?
<rafael2k> Wizzup: dtbs are being installed in /usr/lib/linux-image-5.15.10/allwinner/ and I copied by hand to /boot/allwinner
<rafael2k> Wizzup: kernel and initrd are installed, but they dont get copied to ddefault locations specified in boot.txt
<Wizzup> freemangordon: what did you change?
<Wizzup> rafael2k: ok
_inky has quit [Ping timeout: 256 seconds]
inky has quit [Ping timeout: 240 seconds]
Pali has joined #maemo-leste
inky has joined #maemo-leste
inky has quit [Ping timeout: 256 seconds]
DPA has quit [Ping timeout: 240 seconds]
DPA- has joined #maemo-leste
DPA- has quit [Client Quit]
DPA has joined #maemo-leste
<freemangordon> Wizzup: reverted 6dd1aad1d0c4716944098b7b0f2abdd3a26cc0be.
<freemangordon> we must do that asap
<Wizzup> freemangordon: in kernel?
<Wizzup> freemangordon: asap as in. now?
<freemangordon> yes, in kernel
<freemangordon> asas as 'as soon as we can'
<freemangordon> this brings massive improvement on d4 and n900 (not tested)
<freemangordon> and will allow us to not use 3-buffer
<freemangordon> which will reduce memory usage
<freemangordon> this commit is the reason for 6ms delay in drmModePageFlip()
<bencoh> don't we want to actually flush cache to memory during sync_buffer() ?
inky has joined #maemo-leste
inky has quit [Ping timeout: 240 seconds]
<Wizzup> freemangordon: ok
<Wizzup> freemangordon: ok so I'll make a trace of the fallback method, *without* EGL_BUFFER_PRESERVED set?
<Wizzup> or with?
<Wizzup> because I already have both
inky has joined #maemo-leste
inky has quit [Remote host closed the connection]
inky has joined #maemo-leste
<freemangordon> without
<freemangordon> bencoh: I think this is done on the other side (GPU)
<bencoh> hmm ...
<freemangordon> IIUC
<bencoh> so the gpu automatically forces a cache sync when pushing a frame to it?
<freemangordon> I don;t really know when pvr driver flush caches
<bencoh> ah
<freemangordon> but it does
<bencoh> so it happens on the cpu side
<bencoh> wait, something's wrong ... if it already takes place, why would it take 6ms?
<freemangordon> ah, yes, if you look at it like that
<bencoh> I mean, why would it take another 6ms?
<freemangordon> bencoh: this commit in omapdrm
<freemangordon> not in pvr driver
<bencoh> aren't both used in our case?
<freemangordon> yes, they are
<bencoh> I feel like I'm missing something
<freemangordon> but omapdrm is not the one to flush anything, as it renders nothing
<freemangordon> maybe I am missing something too
<bencoh> sure, but then why would flushing writes to buffer take 6ms?
<freemangordon> I am not sure what dma_sync_single_for_device does
<bencoh> (unless that sync-to-device does more than what I think it should do on our platform, and for some reason takes a lot of time)
<freemangordon> this is done for every page of our scanout buffer
<freemangordon> and yes, maybe it does more
<bencoh> I guess you checked reverting that commit doesn't result in (more) tearing? :)
<freemangordon> I don;t see how this commit may affect tearing
<freemangordon> and yes, I checked :)
<freemangordon> it affects fps only
<bencoh> well, gpu fetching a non-fully-synced buffer sounds like tearing expected to me, hence me asking :)
<freemangordon> that's the point, gpu should fetch nothing here
<freemangordon> gpu has already rendered and we prepare the buffer for displaying
<bencoh> but it's supposed to fetch later on
<bencoh> hmm
<freemangordon> why is that?
<bencoh> wait, I might be the one missing something
<bencoh> (I probably am)
<Wizzup> freemangordon: hm ok, but didn't enunez ask to have it on?
<bencoh> is that an input buffer to gpu, or an output buffer from gpu?
<Wizzup> maybe I will share both
<freemangordon> Wizzup: ok
<freemangordon> bencoh: this is a back buffer (so output) we are preparing to flip to be front
<freemangordon> gpu == renderer, gpu != display controler
<freemangordon> so, this buffer is output for gpu and input for display controller
<freemangordon> and this is display controller (so CPU) doing sync
<freemangordon> but there is nothing to be synced, IIUC, as CPU does not render
<freemangordon> I think this commit mitigates the issues tmlind has with WL as it adds a delay, during which GPU finishes rendering
<freemangordon> but not fully, as sometims GPU needs more than 6ms to render
<freemangordon> does this sound sane?
<freemangordon> it is absolutely possible that I am talking nonsense here, but the net effect is that reverting that results in stable 80fps being hit on h-d swiping without any visible rendering artifacts, besides the tearing and ants, but they are there with and without that commit
<freemangordon> and also removing that commit results in drmModePageFlip() behave according to specs
<freemangordon> (didn;t check xorg logs though)
xmn has joined #maemo-leste
<Wizzup> freemangordon: ok so I will revert 6dd1aad1d0c4716944098b7b0f2abdd3a26cc0be for now in our -devel kernel
rafael2k has quit [Ping timeout: 256 seconds]
<tmlind> ack, that patch is a hack
<freemangordon> Wizzup: :mod:
<freemangordon> :nod:
<freemangordon> Wizzup: shall I disable 3-buffer to be enabled by default in omap code?
<freemangordon> I think this is the sane
<freemangordon> the other option is to disable it in config
<Wizzup> I would disable by default if we have no use for it
<freemangordon> ok, will disable and spin a new build
<Wizzup> ty
<Wizzup> maybe wait for kernel to complete
<freemangordon> for the build?
<freemangordon> sure
<freemangordon> tmlind: can you recall any other hack patch that might be related to tearing?
<freemangordon> hmm, I think I know what the possible fix for the corruption could be, in xorg
<freemangordon> there is pvr driver call that flushes GPU buffers to memory
<Wizzup> great @ corruption
<freemangordon> well, I think this is of low prio
<Wizzup> mhm
<tmlind> freemangordon: well are you seeing the same issues on n900? if not, it's somehow related to the tiler possibly
<freemangordon> never seen
<freemangordon> IIRC
<freemangordon> yeah, could be related to tiler
<freemangordon> Wizzup: ever seens something like http://muru.com/m-l-ants.jpg on n900?
<Wizzup> I do not recall at the moment, I only saw these problems on d4 windows
<freemangordon> mhm
<Wizzup> but my n900 doesn't run for very long on X atm
<Wizzup> because of the alloc problems
<freemangordon> yeah, but this happens on startup only
<freemangordon> without running any application
<Wizzup> never saw that on d4 either
<Wizzup> I only see it in overview windows
<freemangordon> I am seeing it occasionally
<Wizzup> compose view
<freemangordon> could be related to compositing being done on CPU
<freemangordon> maybe those will disappear when I implement GPU compositing accel
<Wizzup> how does that work?
<freemangordon> HW accel compositing?
<freemangordon> USSE code in pvr exa
<freemangordon> binary shaders IIUC
<Wizzup> ok
<freemangordon> could be a bug i nclutter as well
<freemangordon> so, tomorrow will start implementing non-CMA buffers support
<freemangordon> hopefully shouldn;t take much time
<tmlind> i wonder what would happen with omapdrm .cpu_cache_flags = OMAP_BO_UNCACHED for omap4?
<tmlind> just as an experiment to see if the issues disappear
<tmlind> instead of OMAP_BO_WC
<freemangordon> try it, I am curious as well
<tmlind> yeah might be worth trying
<freemangordon> Wizzup: hmm, seems like kernel build is not progressing
<freemangordon> oh, scratch that
<freemangordon> I was looking at wrong xonsole outpit
<freemangordon> *console
<Wizzup> freemangordon: it easily takes 2-3h
<Wizzup> still waiting on the solidrun server :(
<freemangordon> depmod is being run, so it is @ end
<Wizzup> great
elastic_dog has quit [Ping timeout: 240 seconds]
elastic_dog has joined #maemo-leste
elastic_dog has quit [Client Quit]
elastic_dog has joined #maemo-leste
<freemangordon> hmm, now it doesn;t hit more than 56 fps with 2-buffer
<freemangordon> weird
<freemangordon> well, ok, will reenable it by default and will fix one more issue
<Wizzup> great
<freemangordon> tmlind: testing a fix for xorg error messages you were seeing, will let you know when it hits the repo
<freemangordon> non-fullscreen, landscape, glmark2 Score: 56
<Wizzup> with h-d running?
<freemangordon> yes
<Wizzup> not bad :)
<freemangordon> gears run with 80fps
<freemangordon> this is vsynced
<Wizzup> is that max screen refresh or something?
<Wizzup> righgt
<freemangordon> yes
<freemangordon> even in tasknav small window ;)
<Wizzup> :D
<freemangordon> Wizzup: it is in the repo, enjoy and report issues :)
* Wizzup updates
inky has quit [Ping timeout: 250 seconds]
<Wizzup> freemangordon: quite smooth indeed
inky has joined #maemo-leste
amk has quit [Read error: Connection reset by peer]
amk has joined #maemo-leste
uvos has joined #maemo-leste
<Wizzup> I guess I should brush off the pinetab as well once we have the other gfx bug fixed
Twig has quit [Remote host closed the connection]
uvos has quit [Ping timeout: 240 seconds]
_inky has joined #maemo-leste