00:17
xmn has joined #maemo-leste
00:23
akossh has quit [Quit: Leaving.]
00:52
xmn has quit [Ping timeout: 264 seconds]
01:10
xmn has joined #maemo-leste
01:11
xmn has quit [Client Quit]
01:38
lul4 has joined #maemo-leste
01:45
System_Error has quit [Remote host closed the connection]
01:52
System_Error has joined #maemo-leste
01:58
hm has quit [Remote host closed the connection]
02:44
Anasko has quit [Read error: Connection reset by peer]
02:45
Daanct12 has joined #maemo-leste
04:23
xmn has joined #maemo-leste
05:00
pagurus has joined #maemo-leste
05:20
Anasko has joined #maemo-leste
05:34
<
mkfx >
neat. got leste running on android.
05:37
<
mkfx >
is it fesiable to have a "android" port or it's against goals of leste? (native and mainline only?)
05:59
joerg has quit [Ping timeout: 260 seconds]
06:01
joerg has joined #maemo-leste
06:08
lul4 has quit [Quit: had to jack off]
06:49
Daanct12 has quit [Ping timeout: 265 seconds]
06:53
Daanct12 has joined #maemo-leste
06:57
mkfx has left #maemo-leste [#maemo-leste]
07:14
_fab has joined #maemo-leste
07:22
Anasko has quit [Ping timeout: 248 seconds]
07:34
_fab has quit [Ping timeout: 252 seconds]
07:34
mkfx has joined #maemo-leste
07:36
ungeskriptet has quit [Ping timeout: 248 seconds]
07:36
ungeskriptet has joined #maemo-leste
07:47
Anasko has joined #maemo-leste
08:17
alifib has joined #maemo-leste
08:19
ikmaak has quit [Ping timeout: 252 seconds]
08:20
ikmaak has joined #maemo-leste
08:27
alifib has quit [Quit: .]
08:36
antranigv has quit [Ping timeout: 246 seconds]
08:38
gnarface has quit [Ping timeout: 265 seconds]
08:42
gnarface has joined #maemo-leste
08:44
antranigv has joined #maemo-leste
08:58
mkfx has left #maemo-leste [#maemo-leste]
09:00
gnarface has quit [Ping timeout: 248 seconds]
09:00
gnarface has joined #maemo-leste
09:37
mkfx has joined #maemo-leste
10:01
xmn has quit [Ping timeout: 252 seconds]
11:04
<
freemangordon >
mkfx: we are fine, the issue is that such port has maybe 30% of the functionality
11:05
Anasko has quit [Read error: Connection reset by peer]
12:06
<
Wizzup >
mkfx: please document the process
12:06
<
Wizzup >
and make it replicable
12:11
mkfx has left #maemo-leste [Disconnected: Replaced by new connection]
12:11
mkfx has joined #maemo-leste
12:27
pagurus has quit [Ping timeout: 265 seconds]
12:33
arno11 has joined #maemo-leste
12:34
<
arno11 >
mkfx: did you use proot or chroot ? or another method ?
12:35
<
arno11 >
btw under proot, i see let's say 85-90% of things working. even mobile data works through the dummy network
12:40
<
sicelo >
Wizzup: let me try today (re:maeotp icon) :-)
12:40
mkfx has left #maemo-leste [Error from remote client]
12:43
Daanct12 has quit [Quit: WeeChat 4.4.4]
12:44
<
Wizzup >
sure @ name
12:52
Daanct12 has joined #maemo-leste
13:17
Twig has joined #maemo-leste
13:32
Guest9365 has joined #maemo-leste
13:43
<
dsc_ >
I didnt test QML @ vkb, ill try
14:05
Daanct12 has quit [Quit: WeeChat 4.4.4]
14:17
<
Wizzup >
arno11: it would be really nice to get documentation on how to make a proot image
14:17
<
Wizzup >
so that we can make it in CI
14:22
<
arno11 >
Wizzup: agree, but idk what exactly diejuse modified in the original old pi3 ascii img
14:24
<
dsc_ >
Wizzup: some complications with the QML stuff because hildon steals focus
14:24
<
dsc_ >
ill fix it..
14:27
<
Wizzup >
freemangordon: I ported the tp-haze python scripts to py3
14:27
<
Wizzup >
should we try to send that upstream?
14:28
<
Wizzup >
I don't know if they work btw, would be worth checking on chimaera whether the results are the same
14:30
<
sicelo >
arno11: didn't diejeuse document it somewhat?
14:31
<
arno11 >
sicelo: somewhat yes, but not the part about img modifications
14:32
<
arno11 >
but it was a very old img
14:33
<
arno11 >
maybe it works better with a recent one, with few modifs in the starting script under termux
14:34
<
arno11 >
i really don't know. i've been able to dist-upgrade to chimaera -devel so i didn't try anything else
14:36
<
arno11 >
(i mean i didn t try the process with another img)
14:36
<
Wizzup >
freemangordon: maybe I am confused and looking at the wrong tp haze branch, I thought you already build a newer one with more patches
14:36
<
Wizzup >
freemangordon: ah, yes, indeed, I used the wrong branch
14:37
<
Wizzup >
ok, that was a wasted time :D
14:37
<
Wizzup >
too bad master wasn't in sync
14:46
mkfx has joined #maemo-leste
14:46
<
arno11 >
Wizzup: i still need 1-2 weeks for maemo-gpt and then i'll have a look @proot stuff
14:51
<
Wizzup >
freemangordon: pulling in sfos patch for tp-ring python2 code to port it to py3
14:52
<
Wizzup >
we should rebase on sfos later, but they have deps on their own internal daemons in it now
14:53
<
dsc_ >
I need to modify HIM to make it work with QML, even then the fix is hacky
14:53
<
Wizzup >
dsc_: got some details?
14:54
<
dsc_ >
keyboard raises, steals focus from Qt app, keyboard goes away, focus re-enters, which triggers the keyboard again
14:54
<
dsc_ >
this does not happen with regular widgets because they do not call showInputPanel() a second time
14:55
<
dsc_ >
proposed solution is to add a command to HIM "keyboard close" so I can throttle it
14:55
<
dsc_ >
another possible solution is not to steal focus
14:56
<
dsc_ >
this work-around is not possible, because Qt5 has a new api
14:56
<
dsc_ >
the new api = showInputPanel()
14:57
<
Wizzup >
ok, let's not add a new command to h-i-m just yet and see what we can do here
14:57
<
Wizzup >
does h-i-m explicitly steal focus, or does it just get focus?
14:58
<
dsc_ >
most likely it just gets focus
14:58
<
dsc_ >
from it being a new x11 thing
14:58
<
dsc_ >
and tbh maybe thats fine
14:59
<
dsc_ >
but I'm not sure how to prevent the loop from happening
15:00
kiva has joined #maemo-leste
15:04
<
kiva >
although link says "fully detailed" the page does not have even fully specification..it has full phone it...but boots first with Intel Atom..so it might have possibility replace boot code.
15:07
<
kiva >
sadly quite expensive in second hand markets, so I dont have money for test boot to linux.
15:16
Anasko has joined #maemo-leste
15:19
arno11 has left #maemo-leste [#maemo-leste]
15:31
<
kiva >
anyway it should be easy examine can it make to Maemo Leste device, because it can boot to Win7.
15:32
<
Wizzup >
freemangordon: I've got a few more pkgs to go but then I think the main blockers for daedalus will be mesa/sgx and tracker
15:32
<
Wizzup >
there's also some tinymail complication issue but I will try to solve that, same for osso-calculator-engine
15:36
<
sicelo >
kiva: if you have the device and are able to get linux booting, then yes, sounds doable
15:36
mkfx has left #maemo-leste [Error from remote client]
15:46
<
Wizzup >
I would image the battery life will be bad
15:49
<
sicelo >
kiva: maybe we need to forget about that device then (at least for the time being) :-)
15:52
<
kiva >
battery life bad indeed...in win7 use it is 2 hours...but old intel atom can drop CPU speed very slow on the fly to wait phone calls and wake up when call coming.
15:53
xmn has joined #maemo-leste
15:54
<
kiva >
sicelo, yes that is true..it is not first thing to do, but if somebody finds it for cheap for tests,it would be good to test.
15:59
<
sicelo >
Wizzup: freemangordon: i'm confused by the N900 camera's dmesg, which reports "could not get clock."
16:00
<
freemangordon >
maybe DTS is wrong/missing
16:00
<
freemangordon >
Wizzup: what's with mesa?
16:00
<
sicelo >
now the curious thing is ... this part of driver has been this way since day 1, and same for DTS
16:01
<
freemangordon >
sicelo: perhaps back then there was a fallback if named clock does not exist
16:01
<
sicelo >
no idea how this ever worked. also looks like return value for `devm_clk_get` has also been stable over the years when given NULL as id
16:01
<
freemangordon >
sorry, when default clock does not exist
16:02
<
sicelo >
anyway, i will test the driver with explicit "extclk" instead of null and see
16:09
<
Wizzup >
freemangordon: ah, I thought we wanted newer mesa
16:09
<
Wizzup >
freemangordon: do you want me to import chimaera mesa and sgx for now
16:09
<
Wizzup >
s/import/build/
16:09
<
Wizzup >
well, our chimaera
16:11
<
freemangordon >
sec
16:12
<
freemangordon >
what is mesa version in daedalus?
16:12
<
Wizzup >
I think that's why I was asking for your help :D
16:13
<
Wizzup >
I don't have a good idea of what mesa patches we have, what amber or not menas for us, etc
16:13
<
Wizzup >
and I don't know about this repo either
16:13
<
freemangordon >
this is the official TI repo for sgx mesa
16:13
<
freemangordon >
basicalli it has the same as what I did back then for 'our' mesa
16:13
<
Wizzup >
last commit 1 year ago, or do we want other branch
16:14
<
freemangordon >
23.2.1?
16:14
<
freemangordon >
I guess we can uplift 22.3.5 to 22.3.6
16:15
<
Wizzup >
would be better if we can stay on 22.3.x, then we don't need special libdrm etc
16:15
<
freemangordon >
ok, lets do it then
16:15
<
freemangordon >
I will rebase 22.3.5 to 22.3.6
16:15
<
freemangordon >
or, maybe can just have sgx patches in /debian
16:16
<
freemangordon >
hmm?
16:16
<
Wizzup >
I prefer not to use debian/patches
16:16
<
freemangordon >
do you have link to debian mesa?
16:16
<
Wizzup >
do we also want newer sgx-ddk-um?
16:16
<
freemangordon >
yes, sure, but not immediately
16:17
<
freemangordon >
lets see if that allwinner with its 4 cores can do fatser :)
16:18
<
Wizzup >
probably not great
16:18
<
freemangordon >
yeah
16:18
<
Wizzup >
I can maybe set something up
16:18
<
Wizzup >
btw, we also need to enable gles v1, etc
16:18
<
Wizzup >
there's a lot of patches we carry, also just to debian/
16:19
<
freemangordon >
yeah
16:20
<
Wizzup >
I wonder if the kirkstone branch is for us
16:20
<
Wizzup >
maybe it's not
16:21
<
freemangordon >
I think it is
16:22
Twig has quit [Remote host closed the connection]
16:22
<
Wizzup >
also note that they dropped __DRIimageExtension to 7 from 8, we set it to 8 from 14
16:22
<
freemangordon >
could be
16:22
<
freemangordon >
will see if there are issues, will fix thema st they arise
16:23
<
Wizzup >
I think if you take this branch and rebase for the minor one in debian we will already have the commit, then we just need to pick our changes
16:23
<
freemangordon >
mhm, something like that
16:23
<
freemangordon >
but, I need a machine to build on
16:23
<
freemangordon >
do we already have VM images?
16:24
<
Wizzup >
for daedalus? no
16:24
<
freemangordon >
dist-upgrade?
16:24
<
Wizzup >
I don't know if this will build on amd64 either
16:24
<
freemangordon >
why not?
16:24
<
Wizzup >
maybe I should try dist-upgrade first and let you know, there might be a few repos missing
16:24
<
Wizzup >
maybe it will, don't know if it needs sgx specific libs/headers
16:24
<
freemangordon >
no, it does dload/dlsym
16:25
<
freemangordon >
IIRC
16:25
buZz has quit [Read error: Connection reset by peer]
16:25
<
Wizzup >
well, you can certainly snapshot and then try dist upgrade
16:25
<
freemangordon >
ok, lemme clone my chimaera
16:25
<
freemangordon >
mhm
16:25
<
Wizzup >
I didn't do this yet but think we're close
16:25
buZz has joined #maemo-leste
16:25
buZz is now known as Guest9825
16:28
<
freemangordon >
mafw-tracker will take some time
16:28
<
Wizzup >
right, it's not essential atm
16:29
<
freemangordon >
hmm, I wonder what we can do for hildon python bindings
16:29
<
freemangordon >
do we need gtk3 hildon?
16:30
<
Wizzup >
right now we will just have nothing with python/gtk2
16:30
<
Wizzup >
but yes, later on we need to deal with this
16:30
<
freemangordon >
no applets?
16:30
<
Wizzup >
well there's actually very very little that uses gtk2 python
16:30
<
Wizzup >
there's the binary clock applet
16:30
<
Wizzup >
and there's syncevolution-frontend
16:31
<
Wizzup >
that's it I think
16:31
<
Wizzup >
so yes, eventually we'd want gtk3 hildon, but we can live without it even until trixie
16:31
<
Wizzup >
the main upcoming issue will be gconf2 no longer existing in trixie, so we need to go to gsettings
16:31
<
Wizzup >
but for bookwork (daedalus), we're ok
16:31
<
Wizzup >
even for chimaera I had to put in a lot of effort to get some py2 stuff going, and I'm happy not to even try again
16:32
<
freemangordon >
lets see if I will be able to cross-compile mesa
16:32
<
Wizzup >
I can set up a vm for you on our honeycomb build machine
16:32
<
freemangordon >
hmm, wait, I am on ubuntu 20
16:32
<
freemangordon >
or 22
16:33
<
freemangordon >
yeah 20
16:33
<
freemangordon >
I should not need VM, no?
16:33
<
Wizzup >
merlijn@honeycomb:~$ ls devuan-vm-aarch64-plain/
16:33
<
Wizzup >
devuan.qcow2 efi mini.iso
16:33
<
Wizzup >
I can set that up if you want
16:33
<
freemangordon >
21.2.6-0ubuntu0.1~20.04.2
16:34
<
freemangordon >
that's what my native OS is on
16:34
<
freemangordon >
hmm old
16:34
<
Wizzup >
I am setting you up with a vm
16:34
<
freemangordon >
lemme first see if I can do with local VM
16:34
<
freemangordon >
unless you have very fast internet
16:34
<
freemangordon >
hmm...
16:35
<
freemangordon >
still, lemme try local first
16:35
<
freemangordon >
as I will need it anyways
16:36
<
freemangordon >
I am using nfs mount from PC->VM for access to source files
16:37
<
freemangordon >
and my inet is nto that fast as yours (perhaps 75MBs)
16:39
<
Wizzup >
ok, in any case I set up the dev vm
16:40
<
freemangordon >
sure
16:40
<
Wizzup >
as in, I did it already
16:40
<
Wizzup >
I'll dist upgrade it
16:40
kiva has quit [Ping timeout: 240 seconds]
16:48
<
freemangordon >
Wizzup: hmm, why dist-upgrade wants to remove qt applications?
16:52
<
Wizzup >
let me check
16:52
<
Wizzup >
freemangordon: don't know, I think you can just let it remove them for now and it will get pulled in again later
16:53
<
Wizzup >
I will try a dist upgrade once I've done a few more repos
16:54
<
freemangordon >
yep, that's what I did
17:00
<
Wizzup >
I am dist-upgrading the dev vm to daedalus now btw
17:00
<
Wizzup >
(armhf vm)
17:14
_fab has joined #maemo-leste
17:22
<
freemangordon >
me too (amd64)
17:23
<
freemangordon >
Wizzup: I ran out of time today, will continue tomorrow
17:24
<
Wizzup >
let me know if you need a armhf vm
17:24
<
freemangordon >
sure
17:25
akossh has joined #maemo-leste
17:34
Guest9825 is now known as buZz
17:40
arno11 has joined #maemo-leste
18:16
<
arno11 >
Wizzup: btw for daedalus, indeed pa-modules-nemo/cmtspeech-n9xx are not needed
18:25
whatsupboy has quit [Ping timeout: 245 seconds]
18:35
Twig has joined #maemo-leste
19:19
doc has quit [Ping timeout: 244 seconds]
19:30
doc has joined #maemo-leste
20:13
pere has quit [Ping timeout: 246 seconds]
20:29
Twig has quit [Remote host closed the connection]
20:42
xmn has quit [Ping timeout: 272 seconds]
21:27
pere has joined #maemo-leste
21:40
xmn has joined #maemo-leste
22:43
Anasko has quit [Ping timeout: 276 seconds]
22:51
arno11 has left #maemo-leste [#maemo-leste]
23:04
<
Wizzup >
ok, I made a python script to parse all our jbos and their configs to generate an ordered list of packages - so that we can build them in order without having to worry about deps next time
23:04
<
Wizzup >
I just had to inject 'mce-dev' as a dep since that's our only circular one somehow :)
23:05
<
freemangordon >
VM does not boot to HD after dist-upgrade
23:05
<
freemangordon >
will look at it tomorrow
23:09
<
Wizzup >
this will help a lot with trixie I think
23:13
<
Wizzup >
freemangordon: hmm
23:14
<
Wizzup >
root@devuan-armhf-dev:~# cat /etc/*release*|head -n1
23:14
<
Wizzup >
PRETTY_NAME="Devuan GNU/Linux 5 (daedalus)"
23:14
<
Wizzup >
root@devuan-armhf-dev:~# arch
23:14
<
Wizzup >
the armhf vm on my aarch64 host is ready at least
23:30
_fab has quit [Quit: _fab]
23:43
LjL has quit [Read error: Connection reset by peer]
23:44
LjL has joined #maemo-leste