libera/#maemo-leste/ Saturday, 2024-01-20

uvosWizzup: its a regmap00:12
uvosso theres a file in debugfs for it00:12
uvosnot sure the exact path00:12
Wizzuphi00:12
Wizzupok, let me see00:12
uvosmight be /sys/debug/regmap even00:12
Wizzupmeanwhile the android ones I uploaded00:12
Wizzupthere is /sys/kernel/debug/regmap/00:15
Wizzup# ls00:19
Wizzup0-0038  4806a000.serial:modem:audio-codec@2  dummy-scm_conf@4a00200000:19
Wizzup1-0044  dummy-omap4_padconf_global@4a1005a0  spi0.000:19
uvosspi0.0 is cpcap00:19
uvosnot sure why the name is so wierd00:20
uvosi gues thats the host side of the bus?00:20
Wizzuproot@devuan-droid3:/sys/kernel/debug/regmap/spi0.0# cat name00:20
Wizzupcpcap-core00:20
Wizzupright00:20
Wizzupok, I can get the regs on serial, so shall I just them from mainline with screen on (and serial connected, but not usb)?00:21
uvosas nutch of the  same state as android as possible ofc00:21
uvossince we are trying to make the diff as small as possible00:21
Wizzupright00:21
Wizzupthe files I linked on my website have some pretty clear diffs00:21
Wizzupbetween the diff frequencies00:22
uvossure, but ideally we would expect no diff between android and mainline, besides the rtc00:22
uvosand the audio section is tricky00:22
Wizzupwhat I mean is that maybe the android regs can tell us which mainlines regs to look at00:23
Wizzupbut then again I have no idea what I am doing :)00:23
uvoswhat im looking for is mostly the possiblity of configureing a regulator wrong00:23
Wizzuphttps://wizzup.org/dirlist/maemo-leste/droid3/mainline-cpcap-regs.txt00:24
Wizzupdo you also want the emif regs?00:45
Wizzupuvos__: do you have the droid3 signal map as well, or is that https://uvos.xyz/maserati/stockinfo/signalmaps/xt860.txt10:55
WizzupI saw the dts for xt862 but presumably x860 and xt862 'the same' or similar enough10:56
Wizzupalthough the xt860 might not have usb modem10:57
arno11freemangordon: you mean adding dh_installxsession in libcmtspeechdata rules (and xsession file) like pulseaudio in maemo-audio ?10:59
arno11btw i tried to add a xsession file for cmt_pulse by hand and got a blackscreen lol11:00
Wizzupwhat did you add as contents11:01
arno11just /usr/bin/cmt_pulse11:02
Wizzupdid you look at any other xsession files?11:03
WizzupI'm pretty sure that whatever the script does, it should return to allow the next script to run11:04
Wizzupso in the very /least/ you need /usr/bin/cmt_pulse &11:04
Wizzup(and probably #!/bin/bash too)11:04
arno11(yes ofc i looked at other scripts)11:04
Wizzupor ues dsme to start it with will also return11:04
arno11for #!/bin/bash: yes ofc, xsession scripts still use /bin/sh BTW11:08
Wizzupsh is fine11:12
Wizzupdid you check if you backgrounded the task as I mentioned?11:13
arno11let me try again ;)11:13
arno11seems to work with background (need time to load h-d and check)11:18
arno11it works fine :)11:26
arno11so we have just to add dh_install stuff in libcmtspeechdata and we'll have calls OOTB11:27
arno11btw the alerting tone disappeared again11:27
freemangordonarno11: as Wizzup said, look at other xsession files11:29
freemangordonsec, will give you example11:29
arno11already done, why exactly ?11:29
arno11ok11:29
freemangordonhttps://github.com/maemo-leste/connui-common/blob/master/debian/connui-conndlgs.xsession11:30
freemangordonalready done what?11:30
arno11already checked other xsession files11:30
freemangordonok, what dsme parameters you pass?11:31
freemangordonalso, do you install in .post?11:31
arno11ah ok, misunderstanding11:31
freemangordonWizzup: what do you think, where xsession file shall be installed? in .d or in .post?11:32
arno11it works with a basic xsession file with /usr/bin/cmt_pulse &11:32
arno11i didn't try with dsmetool11:32
freemangordonarno11: cool, but this is a system critical daemon that shall be restarted on crash11:32
freemangordonthat's why dsmetool11:32
arno11ok makes sense11:33
freemangordonor, we may decide to reboot the device is cmt_pusle crashes, etc11:33
freemangordonalso, how do you install the script? dh_installzsession?11:33
freemangordondh_installxsession?11:33
arno11no, i just created a file in xsession.d11:34
arno11to test11:34
freemangordonok, I was under the impression you are tryint to fix the package11:35
arno11no lol11:35
freemangordonok, but that shall be done by someone that can test it11:36
freemangordondo you mind to do a PR for a proper xsession fix? after testing ofc11:37
freemangordonotherwise we are more or less stuck, as I don;t have another SIM to put in n90011:37
freemangordonunless sicelo  volunteers for the PR :)11:37
arno11yes sure, no probs, i modified and rebuild libcmtspeechdata hundreds of times lol11:38
freemangordoncoo11:38
freemangordonl11:38
freemangordonadding xsession support is very simple, no worries11:38
freemangordonsee https://github.com/maemo-leste/connui-common/blob/master/debian/rules as example11:38
freemangordonyou also need to add control dependency11:39
arno11yes ok11:39
freemangordonmaemo-system-services-dev, iirc11:39
freemangordonand proper xsession file in /debian11:40
freemangordonuse connui-common as example11:40
arno11ok11:40
freemangordonjust change post to pre (iirc) here https://github.com/maemo-leste/connui-common/blob/master/debian/rules#L1111:40
freemangordonbecause we want daemon started before h-d, IIUC11:41
arno11if it starts after, that's ok too11:41
freemangordonup to you11:42
arno11i think i must try both11:42
freemangordonbut then you won;t hear any sound if a call comes11:42
freemangordonalso, with dsmetool you can set nice value11:42
freemangordonsee /usr/sbin/dsmetool -h11:43
freemangordonhmm...11:43
arno11ok11:43
arno11why no sound ?11:43
freemangordonbecause daemon is still not running :)11:44
freemangordonI wonder if we can teach dsme to alter scheduling priority as well11:44
arno11interesting indeed11:45
freemangordoninstead of doing whatever sudoers hacks we were planning11:45
freemangordonbut that will not fix the issue with PA process11:45
freemangordonas it is not dsmetool started11:45
freemangordonhave to run, wish you luck :)11:45
arno11thanks :) i'll try a bit later and let you know (kids time for me)11:46
Wizzupuvos__: so I will double check if I am setting the freq correct, by logging to system, and then also try the latest 6.6 kernel with dts forward ported11:51
Wizzupfreemangordon: I don't know @ .d or .post11:51
sicelono need to reboot device on cmt_pulse crash11:58
freemangordonsicelo: that was just a theory :)12:00
freemangordonbut we shall restart it12:00
freemangordonalso, what will happen if ofono gets restarted?12:00
siceloit should be able to keep running. there's nothing it needs in ofono besides knowing when ofono's AudioSettings interface changes to Active status12:05
Wizzupsicelo: not reboot, but restart12:06
Wizzup11:45 < freemangordon> I wonder if we can teach dsme to alter scheduling priority as well13:25
Wizzupyou could just ship a script start-cmt-pulse.sh that does all this13:25
Wizzupand then dsme just runs this script13:25
WizzupI think13:25
Wizzuptmlind: so uvos has been trying to help me figure out why the droid3 seems to reset (frequently) under load, I just wanted to check if you had some additional ideas13:26
Wizzupcurrently I'm making sure that on the first kexec call the freq is set to max (1ghz), and I think this is already the case, but just in case I will verify13:27
Wizzupthen next I made cpcap register dump at each of the frequencies in android, and also one on leste, to see if there are any regs that are wrong13:27
Wizzupbut I am having a hard time interpreting *what* these cpcap regs are, there is a clear diff between the freqs on android13:28
WizzupI suppose I can make a few more dumps on android in the frequencies and see if there are regs that change in between say 300Mhz attempt 1 and 2, so that I can eliminate further certain regs that don't matter13:28
Wizzupbut other than this I am kind of stuck13:28
WizzupI suppose I could prevent say pvr from loading in case the gpu clock speed is also too high13:29
WizzupWhat seems to happen is that the device just hangs, watchdog realises this and then resets:13:33
Wizzuproot@devuan-droid3:~#13:33
Wizzup-- OMAP 00004430 (version 00000b22) PPA release1.3.5 R213:33
WizzupReset reason = 000379a213:33
WizzupModel ID is 0x0000000313:33
WizzupPPA hash Block:0x9ff00000 Size:260096 Flag:313:33
Wizzupuvos__: I confirmed that the frequency is 1000000 at the time of kexec13:46
Wizzup/system/logs/maemo-freq.txt contains:13:46
Wizzup100000013:46
arno11freemangordon: sicelo: Wizzup: ok, we have calls on N900 OOTB :)14:11
arno11it works, adding xsession/dsme stuff in libcmtspeechdata14:11
sicelogreat. tyvm14:12
sicelodo we have the sphone landscape thing in place ootb too?14:12
arno11nope, still need to modify sphone.ini by hand14:13
Wizzupcan't we set a gconf key?14:14
arno11don't no but probably14:15
arno11and BTW we don't need chrt stuff for cmt_pulse, we just need it for sphone and PA14:15
sicelomaybe that should go in as well (landscape thing). would be unfortunate to find your screen dead14:15
arno11true14:16
Wizzupif there is sphone.ini.d or a gconf key we can manage it with leste-config-n90014:16
WizzupI updated hildon-meta, leste-config and mapphone-kexecboot-config with support for xt910 and xt912 and I split out the config and meta packages for them in case we need to diverge at some point14:17
Wizzupthere is /usr/share/sphone/sphone.ini.d14:18
Wizzuparno11: what change to do you make to sphone.ini, can you share?14:18
Wizzupthen I will update leste-config-n900 now14:19
arno11i was looking for the same thing :) ok let me few sec14:20
arno11you just need to add LandscapeCall=114:21
arno11in Gui14:22
Wizzupso14:22
Wizzup[Gui]14:22
arno11yes14:22
WizzupLandscapeCall=114:22
arno11yes14:22
Wizzupok one sec14:22
arno11cool :)14:22
Wizzupbuilding new leste-config14:24
arno11:)14:24
Wizzupin a few minutes, please apt update and apt upgrade, assuming you're on leste-devel, and then check /usr/share/sphone/sphone.ini.d/landscape-call.ini14:25
Wizzupand then you can remove your change to /usr/share/sphone/sphone.ini and then see if it still works?14:25
arno11ok, yes ofc14:25
Wizzupready to update14:28
Wizzupuvos__: static const struct dsic_panel_data razr_xt9xx_data's width_mm and height_mm doesn't match the xt910-xt912.dtsi width-mm and height-mm14:31
WizzupI doubt this makes a difference (will check, probably just for dpi)14:31
Wizzupyeah looks like it14:31
siceloarno11: you made PR for libcmtspeechdata? so Wizzup can rebuild that while he's here :-)14:31
Wizzupsicelo: I'm almost always here :D14:32
sicelo😃 I'll also love to test (in about 3 hours). would be nice to just apt get14:35
Wizzupuvos__: dispc_timing_hsw from the xt912dts does seem to match the hsync-len <2> in mainline dts14:36
arno11sicelo: Wizzup: i can make a PR + sphone.ini test in 30-45 min (kids around so not so easy for me)14:39
siceloah, no rush :-)14:40
Wizzuptmlind: it looks like panel-dsi-cm had a commit from you to support x_offset (drm/panel: panel-dsi-cm: Add update window offset), but I don't see that actually being used anywhere in the subsequent commit that adds support for xt91014:43
Wizzuptmlind: nevermind I am wrong, it is used14:44
Wizzupuvos__: so page 2085 of the omap4430 trm starts to list the dss regs, is this what you meant?15:20
Wizzupuvos__: rwmem just always gives me bus error on mainline, even on addrs that apparently worked for folks here according to the irc log15:49
arno11Wizzup: i did a dist-upgrade with very last stuff and now N900 refuses to shutdown but reboot instead...in less than 25 sec !!15:50
Wizzupokay, I give up for now, I'm going to use my time in a more effective way than this driver stuff15:50
Wizzuparno11: I don't think I changed anything special15:50
arno11maybe last fmg stuff with weird shutdown15:52
arno11anyway we are not far to solve the slow shutdown imo15:55
arno11wow and sphone crashes with immediate reboot (ofc not related with previous reboot)15:57
arno11Wizzup: so ATM i'm not able to test sphone.ini stuff15:58
Wizzupmaybe it is not happy with the config file16:00
Wizzupi'll try it on my n90016:00
arno11i'll remove sphone.ini.d to see if sphone continue to crash16:00
arno11ok16:00
Wizzupyes please do try that16:00
arno11yup16:00
arno11sphone.ini.d seems to be the problem, currently rebooting to test16:04
arno11yes sphone is not happy with the config file indeed16:12
arno11and the fast reboot was due to sphone.ini.d as well16:13
arno11i'll make the PR for cmt_pulse now (it works fine)16:13
siceloLandscapeCall=1 ... shouldn't that be LandscapeCalls maybe? (plural)?16:16
sicelootherwise, i don't see why it would crash sphone, or cause reboots16:16
WizzupI will check the src and debug if it crashes for me16:18
arno11sicelo: oh yes16:20
arno11you're right16:20
arno11LandscapeCalls=116:20
Wizzuplet's hope it doesn't crash because of this16:20
siceloi doubt the crash is due to it.  in fact, it's not :-)16:21
Wizzuphow do you know?16:21
Wizzupso sphone does not crash for me16:30
Wizzupregardless of the key name16:31
Wizzupsphone: sphone-conf: Could not open config overide dir /home/user/.config/sphone/16:31
Wizzupsphone: sphone-conf: found conf file 0: sphone.ini16:31
Wizzupsphone: sphone-conf: found conf file 1: landscape-call.ini16:31
Wizzupit does load it16:31
sicelo https://github.com/maemo-leste/sphone/blob/e4f6af0d4d744f189ea0382846a6c1d9789c112e/src/modules/gui/gtk2/ui-calls-manager-gtk.c#L445 is where the decision is made, based on https://github.com/maemo-leste/sphone/blob/master/src/utils/sphone-conf.c#L80  ... this just feeds a simple ternary operator/condition. no way it causes crashing16:33
sicelothere might have been something else at play for the observed crash16:33
Wizzupyeah16:35
WizzupI changed it to calls (plural) and then rebooted, and it seems to boot fine16:39
arno11Wizzup: cool, and if you shutdown the device ?16:45
arno11the cmt_pulse PR: https://github.com/maemo-leste/libcmtspeechdata/pull/516:45
Wizzupshutdown with ui or cmdline16:48
arno11with ui16:48
Wizzupwill try now16:48
arno11ok16:48
Wizzuparno11: yes shutdown works fine for me16:50
Wizzuparno11: so the "&" is not necessary when you use dsme16:51
WizzupI'll adjust the dsme flags a bit16:51
arno11ok16:53
arno11rebooting to test call16:56
arno11with sphone.ini.d16:57
arno11Wizzup: wow it works (call) then the phone crashes17:03
arno11working fine without sphone.ini.d, weird17:04
arno11Wizzup: i have to go, let me know when libcmtspeechdata is ready for upgrade17:06
arno11ttyl17:06
tsesaniI posted to the mailing list about building raspi4 images but no response. Also have been chatting in gemini://bbs.geminispace.org/s/maemo. I also released 2005 2006 2007 original code at https://github.com/tsesani/Maemo20:18
uvosWizzup: no idea whats wrong with rwram, but the kernel people where discussing adding more restricitons to /dev/mem20:20
Wizzuptsesani: I did not see that email, I will respond when I get back20:20
uvosso probubly that20:20
uvosWizzup: for the cpcap regs20:20
tsesaniRunning in virtual machine on Devuan 5 OK with X core every once in awhile. Nice work to all.20:21
uvosdiff the state between the mainline kernel and the android kernel at the same oop20:21
uvostheres a cpcap header with the register names, they are fairly inteligable20:21
uvosuse those to narrow  different registers down20:21
uvosreally we are most interested in regulators being different20:22
uvosbionic has some chaneges in what regs are used for what and we just assumed d3 is the same20:22
uvosso thats a good first step20:22
uvosmaybe check sgx clock too, could be that we are running it to fast20:22
uvoswe clocked sgx up on the mapphones relative to spec because motorola also did that on d4/bionic20:23
uvosbut maybe they dident on d320:23
uvosbeyond that spme perifferals are different too between d3 and bionic20:24
uvosso maybe some periferal driver is missbehavig20:24
uvosmight make sense to create a dts with everything non essental removed and see if its still unstable20:24
uvosbeyond that the d3 omap runns mutch older microcode that might have some additional errata fixed later, but this gets really outside of my capabilites20:26
uvoshavent had a time to look at the dumps but oh and you might have to redo them20:27
uvosbecasue we forgot to also fix the sgx opp20:27
uvosandroid is mutch more argessive with power manageing the sgx so its probubly in a lower power state20:28
Wizzupdo you know how to fix the sgx opp?20:37
Wizzup20:28 < uvos> becasue we forgot to also fix the sgx opp21:13
Wizzupdo we also need to do this before kexec?21:13
Wizzupah now I see the email on the ML21:22
uvosno21:54
Wizzupuvos: regarding setting it high before kexec? I figured21:55
Wizzupstill not sure how to set the sgx opp in android for the comparison test though21:56
Wizzupregarding rwmem, so I was trying to get the dss regs on mainline on the razr, and I just kept gettinb bus error21:56
Wizzup/dev/mem did exist21:56
Wizzupit also triggeed a kernel oops every time21:56
Wizzupuvos: regarding razr, I also tried some futile things like setting hsync-active to 1, same for vsync-active, didn't help22:01
Wizzupso:22:03
Wizzuproot@devuan-xt912:~# ./rwmem 0x5800000022:03
WizzupBus error22:03
Wizzuphttps://bpa.st/2JVA22:04
Wizzupit works OK on 6.122:04
Wizzupnot on 6.6.022:04
WizzupI guess I will go back to 6.1 on razr for now so I can read the dss regs22:06
Wizzupuvos: heh no, so I also get the bus error on 6.1 on razr, but not on the d422:11
Wizzupfacinating22:12
Wizzuphm..22:14
Wizzupno, ok22:15
Wizzupso the bus error happens when screen is off22:15
WizzupI guess that makes sense22:15
uvosnot sure about sgx oop in android22:32
uvosmaybe just load it22:32
uvosi think i ran glmark on d4 when doing this for it22:33
Wizzupdoing it for bionic?22:33
uvosno d422:33
Wizzupand then wher do you read the clock?22:33
uvosi was figureing out why mainline sgx was underperforming22:33
uvosanyhow on d3 this might be harder22:34
uvossince d4 can run android 7, which is still essentally mostly compatable with modern android applications22:34
uvos2.3 is decidedly not22:34
uvosso you would have to find something compiled agains the period correct sdk for it to run22:35
Wizzupcan we just clock it way lower in the dts and see if that is stable?22:39
WizzupI mean honestly I agree with your earlier statement that a more minimal dts with (maybe) a lot of things set to 'safe' would be a good way to test stability22:39
Wizzuplike maybe even a dts that just doesn't exceed 300Mhz and has some much lower sgx clock even22:39
uvoswe set the opp low already22:45
uvosthis dident help22:45
uvosso i dont see why doing it in the dts would do anything22:46
WizzupI don't remember doing this, but seems like your memory is better22:46
uvoswell i did it myself22:46
uvosthat was like first thing22:46
Wizzupon droid3? ok22:46
uvosyes22:46
uvosanyhow yes minimal dts would be good22:46
WizzupI'm wondering if there is just some things we've missed/forgot, like not setting freq to 1000Mhz before kexec22:46
uvostheres not mutch to forget really22:47
uvossince its just ctrl-c ctrl-v the bionic22:47
uvosthe bionic (in difference to d4) dosent seam to care about the opp at boot either it seams22:47
uvossince it was apaeranlty always missing22:47
WizzupI mean clearly there is a problem since it is not ctrl-c ctrl-v :D22:51
WizzupI understand it is for the most part22:52
Wizzupcan't we read the allowed clocks from the kernel for the device, or the devtree for the device?22:52
Wizzupfor say sgx22:52
WizzupI just feel like maybe we took a shortcut too many or something22:53
Wizzupokay, so to recap, I will get 6.6 on it just for the heck of it and because it is easier to then make changes22:56
Wizzupdoes sgx clock show up in cpcap regs?22:56
Wizzupor I guess in some regulator like you said22:56
Wizzuphrm this xt912 lets me flash 4.1.2 fine but I am having trouble flashing older fw23:01
Wizzupuvos: ok so I'm looking at razr dss regs atm because I'm a little frustrated with the d3 stuff (might try again tomorrow), and in leste I can now read the regs, but on android rwmem won't work:23:27
Wizzuproot@cdma_spyder:/data/maemo # ./rwmem23:27
WizzupFATAL: kernel too old23:27
WizzupAborted23:27
WizzupI guess maybe busybox devmem can be used23:37
Wizzupnope, that gives bus errors even with the screen on23:39

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