<norayr> which driver to install? on droid?
Keeblo has joined #maemo-leste
Keeblo has quit [Remote host closed the connection]
Daanct12 has joined #maemo-leste
Livio has quit [Ping timeout: 252 seconds]
pere has quit [Ping timeout: 250 seconds]
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #maemo-leste
Daanct12 has quit [Quit: Leaving]
joerg has quit [Ping timeout: 246 seconds]
joerg has joined #maemo-leste
pere has joined #maemo-leste
macros_2ndPC has quit [Ping timeout: 260 seconds]
macros_2ndPC has joined #maemo-leste
lyubov has quit [Quit: WeeChat 3.0]
<freemangordon> uvos: try with higher res, this https://archive.org/download/BigBuckBunny/big_buck_bunny_480p_h264.mov for example
<freemangordon> norayr: just upgrade
mardy has joined #maemo-leste
<freemangordon> uvos: hmm, even with your example I see 30% vs 100% (x11 vs xv)
<freemangordon> keep in mind mpv will use xv by default, so you must specify -vo x11 to test without xv
<freemangordon> oh, it seems mpv uses 'gpu' by default
<freemangordon> well, we are comparing gles vs gles :)
<freemangordon> uvos: compare mpv big_buck_bunny_480p_h264.mov -vo gpu vs mpv big_buck_bunny_480p_h264.mov -vo xv
<freemangordon> I wonder why mpv struggles to play that, nor mplayer neither gstreamer have issues with it
ceene has joined #maemo-leste
<freemangordon> oh, ok, it seems tmlind's patch is needed after all
<freemangordon> or not?
<freemangordon> wait, what? https://www.ti.com/tool/C64XPLUSCODECS
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
<freemangordon> uvos: mpv somehow succeeds to break gpu playback
<freemangordon> after several attempts, fullscreen xv renders with 2 fps, but that happens only after mpv was used
<freemangordon> also, sometimes when mpv is switched to fullscreen, with gpu vo, the video is misrendered (it looks like wrong pitch is assumed)
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
<freemangordon> ok, no idea what mpv is doing, but it uses 30-40% more CPU than mplayer, no matter xv or gpu vo
<freemangordon> mplayer with xv is capable of playing even big_buck_bunny_720p_h264.mov with just a few frames dropped
pere has quit [Ping timeout: 260 seconds]
pere has joined #maemo-leste
xmn has quit [Read error: Connection reset by peer]
xmn has joined #maemo-leste
akossh has joined #maemo-leste
<uvos> freemangordon: iths was -vo vs -vo gpu
<uvos> so xv is accellerated via gles in your ddx?
xmn has quit [Ping timeout: 260 seconds]
_uvos_ has joined #maemo-leste
<_uvos_> ofc -vo x11 is mutch slower
_uvos_ has quit [Ping timeout: 246 seconds]
<freemangordon> uvos: well, it is not gles, but through gpu
<freemangordon> basically bot end up in shaders
<freemangordon> *both
<freemangordon> I guess IMG/TI shaders are better optimized than generic ones in mpv
norayr has left #maemo-leste [Error from remote client]
<freemangordon> uvos: as I said, compare xv vs gpu on big_buck_bunny_480p_h264.mov
<freemangordon> with gpu it drops frames like crazy
mglbg[m] has quit [Quit: You have been kicked for being idle]
norayr has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
<uvos> ok
<uvos> i dont really see why -vo gpu must be slower, but no matter
<uvos> anyhow did you see the ofono logs?
<freemangordon> no, will look at them later
<uvos> ok
<uvos> speaking of gpu acceleration, a gpu accelerated browser would be pretty rad, qwebengine gets petty close it seams, it just renders black with gles enabled (try qtwebbrowser -platform xcb)
akossh has quit [Read error: Connection reset by peer]
norayr has left #maemo-leste [Disconnected: Replaced by new connection]
norayr has joined #maemo-leste
<freemangordon> uvos: most-probably -vo gpu uses shader that is not optimized, while -vo xv uses either very optimized shader or specialized video processing HW/instructions in the GPU
<buZz> uvos: chromium seems hw accelerated
<buZz> or its just magically very fast
<freemangordon> it is not
<buZz> the latter then :D
<freemangordon> yes, it is fast, but not HW accelerated
<freemangordon> it does not support gles2 AFAIK
<uvos> i think it was dropped
<uvos> but in deb 10 it probubly still dose
<buZz> probably does upstream but devuan/debian prefers to not compile it? :)
<uvos> anyhow its not hw accelerated
<freemangordon> :nod:
<uvos> but yeah both ff and chomeium do fairly well with sw rendering
<uvos> to my suprise
<freemangordon> I hope this will get better when I accelerate compositing
<buZz> what changes about battery calibration btw? i cant seem to get it back
<buZz> changed*
<freemangordon> this will release more CPU for them to render
<uvos> freemangordon: well without hildon it is faster still yes
<uvos> everything is
<buZz> not debugging maemo or hildon issues, uvos :)
<freemangordon> yeah, but once we have aHW compositing, the difference should become minimal
<uvos> right
<uvos> that was my point hw composting should help
<uvos> since no compositing dose
<freemangordon> XV was a general rehearsal for that
<freemangordon> because it uses SGXQueryTransfer function, that is not part of the public API
<freemangordon> and I had to RE a pile of structures
<freemangordon> good news is that some of TI SGX SDKs come with debug symbols
<uvos> [4461:4483:1003/114142.601287:ERROR:gles2_cmd_decoder.cc(2603)] [.RenderWorker-0x5e8f08]GL ERROR :GL_INVALID_OPERATION : ScopedTextureBinder::dtor: <- error from previous GL command
<buZz> weird, my /var/lib/droid4-battery-calibration/charge_full is just empty :(
<freemangordon> so it is not *that* hard
<uvos> thats what qwebengine fails at btw
<uvos> probubly assumes an extension we dont have
<freemangordon> yeah
<freemangordon> uvos: btw mpv crashes GPU with 720p bunny
<uvos> buZz: we delete it if the battery goes below -20% full
<freemangordon> and I am sure the issue is with mpv
<uvos> or above 120% full
<uvos> that can happen for various reasons
<uvos> one being that your spike triggers low prematurely
<uvos> and then you discharge further untill the battery is way below "low"
<uvos> the logic is there because we have no idea when the user inserts a new battery, so the values are sanity checked
<buZz> uvos: this changed recently?
<uvos> no
<buZz> weird, never seen before
<uvos> i added this to the kernel >1 year ago
akossh has joined #maemo-leste
<buZz> feels pretty unfriendly
<uvos> no, why should the kernel keep callibration thats for sure totaly wrong?
<buZz> seems the only user that ever swaps batteries around is you :P
<buZz> lol, i put "1000000" into 'charge_full' with a 40% full battery, poweroff through hildon, poweron, boom, uncalibrated , var/lib/droid4-bat-cal/charge_full -again- empty :D
<uvos> where are you putting the value?
<buZz> lol where do you think :P
<uvos> idk
<uvos> changeing var/lib/droid4-bat-cal/charge_full has no effect
<freemangordon> there is a file in /usr/share
<freemangordon> does it not?
<uvos> no
<freemangordon> if you stop the service?
<uvos> then sure
<freemangordon> well...
<uvos> but the right way is tell the kenrel
<uvos> by putting the value into the file in sys
<freemangordon> ah
<uvos> the value from the kernel then gets saved as normal
<buZz> uvos: i changed /sys/class/power_supply/battery/charge_full obviously
<uvos> on shutdown
<uvos> the shtudown also needs to be clean ofc
<buZz> and the init script didnt save it
<uvos> thats wierd
<buZz> it was a clean shutdown, battery is ~40%
<uvos> the script is failing on your system then
<uvos> for some reason
<uvos> try running it by hand
<uvos> check serial output on shutdown
<buZz> hence me asking what changed
<uvos> nothing
<uvos> all of this is very old
<buZz> ah, it didnt get started
<buZz> 'cat write error invalid argument' on starting, great
<uvos> thats normal
<uvos> if you have no var/lib/droid4-bat-cal/charge_full
<buZz> its preventing the init script to execute
<uvos> right there should be a ignored return value there
<buZz> thus not able to -stop- the init script later
<uvos> the install sctipt touches var/lib/droid4-bat-cal/charge_full
<uvos> so its not really a problem
<buZz> thats wrong then
<buZz> as the emptystring inside prevents the init script from working
<uvos> ok
norayr has left #maemo-leste [Error from remote client]
<buZz> alright, putting "1000000" into /var/lib/droid4-bat-cal/cha-fu and starting/stopping the script works
<uvos> buZz: if its missing could you add || true
<buZz> its?
<freemangordon> buZz: please make a PR for that too
<uvos> the return value of the cat line on startup should be ignored
<uvos> if its not
<buZz> the file was there, it was empty , leading to the 'cat' failing and the whole init script stopping
<uvos> please add it
<uvos> just looked at the script
<buZz> but that wont help
<uvos> yeah no touch
<uvos> it checks if charge_full exits
<buZz> it doesnt check if there's a valid input
<uvos> but the saveing on shtudown dose
<buZz> it just blindly stores it
<uvos> so there should be no possiblity of it being emtpy
<uvos> unless you mess with the file
<buZz> beside the method you said that deletes the value
<uvos> no
<buZz> when battery is 20% full ?
<uvos> thats the kernel
<buZz> what did you mean by that then
<uvos> the kernel deletes its internal value
<uvos> reading the value then gives an empty file in sys
<buZz> which gets copied as new calibration on line 21
<uvos> wich the script handels
<uvos> and dosent just save
<buZz> it doesnt ?
<buZz> it does save, there's no check
<uvos> if [ $? -ne 0 ]; then
<buZz> thats the errorlevel of cat
<uvos> rm -f /var/lib/droid4-battery-calibration/charge_full
<uvos> i know
<uvos> the read on the kernel fails
<uvos> with ENODATA
<buZz> not the contents of sys/class/power_supply/battery/charge_full
<uvos> yes but if the kernel delete the value
<uvos> the read fails
<buZz> i think you're overestimating what cat file > otherfile will do :P
<uvos> well idk what cat is supposed to do if read() returns !=1
<uvos> *0
<uvos> surely not return 0
<uvos> anyhow still adding || true to the cat is a good idea
<uvos> since the user might mess with the file
<buZz> alright
<buZz> wont that then -never- hit $? -ne 0 ?
<uvos> no why
<uvos> if the kernel has no value
<buZz> because it would always be true
<uvos> that will still be hit
<buZz> ok
<uvos> your adding || true to the restore cat
<uvos> not the save cat
<uvos> the check is on save
<uvos> ah wait
<uvos> no i see the problem
<uvos> the script exits at line 21
<uvos> if the kernel cant give a value
<uvos> on save
<buZz> exactly
<uvos> thats how you end up with a emtpy file
<uvos> sorry im slow
<uvos> yeah
<uvos> ok
<uvos> this is a real problem
<buZz> \o yay
<buZz> :P
<uvos> um dose /sbin/openrc-run support the option to ingore all return values?
<buZz> why are we using cat anyway, why not just read the file into a var, check the var, and then output it?
<uvos> it grew that way since it was just a cat at first
<uvos> and nothing else
<uvos> but yeah
<buZz> i think we can afford the couple clockcycles :P
norayr has joined #maemo-leste
<buZz> oh, -20% , not 20%
elastic_dog has quit [Ping timeout: 244 seconds]
elastic_dog has joined #maemo-leste
alex1216 has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
alex1216 has quit [Ping timeout: 252 seconds]
<buZz> wait, is 'sudo poweroff' perhaps a 'non-decent shutdown' vs hildon's 'switch off' button ?
<buZz> or 'sudo reboot' ?
<uvos> no
<uvos> but untill recently d4 would crash often on shutdown
alex1216 has joined #maemo-leste
<buZz> hmm ok, but 'hildon menu -> switch off' takes quite a long time, vs 'sudo reboot' or 'sudo poweroff'
<buZz> always felt to me that it was doing something special
<uvos> not really
<uvos> the difference is jus a dbus signal
<freemangordon> that's the issue that was fixed recently
<buZz> ah, nice freemangordon !
<freemangordon> with serial oopsing on shutdown
<uvos> freemangordon: im not sure its fixed
<buZz> or which issue do you mean, the time difference?
<buZz> oh ok
<uvos> freemangordon: im mean thats fixed
<uvos> freemangordon: but my device sill hanged yesterday during shutdown
<freemangordon> yes, but that's another issue I think
<uvos> right
<uvos> but buZz might be encountering this
<buZz> not sure, it seems to shutdown totally fine, just takes longer
<buZz> would that be the symptom?
<uvos> a hang
<uvos> im pretty sure its permanent or at least very long
<buZz> lemme try measuring the difference i'm seeing
ceene has quit [Remote host closed the connection]
<buZz> 'sudo poweroff' = 49 seconds
<buZz> *booting back up* :)
<uvos> sounds way to long for a regular shutdown
<uvos> something is delaying at the least
<uvos> maybe shutdown with serial attached
<buZz> this was just with a usb charger attached (and usb doctor so i can see when shutdown finishes)
<buZz> i still havent made 'the' serial cable yet
<buZz> but no doubt something could be delaying it
<buZz> ah, almost booted back up
<buZz> btw , 49 seconds for a poweroff doesnt feel that bad to me
<uvos> well debian shutsdown in like 5sec
<uvos> leste dose take a bit longer
<buZz> oh sure, if you just kill -9 all processes?
<uvos> but not nearly a minute here
<uvos> buZz: ?
<uvos> just a regular shutdown
<buZz> well, normally you run services on a debian?
<uvos> yes
<buZz> and shutdown would let those services shutoff?
<uvos> yes
<uvos> its regular systemd shutdown
<uvos> it wait
<uvos> s
<buZz> systemd? :D
<buZz> i dont think 5 seconds is realistic for even shutting down hildon
<uvos> systemd is mutch faster at everyting ofc
<uvos> than openrc
<buZz> yes, thats why its 2M lines of code
<uvos> due to the hevy usage of scripts
<freemangordon> well, we have parallel boot disabled
<uvos> buZz: thats irrelivant
<freemangordon> we can enable it
<freemangordon> and it will be faster
<uvos> the thing is that systemd implements everything in c
<buZz> either way, lets see how long 'hildon switchoff' takes, that was my point
<uvos> that is implemented in shell in openrc
<buZz> not rust?
<uvos> so it just has an advantage there wrt speed
xmn has joined #maemo-leste
<buZz> or C#?
<uvos> this is mindless systemd hate
<uvos> if you want to critisize systemd pick something real
<uvos> there are real issues
<uvos> anyhow
<uvos> i was just descibing one reason why debian might be faster than leste
<buZz> ? i wasnt talking about systemd , you were
<buZz> either way, hildon switchoff takes exactly as long as sudo poweroff :) either it was the serial issue, or something else
<uvos> not suppising
<buZz> tnx for letting me measure
<uvos> the only difference is hildon power off signals mce to turn of the display
<uvos> (and changes dsme state)
<uvos> (but i dont think this has a real effect)
<buZz> the dsme state? yeah no clue
pere has quit [Ping timeout: 252 seconds]
<buZz> freemangordon: would parallel boot also do parallel shutdown?
<freemangordon> I guess so
norayr has left #maemo-leste [Disconnected: timeout during receiving]
norayr has joined #maemo-leste
norayr has left #maemo-leste [Disconnected: closed]
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
pere has joined #maemo-leste
norayr has joined #maemo-leste
pere has quit [Ping timeout: 252 seconds]
alex1216 has quit [Quit: WeeChat 2.3]
Livio has joined #maemo-leste
Livio has joined #maemo-leste
Livio has quit [Changing host]
<freemangordon> ok, XV works over HDMI too :)
<Wizzup> sweet
<freemangordon> mhm
<freemangordon> I pushed 2 fixes recently, now it should be 100% stable
<uvos> plenty-o-work
<uvos> and the implementaion is bad
<uvos> (just over remoteproc vs real kernel driver)
<freemangordon> I already have (had) lots of experience with gst-dsp
<uvos> ok
<uvos> but rember its very different on omap4
<uvos> since the cpu can acess the dsp at all
<uvos> *cant
<freemangordon> the same on omap3
<freemangordon> but year, remoteproc is new to me
<freemangordon> *yeah
<uvos> on omap3 the dsp is connected to the main cpu cluster
<uvos> on omap4 its connected to the other cpu cluster
<uvos> ie the cortex m3 one
<uvos> that dosent exist on omap3
<uvos> you have to communicate with the fw on the m3 cluster to do anything with the dsp
<freemangordon> I see
<freemangordon> well, that makes it a bit harder I guess
<uvos> so all the code to do this is floating around
<uvos> the driver was once in stageing iirc
<uvos> but was removed
<freemangordon> which driver?
<freemangordon> tidspbridge?
<uvos> remoteproc bridge driver
<freemangordon> ah
<uvos> for ducati
<uvos> (the m3 cpu cluster)
<freemangordon> I dont; think DSP is something I will play with soon though
<freemangordon> we have too many other issues
<uvos> sure
<freemangordon> also, I think we would like to implement va-api if anythink
<freemangordon> *anything
<uvos> yes ofc
* freemangordon is about to try XV on n900 :)
Twig has joined #maemo-leste
<freemangordon> crashes there, most-probably difference in sgx structure
<freemangordon> yeah, sgx transfer structure is smaller there
Twig has quit [Ping timeout: 268 seconds]
pere has joined #maemo-leste
Twig has joined #maemo-leste
lyubov has joined #maemo-leste
lyubov has quit [Client Quit]
pere has quit [Ping timeout: 252 seconds]
xmn has quit [Ping timeout: 264 seconds]
mardy has quit [Quit: WeeChat 3.5]
<buZz> ah, nevermind, its not new enough :P
pere has joined #maemo-leste
Twig has quit [Ping timeout: 265 seconds]
<freemangordon> ok, now XV works on both d4 and n900 :)
<Wizzup> nice
<freemangordon> yep
<norayr> shell i update?
<freemangordon> tomorrow will try to find ofono bugs that uvos has reported and then will try to implement HW compositing
<freemangordon> norayr: yep, why not
Daanct12 has joined #maemo-leste
Danct12 has quit [Ping timeout: 246 seconds]
elastic_dog has quit [Ping timeout: 264 seconds]
elastic_dog has joined #maemo-leste
akossh has quit [Quit: Leaving.]
<buZz> xv seems to work well in mpv :)
uvos has quit [Ping timeout: 268 seconds]
enyc has quit [Ping timeout: 268 seconds]
enyc has joined #maemo-leste
<Wizzup> freemangordon: did you end up mailing nikolaus wrt sgx userspace builds?
Livio has quit [Ping timeout: 246 seconds]