<Pali>
freemangordon: Hi! Did you have a time to look at that u-boot rx51 usb code?
ikmaak has quit [Remote host closed the connection]
cockroach has joined #maemo-leste
scops has joined #maemo-leste
<scops>
Hello :) i`m going to buy a pinephone for maemo leste since i really liked Diablo back in the day (i know maemo leste is more like maemo 5 than 4). so my question is; do i need to reflash and follow the steps on https://leste.maemo.org/PinePhone for every update or can i just "apt upgrade" or something like that?
<scops>
and how useable for example in compare to Nokia n810/n800 is maemo leste in the current state of development?
<Wizzup>
apt upgrade will work
<Wizzup>
n810 didn't do calls, right?
<scops>
yeah, i dont need a new phone... i'm looking for modern replacement for my old internet "tablet" ;)
<scops>
so wwan functionality doesnt matter for me atm
<Wizzup>
pinephone with keyboard should work pretty well
<Wizzup>
there are some power management and 3d driver things to sort out, but it's not bad I think
<scops>
does leste also include modern ports of old applications? for example gpe apps or the original internet tablet and maemo5 apps like the mailer, file management (....)?
<scops>
i ask because imho modern gtk3 apps are somewhat slow on librem5 (i have one) and even slower on the pinephone
<scops>
(hehe even my old n810 feels faster on something like ebook reading or file management than the librem5 with phosh xD)
<sicelo>
:-)
<sicelo>
As for old applications, some have been ported already, and others can be ported on request
Twig has quit [Ping timeout: 272 seconds]
<scops>
how can i show the mouse on vbox? in the wiki there is a command switch for qemu... but on vbox?
<Wizzup>
it should just be visible
<scops>
it isnt... i'm testing the maemo-leste-1.0-amd64-20210530 build
<scops>
it flashes for a sec if i scroll
gordon1 has joined #maemo-leste
<Wizzup>
scops: what input device did you select in vbox
<scops>
thats what i said, that is a commandline switch for
<scops>
qemu
<scops>
not for virtualbox
Twig has joined #maemo-leste
<gordon1>
hi, got redirected here from #maemo, basically a question about n900 power management, why leste's current consumtion is 10x more than original freemantle? Do we know the reason? I got told that it's up to userspace cooperation and everything is ready for correct PM in kernel, is that so? And if that's so can I at least get proof-of-concept 8mA consumtion on idle with everything disable and no
<gordon1>
userspace software runing with recent kernel?
<gordon1>
guys on #maemo told me that it is up to userspace, i.e. userspace stop CPU from going into those states?
<buZz>
right, i'm not sure what you're asking, you want to run the kernel without any userspace?
<buZz>
maybe you could replace /bin/init with a small script? :P
<buZz>
not sure how you'd even readout power draw then, unless you're measuring externally
<gordon1>
yep, i've been there too, but only relevant issue there is power consumtion measurement tool, which just shows that cpu doesn't go below C1 for any significant amount of time, but i'm not sure if it answers the question "why?", maybe i just can't read the output of this tool
<gordon1>
yeah, that could be a start, good idea
<buZz>
a linux system is many parts that can all be throwing rocks in the gears :)
<bencoh>
you don't really need to "replace" /bin/init for that btw
<gordon1>
i think i can just read bq27200/current_now every N seconds, is that reliable source of current consumption?
<bencoh>
you can just disable most services and see whether it actually starts entering idle states
<buZz>
oh thats a nice route aswell yeah
<buZz>
does framebuffer console work on the leste kernel?
<bencoh>
gordon1: probably, and if not, there is some script that reads values from the bq27xx fuel gauge using i2cget
<gordon1>
bencoh: well, i thought more of doing some small initrd to make sure there is nothing running
<Wizzup>
gordon1: we do know the reason, we don't hit OFF mode currently
<Wizzup>
so something keeps kernel awake
<bencoh>
gordon1: that would probably work as well
<Wizzup>
could be powervr driver or something else
<Wizzup>
it's solveable (and I got a later kernel to idle well without pvr loaded)
<buZz>
does n900 use the same version of powervr as droid4 ?
<Wizzup>
buZz: not currently, no
<buZz>
could it?
<gordon1>
Wizzup: yey
<bencoh>
(huh, I was about to ask whether it was pvr-related :( )
<gordon1>
so, to summarize, we can get low power consumption without graphics?
<bencoh>
Wizzup: does it reach the default arm idle state (based on wfi) at least?
<buZz>
wizzup said he achieved that on a different kernel from the one inside leste now
<gordon1>
is there some "generic" fb stuff that i could use instead of powervr driver?
pere has joined #maemo-leste
<gordon1>
buZz: well, i'm compiling my mainline 5.19.2 right now to give it a try, so don't think that's a problem
<Wizzup>
gordon1: great, you can start trying it with minimal userspace, see if it hits off mode, then starting maemo
<Wizzup>
keep in mind that leste requires powervr in the kernel, and we don't have that in recent lerkenl
<Wizzup>
kernel*
<Wizzup>
also 5.19?
<gordon1>
oops
<gordon1>
5.12
<Wizzup>
I recently wrote a long message about pwr mgmt
<gordon1>
how can i verify that it is in OFF mode? is it C7 on power-top?
<bencoh>
I would check every /sys/devices/system/cpu/cpu0/cpuidle/state*
<gordon1>
>A shortcut to start on (2) and (3) is to load the latest kernel without powervr on the n900 and start working on OFF mode, without 3d acceleration
<gordon1>
(i'm ok with that)
<gordon1>
(i just need a terminal)
<gordon1>
bencoh: thanks
<gordon1>
thanks, i'll try to play with latest kernel and stuff like pmos/i3wm to check if it can do proper PM
<gordon1>
spoiler: with stock pmos/5.7.0 kernel it cannot
<buZz>
quite sure i3wm has nothing to do with power management :P
<Wizzup>
gordon1: you do need to enable off mode via sys or proc, and also try to boot to just init=/bin/sh
<gordon1>
ok
* gordon1
first needs to bisect why 5.12 keeps panicing but 5.7 doesn't
<sicelo>
It's /sys, and recent kernels enable it by default
<gordon1>
i took pmos config from 5.7, did olddefconfig and now getting panics
<gordon1>
can't read full stacktrace since i don't have UART
<gordon1>
if you have working 5.12 config i would really appreciate if you can share it
<sicelo>
I'm on android phone currently, but will see if I have it handy
<sicelo>
But did you try omap2plus_defconfig as is?
<gordon1>
well, i thought about that but superficial check showed that it lacks some rx51 options so i decided no to go with it
<sicelo>
Options such as?
<sicelo>
I'd definitely recommend starting with omap2plus, then enable what you need
<sicelo>
I think 5.12 needed mmc aliases too
<gordon1>
i don't remember which one in particular, i just grepped by RX51 and found multiple =n
<buZz>
maybe one was RX51_enable_hugepowerdraw
<buZz>
:D
<sicelo>
:-D
<Wizzup>
I mean, we could work on OFF mode now, but then we'd have a n900 without 3d
<Wizzup>
and if you haven't seen it - llvmpipe on the n900 is pure sadness
<Wizzup>
expect 0.1fps
<gordon1>
do i need to do something in particular to enable off mode?
<Wizzup>
gordon1: sicelo said that recently it was enabled by default, but the n900 wiki page on leste.maemo.org should contain a lot of info
<Wizzup>
I don't recall currently, sorry
<Wizzup>
gordon1: see:
<Wizzup>
To enable the OMAP sleep debug LEDs (on the keyboard). Open keyboard, turn off the screen with the slider, and the LEDs will turn off if the phone ever reaches sleep modes.
<gordon1>
yeah, read that, but that's just indication..
<gordon1>
but that might be helpful
<Wizzup>
it is a solid indication since the leds never go off if you don't hit OFF mode
<Wizzup>
unless you're in direct sunlight :-)
<Wizzup>
brb
<gordon1>
well, booted into pmos recovery initrd with pretty much only /bin/sh running, according to cpuidle/states*/usage it spends most of the time in C2 still
<bencoh>
you could check /proc/interrupts for more info
<sicelo>
You enable it by echoing 1 to /sys/kernel/debug/pm_debug/enable_off_mode ... something like that
<gordon1>
i would if i find out how to type '|' =/
<gordon1>
or '>'
<sicelo>
Then you can use the LEDs for indication
<sicelo>
You can load a console keymap or something
<gordon1>
nvm, it has tee
<bencoh>
:]
inky_ has quit [Ping timeout: 268 seconds]
<gordon1>
#1 is pm_wkup
<gordon1>
which sounds like no shit sherlock
<bencoh>
wait, there is a "pm_wkup" interrupt?
<bencoh>
sounds fun
<gordon1>
according to /proc/interrupts there is
<bencoh>
doesn't show up in maemo5 kernel, so I guess it's ""new""
<gordon1>
second one is gp_timer, third - 48070000.i2c
<gordon1>
those one >10k
<gordon1>
rest are under 1k
<gordon1>
*those ones
<gordon1>
that's 5.7.0
<gordon1>
will try 5.12 with omap defconfig
<sicelo>
You might find 5.12 is busier than 5.7 :-)
<gordon1>
5.12.9 with omap2plus_defconfig results in black screen
<bencoh>
alright, gp_timer comes from ./arch/arm/mach-omap2/timer.c
<bencoh>
(looks like it's the clocksource on omap)
<bencoh>
pm_wkup comes from ./arch/arm/mach-omap2/pm34xx.c and it has some funky comment
<gordon1>
i2c thing means something is polling some i2c device, doesn't it?
<bencoh>
yeah
<bencoh>
well, either actively polling, or reading some i2c registers after receiving some interrupt
<gordon1>
sicelo: i don't use mmc right now, it just loads initrd
<gordon1>
but lemme try anyway
<gordon1>
sicelo: 5.12.9 already has that code
<sicelo>
Ah. I checked against 5.12.7 which is the most recent I have on my laptop
<gordon1>
omap2plus_defconfig has no FB_OMAP2 enabled
<sicelo>
Something else I found with N900 (at least the one I have) is that sometimes you just have to keep retrying boot ... maybe something doesn't reset properly once in a while, ¯\_(ツ)_/¯
<sicelo>
Uses drm fb
<gordon1>
5.7.0 config uses fb_omap2 and works, i'll try to enable it
<gordon1>
didn't help
<sicelo>
I was using drm for my tests
<gordon1>
yeah, omap2plus_defconfig even more unsuccessful than taking config from pmos, can't even get kernel output
<gordon1>
i probably need to solder UART
<sicelo>
It needs patience :-)
<sicelo>
UART would be best, of course
<gordon1>
oh, no patience involved, it returns back to off state after a while (i assume when panic timeout passes), so i can turn it on again
<Wizzup>
gordon1: there's also the patch on the wiki to debug what is blocking deeper idle states
<sicelo>
Meant, patience to find good config
<gordon1>
ah
<Wizzup>
gordon1: iirc last time tmlind tried with 4.12 it just booted with omap2plus_defconfig
<Wizzup>
5.12*
<sicelo>
Will upload config from 5.12-rc8 ... I might have had some unnecessary stuff, can't remember
<gordon1>
well, maybe there is something that is required compiled as module or i am doing something wrong preparing uImage