<freemangordon>
uvos: I think it is more that hildon doing compositing
<freemangordon>
I installed and ran icewm and it makes no diff in gtkperf
<freemangordon>
so maybe I am doing something stupid in the driver
<freemangordon>
xorg driver that is
<Wizzup>
is it fast on fremantle?
<freemangordon>
which one?
<Wizzup>
gtk scrolling performance
<freemangordon>
yes
<freemangordon>
way better
<freemangordon>
compare scrolling in control panel
<freemangordon>
n900/fremantle is faster than d4/;este
<freemangordon>
*leste
<buZz>
hehe, i already find the d4 fast in gui stuff, wonder how fast it -could- be
<buZz>
i mean, for the age of the hw
<buZz>
is there any reason to not use debhelper for a -extras package?
<buZz>
¯\_(ツ)_/¯
<Wizzup>
nope, dh is fine
<freemangordon>
buZz: scrolling in addresbook, for example tops @ 40fps
<freemangordon>
that should be at least 60-70
<buZz>
hmm ok
<buZz>
i think i found a bug in devilutionX that prevents gameplay :( seems it has some code for placing virtual touchscreen buttons, yet the actionbuttons parts of that arent rendered or functional :( boo
<Wizzup>
maybe I should make a Sync page on our wiki and move the contacts and calendar stuff there?
<Wizzup>
buZz: if you have nextcloud you can use that too
<Wizzup>
I'm poking meridion atm to see if he wants to help try it
<buZz>
Wizzup: yes, something like that was my idea, something for 'sync everything to elsewhere' and collect at least links to the other docs
<buZz>
or combine em all
<Wizzup>
freemangordon: imho the scrolling also usually 'lasts too long' if that makes sense
<Wizzup>
buZz: well, we want to discuss calendar and contacts ui features without the sync
<Wizzup>
but yes that is what I meant, I can make a sync page
<freemangordon>
Wizzup: lasting too long should be something we can easily fix
<freemangordon>
the issue is that it is choppy
<freemangordon>
*the real issue
<buZz>
Wizzup: i think setting up nextcloud from zero is more effort than radicale , i dont really want/need a web gui, just 'place to sync to' where i can hopefully share calendar or contacts with other people
<buZz>
but just 'cp' would be fine for sharing too ;)
<Wizzup>
buZz: yes, but others use nextcloud
<buZz>
right, i guess?
<buZz>
the main motivation for syncing is 'share calendar with some android user without thirdparty'
<Wizzup>
hmmm
dev has joined #maemo-leste
<Wizzup>
can you explain your motivation some more
<buZz>
GF wants to know my agenda , atm i need to tell her :P
<buZz>
but i'd like to use qalendar more for it, so i can auto-sync it to her
<Wizzup>
ok, so she will use your radicale then
<buZz>
yeah if that can work :)
<buZz>
ah, devilutionX dev awake \o
<buZz>
weird, lol, if i change resolution to 640x480 , there's nothing rendered (still rendered though, i can see a single frame when i close it)
<buZz>
ah, nevermind, seems the 'upscale' parameter was preventing rendering? weird
Livio has joined #maemo-leste
Livio has joined #maemo-leste
Livio has quit [Changing host]
<Wizzup>
syncevolution complains about the https chain in my nextcloud, which is surely fine
<Wizzup>
meh.
<buZz>
meh, whats the complaint about it?
<buZz>
about that 'upscale' parameter > a devilutionX dev says 'Maybe your system doesn't support software blitting?'
<buZz>
i'm not sure what that means but could be some missing feature in xorg driver?
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
xmn has joined #maemo-leste
<Wizzup>
buZz: let me know if you need help with syncing
<Wizzup>
I'm working on the wiki page now
<buZz>
lol > DEBUG: Couldn't find matching EGL config (call to eglChooseConfig failed, reporting an error of EGL_SUCCESS)
<buZz>
Wizzup: i'll switch topics in a bit, hoping this devilutionX issue might be small enough to fix soon :P
<buZz>
lol > button.png is 87x2262 so the image is probably too tall.
<buZz>
pfff, these ppl think i want to maintain a devilutionX fork just for a single resized image :P they gotta be tripping
<buZz>
does anyone have a N900 with latest leste available that could compile and run devilutionX on it with --verbose 2> verbose.log ? :P
<buZz>
for the leste -extras package, i'll have to add 'something' to get lower res image, but maybe the N900 needs even lower?
<buZz>
or maybe someone already knows max texture dimensions for GLES2 on n900?
<freemangordon>
buZz: max texture dimensions are reported by GL itself, if asked
<buZz>
yeah i know, but i have no N900 here with anywhere near current anything on it :P
<buZz>
this game tries to load a 87x2262 texture and silently fails , leading to difficult gameplay, as some texture is missing
<buZz>
just contemplating 'best' route to get around this
<buZz>
and would be sad to have to redo it for a different Leste device later
<sicelo>
freemangordon: btw this is correct for console on N900? CONFIG_CMDLINE="rootwait root=/dev/mmcblk0p2 console=ttyS0" , or should be some other tty?
<freemangordon>
sicelo: not sure, what is the issue?
<sicelo>
just trying to get console working on n900, for the bisection i've been doing
<sicelo>
i use the latest u-boot from maedevu.maemo.org to start the device, and after u-boot shows "Loading Kernel Image , Starting kernel ...", nothing ever shows up in console
<sicelo>
console output is working while Nolo/X-Loader is running, so i'm guessing i have wrong config in kernel, dunno
<buZz>
sicelo: is your n900 on leste and up to date etc? could you try devilutionX --verbose for me to see max texture size it reports?
<buZz>
so i dont have to fix it later when ppl want to diablo1 on n900
<sicelo>
unfortunately no. it currently has old postmarketOS
<buZz>
alright, guess i should dig up a n900 here ^_^
<sicelo>
i use pmOS or debian when testing newer kernels on n900, because ML is not easy to use without accel. d4 is always running latest ML however, since i don't use it for anything else
<buZz>
alright, found my 3x n900 :P lets see which one works
<sicelo>
no luck, mmm. i must have some other problem with my config then
<buZz>
ah ,ofcourse, the one with the damaged screen, haha, welp, does seem i had leste on it before, but its unable to read SD now .. maybe just loose
<freemangordon>
buZz: BTW, maybe I am blind, but I dont; NEON-optimized functions to increase src/dst
<freemangordon>
*I don;t see
<freemangordon>
obviously the code is correct, maybe I don't remember arm asm enough
<buZz>
arent src/sdt allocated before these calls?
<buZz>
just a guess
<freemangordon>
sure, but those functions are just called in the middle of the function
<buZz>
if its a heavy part of the function, it can matter a lot
<freemangordon>
anyway, I'll try to find some time to port those patches tomorrow and see if it makes any difference
alex1216 has quit [Quit: WeeChat 2.3]
hexagonwin has joined #maemo-leste
<sicelo>
freemangordon: i don't suppose this is still under your radar, but you had asked for the output for the usb problem i'm chasing. here, https://paste.debian.net/1256482/
<sicelo>
[ 13.996612] isp1704_charger isp1707: failed to register isp1704 with error -22
<sicelo>
[ 13.996643] isp1704_charger: probe of isp1707 failed with error -22
<sicelo>
that's what i want to fix. however, the real cause appears to be [ 1.389648] musb-hdrc musb-hdrc.0.auto: error -ENXIO: IRQ mc not found
<sicelo>
in other kernels, there's an actual musb crash, with a trace
<buZz>
might be missing 'mc' label in dtb or something?
<sicelo>
it's there iirc. dts has had no changes at all
dev has left #maemo-leste [Disconnected: Replaced by new connection]
<Wizzup>
I will try to add some more, but please proof read, or even try it out if you want to
<Wizzup>
I need to go head outside for a bit
<sicelo>
buZz: yes, if the N900 is detected, which should normally be the case
<sicelo>
buZz: you boot with keyboard slid out, right?
<buZz>
sicelo: there's no 'boot' step in those instructions?
<buZz>
i skipped the -l and -b above , didn't think i'd need them with -f
<buZz>
Wizzup: cool! i'll go noob it out, got radicale installed already
<sicelo>
i meant - keyboard is slid out when you do the steps?
* sicelo
has never used -f ... want to keep Fremantle intact
<buZz>
sicelo: ah, all the steps?
<sicelo>
yes, at least that way you'll be sure N900 is discoverable by 0xFFFF
hexagonwin has quit [Remote host closed the connection]
<sicelo>
it is discoverable even when closed, to be fair, but some steps require it to be open, so i don't see why i'd close it
<sicelo>
Found USB device: RX-51 (0x421:0x1c7) in RAW disk mode ... <<< wrong mode for sure
<sicelo>
should be in Update Mode for 0xFFFF/flasher
<buZz>
finally, pinephone is compiling devilutionX , pff
* buZz
switches off n900 again :) lets try again
<buZz>
the 2020 uboot does work, right?
<buZz>
and just connecting -powered off- should be enough for it to detect the n900?
<sicelo>
yes
<buZz>
maybe its still shutting down ..
<sicelo>
heh, just take battery out?
<buZz>
ok, battery removed, battery put back in, connect on usb with 'waiting for usb device' still running, the n900 boots straight to uboot thats on the device already :/
<buZz>
-l doesnt help either, maybe its my 0xffff compile? *grabs prebuilt*
<buZz>
weirdly, all 'high current, short cables' didnt work, but a 5M long micro-usb did
<buZz>
:P
Twig has quit [Ping timeout: 265 seconds]
<norayr>
I am thinking what to do for maemo hildonized apps to work on other distros
<norayr>
And maybe instead of porting hildonization to more modern gtks it's better to fork gtk2 and rename it
<sicelo>
um ...
<sicelo>
what applications do you have in mind?
<norayr>
so that our hildonized ghk would work on other distros
<norayr>
Well every hildon app whdch uses let's say hildon buttons
<norayr>
msid, leafpad, mfat, meverything
<norayr>
but maybe that's not possible since they teed hildon to run...
<norayr>
and then that's not good.
<norayr>
i don't know how to solve this problem - our stack usable across oses.
<norayr>
otherwise we are better than nailfish but not much.
<norayr>
that was painful to get rid of sailfish dependency for me.
<sicelo>
many of the hildonized applications came from regular desktop linux... i.e. you can just use the regular desktop versions in other distros
<norayr>
but i don't want to get into other dependency.
<sicelo>
e.g. leafpad
<norayr>
yes but many are developed with hildon in mind and only exist with hildon versions.
<buZz>
seems pinephone doesnt report DPI :( but, does not need the lowres fix, lets see on n900 now
<sicelo>
those aren't many, i think, and can be ported back to regular gtk somewhat easily, i'd say
<norayr>
sigh. maybe you're right. but maybe not many today. if maemo gets used more widely we may get new hdldon only apps. that's not bad, i am thinking on how to use it for advantage.
<norayr>
so forking and renaming gtk2 is one way maybe. getting it to carry everything hildon app needs.
<sicelo>
i'd say - cross that bridge when that day comes :-)
<norayr>
if tdat is possible.
<sicelo>
bear in mind most distros have phased out gtk2 since a while ago
<norayr>
they phased out gnome2 too, then added mate after some time.
<uvos>
i have been using this for qutie some time for contacts sync via carddav btw
akossh has quit [Quit: Leaving.]
<Wizzup>
uvos: wasn't documented anywhere
<Wizzup>
maybe it's helpful to have these online somewhere
<Wizzup>
uvos: do you sync over tls?
<sicelo>
freemangordon: here's a kernel run that has a trace, https://paste.debian.net/1256495/ ... this is with cf081d009c447647c6b36aced535ca427dbebe72 reverted
mardy has quit [Quit: WeeChat 3.5]
pere has quit [Ping timeout: 268 seconds]
<buZz>
lol weird, it almost seems Nokia N900 can compile devilutionX faster than a Pinephone?
<sicelo>
um, what leads to that conclusion?
<buZz>
the speed
<buZz>
:D
<buZz>
lol
<buZz>
i'll make clean , time make , once these tests are done
<buZz>
hmmz, does seem to originate from leste .. libsdl2-2.0-0 at least
<buZz>
eh 2.0.14+dfsg2-3+2m7.8
<Wizzup>
we ought to check out the newer sdl compat stuff too
<Wizzup>
iirc it was supposedly mostly complete now
<buZz>
man, they are kinda resisting to fix this 'as the software renderer shouldnt have it'
<buZz>
i feel this is gonna be slow , the hw renderer already just does 20-30fps :P
pere has joined #maemo-leste
<Wizzup>
"this'?
<buZz>
oh, nevermind, i misunderstood what its being used for
<buZz>
but on droid4 , if i dont use the hw scaling , there's nothing drawn to screen, unless i open the task viewer , and only briefly then , because the program kills itself on alt-tab
<buZz>
but on pinephone, without hw scaling, it works totally fine
<buZz>
Wizzup: is that 2.0.14+dfsg2-3+2m7.8 from our repos somewhere?
<buZz>
can i link the devilutionX devs to it? :P
<buZz>
lol! funny enough, on Nokia N900 the game doesnt see there's a touchscreen! so it runs in normal 'mouse' mode
<buZz>
which kinda works easier? not sure
<Wizzup>
buZz: ours is probably outdated at this point
<Wizzup>
buZz: n900 is resistive and not mt
<buZz>
but thats what we are using now, right?
<buZz>
i know
<Wizzup>
could be related
<Wizzup>
2.0.14 seems like just libsdl2?
<buZz>
oh, yes, libsdl2 indeed, sorry
<buZz>
thats the 'libsdl2-2.0-0'
<buZz>
devilutionX runs quite well on N900 regardless, btw
<Wizzup>
cool, glad ot hear
<Wizzup>
I need to get some sleep :)
<buZz>
welterusten
<buZz>
i'll just do our own fork for now, and later when they release 1.5 we might have it all fixed either on libsdl2 side, or on devilutionX side
<buZz>
The key you just pressed is not recognized by SDL. To help get this fixed, please report this to the SDL forums/mailing list <https://discourse.libsdl.org/> X11 KeyCode 124 (116), X11 KeySym 0x1008FF2A (XF86PowerOff).
<buZz>
(pressed the powerbutton in devilutionX on N900)
ikmaak has quit [Quit: No Ping reply in 180 seconds.]