uvos | the bug why hildon scrolling is Y2038 bug :P | 00:12 |
---|---|---|
uvos | *why hildon scrolling is terrible | 00:12 |
uvos | in the launcher | 00:12 |
uvos | it takes the time of the last 3 events adds them together and shoves that into a time_t and then devides | 00:13 |
uvos | to get the mean time | 00:13 |
uvos | that dident even work in 2010 | 00:14 |
lel | IMbackK opened a pull request: https://github.com/maemo-leste/hildon-desktop/pull/17 (fix time overflow bug in tidy-finger-scroll) | 00:25 |
uvos | nvm @2015 | 00:35 |
uvos | it broke Fri May 15 02:09:25 2015 UTC | 00:35 |
Wizzup | uvos: which scrolling is this? | 01:00 |
uvos | Wizzup: all scrolling in h-d | 01:02 |
uvos | most notably the launcher | 01:02 |
uvos | but also tasknav etc | 01:03 |
Wizzup | uvos: oh... | 01:04 |
Wizzup | that would be a great catch | 01:04 |
Wizzup | uvos: so it gets much more smooth this way? | 01:04 |
uvos | no, the bug is, in the launcher etc, scolling and lifiting your finger is supposed to cause it to continue scrolling untill it coasts to a stop. | 01:05 |
uvos | what happens in reality is it stops immidiatly | 01:05 |
Wizzup | ah | 01:05 |
uvos | this pr fixes that | 01:05 |
Wizzup | I've asked fmg to look, I think he's our h-d person | 01:06 |
Wizzup | meanwhile I need to figure out again why dist-upgrade doesn't work for me on experimental | 01:06 |
Wizzup | *sigh* | 01:06 |
Wizzup | I think I'll do that tomorrow | 01:06 |
Wizzup | good catch | 01:09 |
Wizzup | that's a funny one for the news post | 01:09 |
_inky | uvos: >but, but we like our strange, rare, near obsolete nokia/motorola devices | 01:29 |
_inky | me too, but those don't attract people and therefore developers. | 01:29 |
Wizzup | uvos: I guess this helps icm your signal map https://github.com/STS-Dev-Team/kernel_kexec_modules/blob/2.6.35-solana/arch/arm/mach-omap2/board-mapphone-modem.c#L81 | 02:10 |
tmlind_ | fyi, for folks interested in nokia n810 mainline kernel support, looks like there is now a git tree with pending patches: | 05:56 |
tmlind_ | https://github.com/relghuar/linux-stable-nokia-tablets/commits/n810-5.15 | 05:57 |
sicelo | nice tmlind_ :-) | 07:47 |
sicelo | _inky: you're actually correct. mentioning those devices in most rooms nowadays elicits zero response | 07:48 |
freemangordon | tmlind_: we need someone to help with omapdrm | 08:09 |
freemangordon | or with drm in general | 08:10 |
freemangordon | I don;t know where the issue is, but according to specs drmModePageFlip should return immediately | 08:11 |
freemangordon | 6ms is not my understanding of "immediate" | 08:11 |
freemangordon | given that 'flush' time on d4 seems to be 12.5 ms, this delay limits max FPS to 54 | 08:13 |
freemangordon | which is exactly what we see with 3-buffer | 08:13 |
freemangordon | and it is even worse on n900 | 08:13 |
freemangordon | not to say that the tearing we see is a sign to a more general issue | 08:15 |
freemangordon | *sign of | 08:15 |
freemangordon | So, either framedone irq comes too early(so we request another flush while the previous on is still in progress), or flushing to panel should be done in a different way | 08:24 |
tmlind_ | freemangordon: is this also with d4 hdmi? | 08:32 |
freemangordon | tearing? | 08:40 |
freemangordon | have to test it | 08:40 |
freemangordon | will do, later on | 08:41 |
freemangordon | Wizzup: BTW, is there tearing with ddk 1.9? | 08:41 |
freemangordon | (sorry if you have already answered, I forgot) | 08:41 |
freemangordon | tmlind_: yes, there is tearing | 08:53 |
freemangordon | you imply that GPU is still rendering? | 08:54 |
tmlind_ | no just wondering if this might be limited to command mode lcd only | 08:59 |
freemangordon | doesn't seem to be | 09:00 |
tmlind_ | ok | 09:00 |
freemangordon | I am curious what Wizzup will report re ddk1.9, given he still keeps it | 09:00 |
freemangordon | hmm, wait | 09:01 |
* freemangordon checks something | 09:01 | |
freemangordon | flase alarm | 09:03 |
sicelo | iirc he said there is tearing in ddk 1.9 too | 09:06 |
freemangordon | :( | 09:10 |
freemangordon | so, unfortunately the issue is in omapdrm, not in pvr driver or ddx | 09:10 |
freemangordon | at least that's my understanding | 09:11 |
tmlind | freemangordon: so how much slower is the flip on n900 then? | 09:24 |
sicelo | https://libera.irclog.whitequark.org/maemo-leste/2021-11-30#31284618; | 09:32 |
uvos | freemangordon: added a comment to https://github.com/maemo-leste/hildon-desktop/pull/17 | 10:04 |
mighty17[m] | uvos: compiled omapconf, what cmd do you need? | 11:32 |
Wizzup | freemangordon: yes, 1.9 has tearing in portrait | 11:33 |
mighty17[m] | <mighty17[m]> "uvos: compiled omapconf, what..." <- went thru the whole wiki, too much info :/ | 11:47 |
mighty17[m] | https://paste.debian.net/1221489/ i suppose this? | 11:49 |
freemangordon | uvos: thanks! | 11:55 |
freemangordon | uvos: I am fine with the commit. Either you or Wizzup, please add this description to the commit message before merge | 11:57 |
Wizzup | I'll do it | 11:59 |
freemangordon | thanks | 11:59 |
freemangordon | tmlind: I think it takes 6-8 ms there as well, but don;t have time to check now (RL work pressure :) ). Will check later on. | 12:00 |
lel | IMbackK synchronize a pull request: https://github.com/maemo-leste/hildon-desktop/pull/17 (fix time overflow bug in tidy-finger-scroll) | 12:01 |
uvos | Wizzup: i allready did it | 12:01 |
uvos | mighty17[m]: audio os_idle | 12:01 |
uvos | mighty17[m]: audit os_idle | 12:01 |
Wizzup | uvos: I just did it locally and did a changelog | 12:02 |
Wizzup | but uh, let me check | 12:02 |
Wizzup | uvos: ok I'll go with mine since it's the same | 12:03 |
Wizzup | uvos: btw I ordered 2 droid3 polarcell batteries | 12:08 |
Wizzup | let's see if they give me more than the estimated 400mAh on the current battery | 12:08 |
uvos | 400mAh uff | 12:09 |
Wizzup | upower estimates 1200mAh for the droid4 one so it seems not entirely wrong | 12:10 |
Wizzup | btw it looks like various pins not in the gpiomap are in the kernel src I linked last night, right? | 12:11 |
uvos | Wizzup: yes thats true | 12:15 |
uvos | (also on xt894) | 12:15 |
uvos | ofc those should not be a problem for you to find an compear | 12:15 |
Wizzup | right | 12:27 |
Wizzup | new h-d is in -devel | 12:27 |
lel | MerlijnWajer closed a pull request: https://github.com/maemo-leste/hildon-desktop/pull/17 (fix time overflow bug in tidy-finger-scroll) | 12:35 |
uvos | tmlind: can you get die_id on the mainline kernel? | 12:45 |
uvos | tmlind: here is a patch for kexecboot to allow correct handling of xt875: http://uvos.xyz/maserati/patches/0001-Add-detection-for-the-xt875-s-mainline-kernel.patch | 12:49 |
tmlind | uvos: ok i think we decided not to export die_id years ago after the pentium id fiasco | 12:53 |
uvos | tmlind: ok then on bionic i cant do any better for the rootpassword in kexecboot that this | 12:53 |
uvos | *than | 12:53 |
tmlind | well the busybox there should have reg read capability though | 12:54 |
tmlind | see droid4-pm script for that | 12:54 |
tmlind | busybox devmem | 12:55 |
uvos | tmlind: mmcblk1p18 is what fastboot partition on mz617? | 12:59 |
uvos | cdrom? | 12:59 |
mighty17[m] | <uvos> "mighty17: audit os_idle" <- https://paste.debian.net/1221497/ | 13:01 |
tmlind | uvos: that's cache partition | 13:04 |
tmlind | uvos: i think that's about the only partition that can be flashed with fastboot on mz617.. | 13:05 |
tmlind | also mmcblk1p19 | 13:06 |
tmlind | can be flashed, that's preinstall | 13:06 |
uvos | uff this sucks | 13:20 |
Wizzup | uvos: mhm? | 13:27 |
uvos | Wizzup: dident realise that mbm.bin on mz617 is even more resitrictive than even mbm.bin on xt8xx let alone allow-mbmloader-flashing-mbm.bin | 13:29 |
Wizzup | arg | 13:30 |
Wizzup | uvos: have you seen a lot of resets? | 14:33 |
Wizzup | I haven't really | 14:33 |
Wizzup | droid4 | 14:33 |
uvos | yes | 14:33 |
Wizzup | hmm, I had uptime of ~1.5 days and now ~20hrs | 14:34 |
Wizzup | I rebooted the 1.5 for kernel upgrade | 14:34 |
Wizzup | bbiab | 14:34 |
uvos | dident know d4 support was allready in linux 1.5 | 14:35 |
uvos | oh 1.5 days | 14:35 |
Wizzup | mhm | 14:35 |
uvos | it mostly reboots with smplayer playing something | 14:35 |
Wizzup | aha, ok | 14:35 |
mighty17[m] | <mighty17[m]> "https://paste.debian.net/1221497..." <- uvos ^^ | 14:35 |
uvos | mighty17[m]: dss is on device cant idle with that isent ideling | 14:38 |
uvos | also sgx | 14:38 |
uvos | also your sysconfig is wrong full_log tells you what exactly in eatch category | 14:39 |
mighty17[m] | uvos: well so how do i add idle support to it? | 14:39 |
mighty17[m] | or do i just stop dss ??? | 14:39 |
uvos | omapdrm has perfectly fine support for ideling dss | 14:40 |
uvos | its just broken on your device for some reason | 14:40 |
uvos | could be userspace | 14:40 |
mighty17[m] | cant debug that? | 14:40 |
mighty17[m] | and what about sgx? | 14:40 |
uvos | sgx is probubly active becasue the display is active | 14:41 |
uvos | well debuging | 14:41 |
uvos | run the device with minimal userspace | 14:41 |
uvos | just /bin/bash | 14:41 |
uvos | see if it idles | 14:41 |
uvos | you have to enter dpms with the drm devices there | 14:42 |
mighty17[m] | uvos: uhh how do i do that :/ | 14:42 |
uvos | there is no "easy" way to debug any of this | 14:42 |
uvos | init=/bin/bash | 14:42 |
uvos | but you dont have serial | 14:42 |
uvos | so really no idea | 14:43 |
bencoh | actually there is, but not with a full-blown maemo | 14:43 |
bencoh | unless you disable everything | 14:43 |
mighty17[m] | uvos: welp :( | 14:43 |
bencoh | serial on d4 is easy though | 14:43 |
uvos | he isent on d4 | 14:43 |
bencoh | oh, my bad | 14:43 |
uvos | hes on some samsung tablet | 14:43 |
uvos | problem is he cant interact with the device at all without full blown gui userspace | 14:43 |
bencoh | that'll be hard yeah | 14:44 |
uvos | no otg not serial and no keyboard | 14:44 |
mighty17[m] | uvos: at max i have ssh | 14:44 |
uvos | yeah i mean make yourself a runlevel with just the absolute minimum to connect with ssh | 14:45 |
uvos | ie just load the wifi kernel module and have bash + wpa_supplicant | 14:45 |
uvos | and ssh and nothing else | 14:45 |
mighty17[m] | ow thats gonna be a lot of work | 14:46 |
mighty17[m] | well any other way i can improve my battery life? | 14:46 |
uvos | mo | 14:46 |
uvos | no | 14:46 |
uvos | its not _that_ hard | 14:46 |
uvos | also check what drm output is active in sysfs | 14:47 |
mighty17[m] | omapdrm? | 14:47 |
uvos | also go around sysfs and check the runtime pm states of varoious devices | 14:47 |
uvos | but really you need a minimal system | 14:47 |
bencoh | wait, why wifi? don't you have usbnet? | 14:48 |
uvos | otherwise figureing out what is using what and keeping it active and what is the kernel not implementing pm on some device is going to be nigh impossible | 14:48 |
mighty17[m] | i do.... | 14:48 |
uvos | oh you do | 14:48 |
uvos | last i heard usb dident work | 14:48 |
uvos | well use that | 14:48 |
mighty17[m] | thats why i said ssh | 14:49 |
uvos | ok | 14:49 |
mighty17[m] | uvos: usb otg | 14:49 |
uvos | well minimal system with just usb net | 14:49 |
uvos | then | 14:49 |
mighty17[m] | i have no idea how'd i do that | 14:49 |
uvos | well maybe focus on why dss isent ideling first | 14:50 |
uvos | that should be possible with full system | 14:50 |
uvos | thats not enough to get it to idle ofc | 14:50 |
uvos | but its a first step | 14:50 |
uvos | omapdrms outputs arnt in dapm state | 14:50 |
uvos | so figure out why | 14:51 |
mighty17[m] | wait wait, lemme understand | 14:51 |
uvos | some of the stuff that omapconf reports as errors in sysconfig are proububly easy pickings too | 14:51 |
mighty17[m] | uvos: maybe coz it isnt getting the clk it wants | 14:51 |
uvos | see full_log | 14:51 |
mighty17[m] | `/os_idle_uc_audit_summary.txt` ? | 14:52 |
uvos | no | 14:52 |
uvos | full_log | 14:52 |
uvos | you have to specify that omapconf shal create it in its cmdline | 14:52 |
uvos | anyhow on d4 we have 6 errors in omapconf - those are related to off mode not working and some spurtious ones with clock rates | 14:53 |
uvos | you have 12 | 14:53 |
uvos | so check out what those 6 extra are and fix em. | 14:53 |
mighty17[m] | Alright, thanks for the help! I'll try to check those extra 6 | 14:54 |
uvos | "[14:51] <mighty17[m]> uvos: maybe coz it isnt getting the clk it wants" i have no idea what you mean by this | 14:54 |
uvos | but if somehing isent geting the right clock you should fix that ofc | 14:55 |
mighty17[m] | uvos: I don't know how to fix that tho! I put the correct value and my display goes crazy, I have to put half the value | 14:55 |
uvos | anyone else haveing issues with dtschema when building 5.16-rc3? | 15:33 |
uvos | tmlind: maybe | 15:33 |
uvos | sort: -:2: disorder: 2021.02 | 15:34 |
uvos | ERROR: dtschema minimum version is v2021.2.1 | 15:34 |
uvos | did try mrproper and git clean | 15:34 |
uvos | i ended up having to install https://github.com/robherring/dt-schema by hand | 16:54 |
uvos | there is a package in arch but its to old - im kindof suprised that the kernel needs really very special outside depends to build now. | 16:55 |
uvos | *https://github.com/devicetree-org/dt-schema | 16:58 |
uvos | anyone here have a bit more expierance with debootstrap? | 23:36 |
Wizzup | I think bencoh has some, looking at his lxc setup | 23:37 |
uvos | i can create a debian rootfs just fine | 23:38 |
uvos | but if i try to create a devuan one | 23:38 |
uvos | i end up with no init | 23:38 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!