| arno11 | nice, do you see gpu_unai ? | 00:01 |
|---|---|---|
| Wizzup | arno11: yes | 00:12 |
| arno11 | cool, so it works, i'll send you stuff tomorrow | 00:13 |
| Wizzup | uvos: https://phoenix.maemo.org/job/droid4-linux-binaries/architecture=armhf,label=armhf/195/ | 00:32 |
| Wizzup | make[6]: *** No rule to make target 'debian/linux-image/usr/lib/linux-image-omap/omap4-droid3-xt862.dts', needed by '__dtbs_install'. Stop. | 00:32 |
| uvos | it seams to be looking in the wrong place | 00:44 |
| uvos | all the dts are now in arch/arm/boot/dts/ti/omap/ instead of in arch/arm/boot/dts | 00:44 |
| Wizzup | ok, want me to fix it or shall I? | 00:45 |
| Wizzup | err | 00:45 |
| Wizzup | lol | 00:45 |
| Wizzup | want me to fix it or will you? | 00:45 |
| uvos | i mean i gues, if that is the issue | 00:46 |
| uvos | but then again i dont know how it finds the other dtbs | 00:46 |
| uvos | since those also changed location | 00:46 |
| uvos | so im not sure what to change atm | 00:46 |
| uvos | maybe somehow you are not asking for ti to be built instead | 00:47 |
| uvos | btw this is not how we version the kernel | 00:47 |
| uvos | version should be 6.6.8.0 | 00:47 |
| uvos | the 0 being the version we increment when we make code changes | 00:47 |
| Wizzup | k, it's experimental so not the biggest issue I think | 00:48 |
| uvos | anyhow where is the decision what dtbs to built even made | 00:49 |
| uvos | in the packageing files | 00:49 |
| Wizzup | I don't think it's looking in the wrong place fwiw | 00:49 |
| Wizzup | scripts/package/builddeb | 00:50 |
| Wizzup | I think the droid3 dtb just isn't being built | 00:50 |
| Wizzup | I think I fixed this issue before | 00:51 |
| Wizzup | lol | 00:52 |
| Wizzup | omap4-droid4-xt894.dtb \ | 00:52 |
| Wizzup | omap4-droid3-xt862.dts \ | 00:52 |
| Wizzup | omap4-duovero-parlor.dtb \ | 00:52 |
| Wizzup | see the problem yet? | 00:52 |
| Wizzup | the problem is in 29885d11320666d987fc1028adcc9058f9769fc7 / arch: arm: dts: omap4-droid3-xt862: move into ti/omap | 00:53 |
| uvos | heh | 00:53 |
| uvos | ok | 00:53 |
| Wizzup | I'll fix it | 00:53 |
| Wizzup | so what version do you want in the changelog? | 00:53 |
| uvos | ex 6.1.67.1-1 | 00:54 |
| Wizzup | it's 6.6.x | 00:54 |
| uvos | 6.1.67 is the upstream version .1 is the second code revision of our patches | 00:54 |
| Wizzup | but I don't know what stable release you rebased upon | 00:55 |
| uvos | its just so we can bump the version without it going out of sync with upstream | 00:55 |
| uvos | https://github.com/maemo-leste/droid4-linux/blob/6852f3753c06ae2ad1eef2e1f25441a89b802bcf/Makefile#L4 | 00:56 |
| Wizzup | 6.6.29.0- then? | 00:57 |
| Wizzup | 6.6.29.0-1 then? | 00:57 |
| uvos | jup | 00:58 |
| Wizzup | NAME = Hurr durr I'ma ninja sloth | 00:59 |
| Wizzup | I forgot about this one | 00:59 |
| uvos | dem do be silly | 00:59 |
| uvos | best one is still 3.11.0 linux for workgroups | 00:59 |
| Wizzup | hehe | 01:00 |
| Wizzup | ok so the hope is that apart from d4 audio calls, this 6.6 works ok? | 01:00 |
| uvos | i mean i have it on my d4 | 01:01 |
| uvos | and yes | 01:01 |
| uvos | works fine besides that | 01:01 |
| uvos | at least on d4 | 01:01 |
| uvos | ts issue on n900 might be because of your patches as you say | 01:01 |
| uvos | which are included | 01:01 |
| Wizzup | I think we already included them before, but I am not sure | 01:02 |
| Wizzup | it's building now, I might make a future experimental build with the regmap writable | 01:02 |
| uvos | sure | 01:02 |
| arno11 | Wizzup: btw most arm64 devices are probably powerful enough to run almost all emulators through RetroArch (even if it is a pita to configure) | 11:46 |
| arno11 | at least diejuse ran generic pcsx easely in chroot iirc | 11:47 |
| Wizzup | arno11: do you use OMP on the n900? | 14:49 |
| arno11 | Wizzup: nope i don't like it (even on fremantle) | 15:35 |
| arno11 | i prefer mplayer/smplayer | 15:36 |
| arno11 | and audacious for music | 15:36 |
| arno11 | i don't like the way omp works with mafw stuff | 15:37 |
| Wizzup | how do you notice that in the user experience? | 15:39 |
| Wizzup | in any case I'm using it now and it works ok for me, but my n900 in general is pretty slow still | 15:39 |
| arno11 | ah ok. from a user pov, mafw is too slow for n900 | 15:40 |
| arno11 | and the fact that you can't really choose what is really playable or not is a problem for me | 15:41 |
| arno11 | btw we can have a look on what is still slowing down your n900 | 15:49 |
| Wizzup | what do you mean, what is playable or not? | 16:01 |
| Wizzup | arno11: appreciate the help in checking, I'm currently deep into some work thing | 16:01 |
| Wizzup | but I tested the latest 6.6 on my n900 and it works ok | 16:01 |
| Wizzup | (still playing music with it) | 16:01 |
| Wizzup | didn't test call audio, but it's uvos latest branch now | 16:01 |
| Wizzup | so you might want to give it a swing | 16:01 |
| arno11 | ah ok cool | 16:01 |
| arno11 | playable or not: i meant lot of audio/video formats are not tracked iirc | 16:04 |
| Wizzup | if they are not we shoul dtry to fix that over time | 16:06 |
| Wizzup | I personally really like OMP | 16:06 |
| arno11 | ok, btw i forgot to mention that n900 is very slow/unusable when mafw tracker is running (ofc if there is lot of media) | 16:08 |
| arno11 | same in fremantle if i let my leste sd card in the slot btw | 16:09 |
| arno11 | bbl | 16:15 |
| Wizzup | yes, all devices will be of course | 17:13 |
| Wizzup | but it doesn't run often at all | 17:13 |
| arno11 | yes indeed | 17:56 |
| arno11 | i forgot the main issue with omp on N900: cpu and power usage | 17:57 |
| arno11 | power usage is 2-3 times higher than audacious for music | 17:58 |
| arno11 | around 100mA screen off with audacious, around 200 with omp on N900 iirc | 18:03 |
| arno11 | and cpu usage makes multitasking difficult | 18:05 |
| arno11 | i wonder why there is so much diff | 18:06 |
| arno11 | anyway we all have different favorite apps for different reasons :) | 18:08 |
| dsc_ | nioCat: welcome :) | 18:23 |
| nioCat | meow | 18:24 |
| kona_ | Wizzup: i haven't tried this yet on my 900 but might consider configuring any background activity to be nice(1) and starting any cpu-bound jobs with nice as well. | 19:54 |
| kona_ | may help with the issues arno11 was noting about responsiveness. | 19:54 |
| kona_ | it helped a bit on my n810 back in the day | 19:55 |
| kona_ | for system daemons/services/whatever might consider making that default behavior | 19:55 |
| kona | arno11: re: performance with background tasks running, might try renice -n 10 -g ${pgrp_pid} | 20:42 |
| kona | if you do that for any troublesome background task/service/daemon and use the process group leader pid, it should make foreground stuff feel more responsive. | 20:44 |
| arno11 | yes i already made lot of tests with nice/renice and chrd | 20:47 |
| arno11 | it makes a diff for stuff like phone calls, audio and other stuff. but for heavy daemons like trackers, that's another story. | 20:49 |
| arno11 | imo nice stuff is already not too bad on leste and that's tricky to be sure there is not too much impact on other process/daemons when we modify priorities | 20:54 |
| arno11 | but again that's just my user opinion | 20:55 |
| arno11 | btw if we implement new transitions and no tracker in $HOME, there is almost no slowness anymore excepting for very few things | 21:00 |
| arno11 | (i mean on n900) | 21:03 |
| Wizzup | I do agree tracker should not follow $HOME | 21:20 |
| Wizzup | I forgot what we decided was the best way to solve it | 21:20 |
| Wizzup | you were looking at the gconf schema, did we just want to change the defaults xml? | 21:20 |
| arno11 | i was looking to gconf for apt-worker and indeed we could change the default xml | 21:25 |
| arno11 | for gnome tracker, still don't know what could be the best way | 21:26 |
| arno11 | and if it should be apply on all devices or just n900 | 21:27 |
| Wizzup | we build gnome tracker s owe cna change the default xml | 21:39 |
| arno11 | ah ok | 21:41 |
| arno11 | cool | 21:41 |
| sicelo | kona: still have the N810, and working? | 21:59 |
| kona | sicelo: so, i should have two of them, both working but one of them has a cracked screen. | 22:39 |
| kona | but i haven't seen them since moving in 2015, so idk :) | 22:39 |
| sicelo | :-D | 22:43 |
| sicelo | i think they were beautiful devices | 22:43 |
| Wizzup | I also have them here in some drawers | 22:44 |
| Wizzup | but I already think I'm masochistic enough just to work on the n900 :D | 22:44 |
| kona | i think they felt better in the hand than the n900, but the n900 has better specs for sure. | 22:44 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!