| 00:22.49 | *** join/#maemo infobot (~infobot@rikers.org) |
| 00:22.49 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | DONT FORGET TO VOTE FOR COUNCIL! https://maemo.org/vote/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf ~tabletsdev ~combined ~emmc ~flasher sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog |
| 01:53.08 | *** join/#maemo infobot (~infobot@rikers.org) |
| 01:53.08 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | DONT FORGET TO VOTE FOR COUNCIL! https://maemo.org/vote/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf ~tabletsdev ~combined ~emmc ~flasher sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog |
| 02:25.15 | *** join/#maemo LjL (~ljl@unaffiliated/ljl) |
| 03:22.58 | *** join/#maemo pagurus (~user@p4FDC328A.dip0.t-ipconnect.de) |
| 05:14.12 | *** join/#maemo florian (~fuchs@x4d094d3d.dyn.telefonica.de) |
| 05:51.47 | *** join/#maemo cyteen (~cyteen@cyteen42.plus.com) |
| 06:13.15 | *** join/#maemo dafox (~dafox@92.69.238.236) |
| 06:41.33 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 06:49.55 | *** join/#maemo florian_ (~fuchs@p5DE3C046.dip0.t-ipconnect.de) |
| 07:14.46 | *** join/#maemo xorly (~xorly@ip-86-49-24-93.net.upcbroadband.cz) |
| 07:16.16 | *** join/#maemo err0r3o3_ (~err0r3o3@93-82-157-170.adsl.highway.telekom.at) |
| 07:43.48 | *** join/#maemo florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 07:44.26 | *** join/#maemo mike727 (d31f1b25@gateway/web/freenode/ip.211.31.27.37) |
| 07:56.00 | *** join/#maemo L29Ah (~L29Ah@31.173.81.18) |
| 08:02.22 | *** join/#maemo Kabouik (~kabouik@129.242.224.29) |
| 08:06.14 | *** join/#maemo eMHa (~mh@81.26.162.98) |
| 08:38.51 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 08:49.14 | *** join/#maemo qwazix (~qwazix@Maemo/community/ex-council/qwazix) |
| 08:50.31 | *** join/#maemo Sicelo009N (~sicelo@unaffiliated/sicelo) |
| 08:54.19 | Sicelo009N | so from what i understood from freemangordon's explanantion, iphbd is responsible for queuing data for transmission via network. is it possible to tweak/adjust its parameters, e.g. how often it sends? |
| 08:55.16 | Sicelo009N | DocScrutinizer51: perhaps you could change /topic in connection with voting :-) |
| 08:59.25 | *** join/#maemo qwazix (~qwazix@Maemo/community/ex-council/qwazix) |
| 09:03.10 | *** join/#maemo Kabouik (~kabouik@129.242.224.29) |
| 09:03.50 | *** join/#maemo Kabouik (~kabouik@129.242.224.29) |
| 09:07.11 | *** join/#maemo silviof (~silviof@unaffiliated/silviof) |
| 09:31.11 | *** join/#maemo Sicelo009N (~sicelo@unaffiliated/sicelo) |
| 09:32.55 | Sicelo009N | another unexpected reboot ... swap on uSD not helping |
| 09:37.12 | Sicelo009N | if i didn't love the N900 so much, I'd trash it |
| 09:39.32 | Sicelo009N | uninstalled cvm/phoneme now (although i've had it before with no issues) |
| 09:40.09 | Wizzup | I use my N900 mostly for calls/sms, casual browsing and (mostly!) xterm+ssh |
| 09:40.14 | Wizzup | Sometimes I use recaller |
| 09:40.35 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 09:41.25 | Sicelo009N | for me it's everything :-) |
| 09:43.35 | mike727 | can you do load speaker with recaller? When I try, I have an echo. I guess it doesn't do sound cancelation like how the phone prevent's feedback during a call. |
| 09:45.39 | L29Ah | buy a few n900s and switch them when they break |
| 09:45.52 | mike727 | The n900 was my first phone, had it for 2 years. For me, it's a hassle to install programs, but I still love it. I was stunned when I first figured out FMTX, so awesome. |
| 09:46.20 | mike727 | Number 4 is on the way |
| 09:46.29 | Sicelo009N | L29Ah: unfortunately can't find any this side :-( |
| 09:47.29 | L29Ah | ebay? |
| 09:49.16 | mike727 | Yes, was unexpected; no one else had bid. I laughed a few months ago seeing one going up so high with the bidding frenzy. Still worth every penny. |
| 09:51.43 | mike727 | I'm guessing people had a break from ebay after the site-wide 20% off. So there was less people to find it. |
| 09:54.54 | mike727 | *155 off promotion |
| 09:55.00 | mike727 | **15% |
| 09:56.15 | Wizzup | Sicelo009N: well, I usually have a laptop with me... :) |
| 09:57.21 | Sicelo009N | :-) |
| 09:57.23 | *** mode/#maemo [+o DocScrutinizer05] by ChanServ |
| 09:57.36 | *** topic/#maemo by DocScrutinizer05 -> Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf ~tabletsdev ~combined ~emmc ~flasher sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 09:57.50 | *** mode/#maemo [-o DocScrutinizer05] by ChanServ |
| 10:01.02 | DocScrutinizer05 | mike727: revcaller works great for me, since years and 1000s of calls |
| 10:01.12 | DocScrutinizer05 | recaller even |
| 10:01.33 | DocScrutinizer05 | only nasty thing: it breaks completely when storage full |
| 10:01.49 | mike727 | On "load speaker" ? |
| 10:01.55 | DocScrutinizer05 | settings are a tad tricky |
| 10:02.08 | Sicelo009N | i also remember it evidently had a memleak of sorts .. |
| 10:02.09 | DocScrutinizer05 | yes |
| 10:02.21 | DocScrutinizer05 | does it? |
| 10:02.49 | mike727 | I need some initiative to learn :) |
| 10:03.49 | Sicelo009N | i remember mention of that. iirc even the dev decided to produce orecchiette instead. i could be mistaken .. it's a while a go |
| 10:03.52 | Sicelo009N | *ago |
| 10:04.10 | DocScrutinizer05 | I remember I had some unexpected results from "source" setting |
| 10:05.01 | DocScrutinizer05 | wellllllll, recaller is a hildon desktop applet, seems they *all* memleaked at time |
| 10:05.14 | Sicelo009N | true :-) |
| 10:06.09 | DocScrutinizer05 | one of the worst design decisions in maemo5: desktop applets all being one process |
| 10:07.38 | DocScrutinizer05 | mike727: you got CSSU? |
| 10:10.07 | mike727 | Currently, I'n not sure. I think I installed it before on one of them. |
| 10:10.24 | DocScrutinizer05 | you should get CSSU! |
| 10:10.45 | DocScrutinizer05 | it fixes a *lot* of issues, like the memleaks Sicelo009N mentioned |
| 10:10.59 | *** join/#maemo enyc (~enyc@muddle.enyc.org.uk) |
| 10:11.53 | mike727 | Yes, of course. Thank you. Some people need to be told to step out of the fire. |
| 10:12.10 | mike727 | lol\ |
| 10:19.10 | DocScrutinizer05 | Sicelo009N: btw you ever used saera? I installed it just recently and was amazed how flawlessly it installed |
| 10:19.29 | DocScrutinizer05 | and of course of the T2S |
| 10:19.43 | DocScrutinizer05 | had no chance yet to really test it |
| 10:20.14 | DocScrutinizer05 | but it's using pocketsphinx, incredible |
| 10:20.24 | Wizzup | Works on maemo? |
| 10:20.33 | DocScrutinizer05 | seems so |
| 10:21.36 | DocScrutinizer05 | though I guess pocketsphinx must have evolved into another galaxy since then |
| 10:22.24 | DocScrutinizer05 | *maybe* the old pocketsphinx is even better suited for N900 |
| 10:22.42 | DocScrutinizer05 | recent versions might need octocore ;-P |
| 10:23.01 | Wizzup | not sure what I'd use it for, but fun |
| 10:23.08 | Wizzup | wonder how much battery it eats |
| 10:23.14 | DocScrutinizer05 | yeah |
| 10:23.49 | DocScrutinizer05 | that been actually a little... suspicious |
| 10:24.15 | DocScrutinizer05 | though afaik it needs activation via buttonpress |
| 10:24.28 | DocScrutinizer05 | doesn't listen all the time |
| 10:24.35 | DocScrutinizer05 | not sure about that though |
| 10:25.23 | DocScrutinizer05 | anyway it been smarter back when ("AI") than alexa is today X-P |
| 10:25.30 | *** join/#maemo drcode (~drcode@5.29.192.15) |
| 10:26.11 | DocScrutinizer05 | and YOU control the AI |
| 10:26.18 | DocScrutinizer05 | completely |
| 10:26.31 | Wizzup | yeah, I just have no use for it |
| 10:26.38 | DocScrutinizer05 | unlike friggin alexa and friends |
| 10:26.52 | Wizzup | what I mostly just need is an easy way to record some thoughts or ideas I have (audio rec), and then be able to sort them in a simple manner |
| 10:27.08 | DocScrutinizer05 | well, making calls while driving scooter was a start for example |
| 10:27.11 | ceene | grepping voice and real life conversations :) |
| 10:27.55 | *** join/#maemo TheKit (~nekit@85-95-179-56.saransk.ru) |
| 10:29.03 | DocScrutinizer05 | I think saera and mappero/whatever should get beaten into shape to be on par with damn android google "Drive" |
| 10:29.46 | DocScrutinizer05 | say destination, get voice directions |
| 10:30.16 | DocScrutinizer05 | say contact names to make a call |
| 10:30.21 | Wizzup | I don't think that's easy |
| 10:30.42 | DocScrutinizer05 | #1 for sure not, except for a few well known destinations |
| 10:31.19 | DocScrutinizer05 | you (err pocketsphinx) wouldn't know how to spell the street names correctly |
| 10:32.24 | *** join/#maemo jskarvad (jskarvad@nat/redhat/x-ccskyozfpxxykpfi) |
| 10:32.24 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 10:33.40 | *** join/#maemo Kabouik (~kabouik@129.242.224.30) |
| 10:34.58 | Wizzup | do you know a current drive app helper that works? |
| 10:35.11 | Wizzup | I haven't really found any that can actually calculate routes, and def. not with up to dat emaps |
| 10:35.16 | Wizzup | I mostly just rely on gps |
| 10:35.21 | Wizzup | either with maep or cloudgps |
| 10:35.34 | Wizzup | [one of them always crashes when searching for placs] |
| 10:35.36 | Wizzup | places |
| 10:38.27 | *** join/#maemo enyc (~enyc@muddle.enyc.org.uk) |
| 10:39.48 | *** join/#maemo enyc (~enyc@muddle.enyc.org.uk) |
| 10:41.31 | mike727 | modRama is still actively being developed. No offline routing yet. |
| 10:42.05 | mike727 | *modRana |
| 10:44.14 | Wizzup | ah that seems pretty active yeah |
| 10:47.00 | mike727 | The menus a bit confusing to me, too many options. |
| 10:47.22 | mike727 | *are |
| 10:53.04 | mike727 | Any N9 folk here? : Zerorize flash failed (due to downgrade). Phone refuses to attempt flash (basic & Zerorize). The flasher does Identify the phone (bootloader good?). Should I reboot or Cold flash? |
| 10:53.18 | KotCzarny | nope. they are on #harmattan |
| 10:54.23 | mike727 | yep, sorry. Seems like only tumble weeds there. |
| 10:54.43 | KotCzarny | figures. ;) |
| 10:54.49 | KotCzarny | maemo ftw! |
| 10:56.42 | mike727 | If I get it working, will give it to my little sister, when see says all the other kids at school have phones. It's nice in white. |
| 10:58.34 | KotCzarny | kids shouldnt have phones till 12-14yo |
| 10:58.47 | KotCzarny | it breakes their social skills learning |
| 10:59.04 | KotCzarny | which is sad and changes the future world to the worse one |
| 11:00.48 | mike727 | certainly. Got my first phone at 20, 2 years ago. Did feel a bit left out during high school. |
| 11:01.36 | mike727 | It's crazy seeing school kids who have evidently beat there parents into buying them the latest iphone |
| 11:02.35 | Sicelo009N | DocScrutinizer05: re-saera - no. although i did read the specs and it seems awesome |
| 11:03.35 | mike727 | One parent I talked to who has kids ~10yrs old, said she has too, becase all the other parents buy it for their kids. |
| 11:06.31 | Sicelo009N | mike727: for me Ovi Maps works awesome |
| 11:08.34 | mike727 | offline routing ? Awhile back, it didn't want to follow my location. |
| 11:10.15 | mike727 | Sicelo009N: original stock? |
| 11:12.22 | Sicelo009N | yes |
| 11:13.41 | Sicelo009N | only think stock can't do is offline search. offline routing works ootb. then of course, main other problem is updated map tiles |
| 11:14.44 | Sicelo009N | *thing |
| 11:16.21 | mike727 | offline routing is made to work by 'out of the box' ? Meaning CSSU ? |
| 11:16.57 | *** join/#maemo sunshavi (~user@190.234.106.113) |
| 11:17.39 | Sicelo009N | even in non-ccsu :) |
| 11:18.17 | Sicelo009N | just you don't easily notice due to ovi maps requesting connection as sson as it launches |
| 11:19.00 | mike727 | is there a difference between 'stock' & 'ootb' ? |
| 11:19.33 | Sicelo009N | no |
| 11:20.38 | Sicelo009N | sorry for confusing .. in simpler terms - the Ovi Maps already on your N900 is able to do offline routing. you don't need to do anything special to achieve that |
| 11:21.38 | mike727 | thanks will have to give it a go. :) |
| 11:23.14 | Sicelo009N | problem will be the outdated maps if your area changes fast. where i am - they are still at leat 95% correct |
| 11:25.58 | mike727 | For map updates did you need to change a setting, something like: supl.nokia.com ? |
| 11:28.31 | Sicelo009N | that is not realted to any maps application. that's system-wide gps setting used for all location-aware applications. supl.nokia.com will only work if you have the latest certificate-related packages (see a-gps thread on tmo) |
| 11:30.47 | mike727 | Likely why I've had problems ? Thank you. I guess when I last looked at it, I was too lazy to try and understand it's importance. |
| 11:33.24 | Wizzup | Sicelo009N: ovi maps for me is mostly heavily outdated maps |
| 11:33.27 | Wizzup | do they get updated still? |
| 11:33.30 | Wizzup | or do your roads just not change :) |
| 11:34.22 | Sicelo009N | yes not much changes here :p |
| 11:40.21 | *** join/#maemo enyc (~enyc@muddle.enyc.org.uk) |
| 11:42.12 | Sicelo009N | re - mappero ... interesting that mike727 has roughly ame problem with menu/ui. i've also found it a difficult application to use. of course, i do appreciate the effort! |
| 11:42.26 | Sicelo009N | s/mappero/modrana/ |
| 11:44.34 | mike727 | Yes, its great work. It looks like they have got offline routing working as well https://wiki.maemo.org/ModRana_offline_routing_guide |
| 11:52.39 | *** join/#maemo jpb22 (4f429618@gateway/web/freenode/ip.79.66.150.24) |
| 11:53.26 | jpb22 | Hi all, trying to get in touch with maemo.org admin, but contact@maemo.org bounces... does anyone have a contact point? Thanks |
| 12:00.36 | merlin1991 | jpb22: this is a good contact point |
| 12:01.02 | merlin1991 | what kind of admin are you searching, forums, mail, website, repository? |
| 12:02.22 | jpb22 | merlin1991: website, technically speaking. My forum account was deleted some time ago, but the profile remains and I have no access to modify or remove it. |
| 12:02.40 | jpb22 | I would paste the url but since everything here is publicly logged, it would be somewhat self defeating |
| 12:03.09 | merlin1991 | ah so garage then |
| 12:03.12 | merlin1991 | I can do that |
| 12:03.12 | jpb22 | (since I am looking to remove it due to privacy concerns) |
| 12:03.40 | merlin1991 | pm me the old nick |
| 12:03.53 | jpb22 | awesome, sure thanks |
| 12:10.01 | *** join/#maemo xy2_ (~xy2_@220.245.16.93.rev.sfr.net) |
| 12:30.21 | *** join/#maemo jpb22 (4f429618@gateway/web/freenode/ip.79.66.150.24) |
| 12:51.31 | Sicelo009N | oh nice ... can get iphbd to operate in debug mode |
| 13:05.40 | *** join/#maemo xy2_ (~xy2_@220.245.16.93.rev.sfr.net) |
| 13:07.10 | *** join/#maemo xy2_ (~xy2_@220.245.16.93.rev.sfr.net) |
| 15:02.05 | *** join/#maemo th652 (~user@188.29.164.131.threembb.co.uk) |
| 15:10.01 | *** join/#maemo LauRoman (~LauRoman@5-14-29-237.residential.rdsnet.ro) |
| 15:17.03 | *** join/#maemo Vajb (~Vajb@85-76-42-250-nat.elisa-mobile.fi) |
| 15:17.14 | *** join/#maemo xy2_ (~xy2_@220.245.16.93.rev.sfr.net) |
| 15:25.29 | *** join/#maemo LauRoman|Alt (~LauRoman@5-14-29-237.residential.rdsnet.ro) |
| 15:32.24 | *** join/#maemo th652 (~user@host81-147-143-12.range81-147.btcentralplus.com) |
| 15:39.16 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 15:44.05 | *** join/#maemo Vajb (~Vajb@85-76-42-250-nat.elisa-mobile.fi) |
| 15:47.18 | *** join/#maemo Kabouik (j0n@ks3100825.kimsufi.com) |
| 15:47.36 | *** join/#maemo louisdk (~louisdk@static-5-103-138-205.fibianet.dk) |
| 15:51.06 | *** join/#maemo Vajb (~Vajb@85-76-42-250-nat.elisa-mobile.fi) |
| 16:06.47 | *** join/#maemo Kabouik_ (~kabouik@32.232.202.84.customer.cdi.no) |
| 16:08.43 | *** join/#maemo Vajb (~Vajb@85-76-42-250-nat.elisa-mobile.fi) |
| 16:14.25 | *** join/#maemo th652 (~user@host81-147-143-43.range81-147.btcentralplus.com) |
| 16:22.47 | *** join/#maemo eMHa (~mh@p200300738E025000267703FFFE6CC360.dip0.t-ipconnect.de) |
| 18:25.23 | *** join/#maemo infobot (~infobot@rikers.org) |
| 18:25.23 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf ~tabletsdev ~combined ~emmc ~flasher sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 18:31.52 | *** join/#maemo Sicelo009N (~sicelo@unaffiliated/sicelo) |
| 18:33.03 | *** join/#maemo cyteen (~cyteen@cyteen42.plus.com) |
| 18:41.37 | *** join/#maemo Vajb (~Vajb@85-76-42-250-nat.elisa-mobile.fi) |
| 18:46.48 | freemangordon | Sicelo009N: well, you can even compile it with debug symbols :) |
| 18:47.20 | freemangordon | https://github.com/community-ssu/iphbd |
| 18:55.45 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 19:01.15 | *** join/#maemo Vajb (~Vajb@85-76-42-250-nat.elisa-mobile.fi) |
| 19:01.59 | Sicelo009N | :-) |
| 19:04.36 | DocScrutinizer05 | freemangordon: re kernel servie livetime: ever checked centos? |
| 19:05.39 | DocScrutinizer05 | seems LTS support for 2.6.32(?) kernel until 2020 at least |
| 19:09.06 | freemangordon | could be, but that doesn;t help us much for maemo |
| 19:09.18 | DocScrutinizer05 | hmm, the patches should apply cleanly, no? |
| 19:10.03 | freemangordon | I guess there is a difference between 2.6.28 and 2.6.32 |
| 19:10.03 | DocScrutinizer05 | there for sure is |
| 19:10.09 | freemangordon | but sure, usually they can be backported |
| 19:10.22 | DocScrutinizer05 | but way less than between 2.6.28 and 4.x.x |
| 19:17.14 | *** join/#maemo Vajb (~Vajb@85-76-42-250-nat.elisa-mobile.fi) |
| 19:19.09 | DocScrutinizer05 | kernel LOC 10,118,757(2.6.28)->12,532,667(2.6.32) |
| 19:19.24 | DocScrutinizer05 | doesn't say how much changed, of course |
| 19:20.03 | KotCzarny | what about .28->.29 ? |
| 19:22.42 | enyc | does it make sense to backport patches... |
| 19:22.55 | enyc | rather, forward-port maemo patches//drivers to 2.6.32 instead? |
| 19:23.49 | KotCzarny | sure, as long you dont hit roadblocks in blobs |
| 19:24.16 | enyc | not forgetting any security-fixes that came along in kernel 2.6.28 -> 2.6.32 diff itself anyway... let alone 'since then' |
| 19:26.03 | enyc | also, i wonder if stretch//ascii libc6 etc is 'compatible' with 2.6.32 -- my experience is jessie can work on 2.6.32 though differences in xorg/video/udev sorts of things can be a problem depending on config/usage |
| 19:27.03 | enyc | KotCzarny: has anybody made a diff of 2.6.28 'stock' and 2.6.28 'maemo/power' kernel anyway?? |
| 19:28.02 | KotCzarny | you can do it yourself, maemo's kernel source is available |
| 19:28.25 | enyc | KotCzarny: righ,t where? but in any case i was wondering how much this had been ''investigated'' already you see |
| 19:28.43 | enyc | I don't have an online arm box i can rebuild tese things from hrrm |
| 19:29.07 | enyc | though, is that kernel normally compiled on intel using the maemo dev enviroment DocScrutinizer05 pointed out ??? |
| 19:29.13 | enyc | with arm crosscompilation |
| 19:29.19 | KotCzarny | yes. |
| 19:30.07 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 19:33.47 | DocScrutinizer05 | https://www.linuxfoundation.org/search/Annual%20Linux%20Development%20Report |
| 19:35.16 | DocScrutinizer05 | To download the full report, please visit The Linux Foundationâs Publicationâs website at: https://www.linuxfoundation.org/publications/linux-foundation/who-writes-linux-2015 |
| 19:41.50 | DocScrutinizer05 | http://wstaw.org/m/2017/07/14/plasma-desktopzz8317.png |
| 19:42.11 | DocScrutinizer05 | ~die |
| 19:44.01 | *** join/#maemo infobot (~infobot@rikers.org) |
| 19:44.01 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf ~tabletsdev ~combined ~emmc ~flasher sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 19:51.12 | DocScrutinizer05 | ~status |
| 19:51.12 | infobot | Since Fri Jul 14 19:42:33 2017, there have been 0 modifications, 0 questions, 0 dunnos, 0 morons and 0 commands. I have been awake for 8m 39s this session, and currently reference 119688 factoids. I'm using about 78824 kB of memory. With 0 active forks. Process time user/system 1.85/0.03 child 0/0 |
| 19:54.21 | enyc | KotCzarny: can't see the amemo source / building instructions on the wiki.... |
| 19:54.56 | enyc | KotCzarny: and i'd rather have talked with Pali or so first if they are still contactable! |
| 19:54.56 | KotCzarny | do you know the basics of debian packaging/building ? |
| 19:54.56 | enyc | KotCzarny: or whoever it is whose already familiar with patching the power kernel so far |
| 19:55.21 | enyc | KotCzarny: I think so, but I may not be best choice as to person to spend lots of time on it |
| 19:55.42 | DocScrutinizer05 | keeping kernel and core system of *maemo* in a working status is one thing. Porting packahes to maemo though is another one, until recently you could basically just re-compile any debian package for maemo and fine (leave aside needed adaptions for hildon). Since systemd this doesn't apply anymore to an increasing number of packages. That's where devuan comes in, as the distro that continues to be what debian was |
| 19:57.39 | DocScrutinizer05 | of course you also can port old maemo packages to modern devuan, but the result isn't a devuan system but a debian/devuan system with maemo 'apps' |
| 19:58.08 | DocScrutinizer05 | S/isn't a devuan/isn't a *maemo*/ |
| 19:59.11 | DocScrutinizer05 | of course you also can port old maemo packages to modern devuan, but the result isn't a *MAEMO* system (incl all the core system twekas to make it perform excellent in a phone environment) but a debian/devuan system with maemo 'apps' |
| 20:00.08 | *** join/#maemo Vajb (~Vajb@85-76-42-250-nat.elisa-mobile.fi) |
| 20:02.17 | enyc | DocScrutinizer05: if core or maemo patched including kernel bumped to 2.6.32 LTS (worth trying if not too hard imho), will devuan stretch armhf chroot work on that kernel ? especially is libc6 backwards-compatible-enough ? |
| 20:03.54 | DocScrutinizer05 | that's a too complex question for me to answer. sorry |
| 20:04.22 | enyc | debian/devuan jessie, so far as I can tell, works with minimum 2.6.32 kernel |
| 20:07.26 | DocScrutinizer05 | I'm pretty sure any devuan stuff can run in a carefully crafted chroot or other container or virtulization under maemo |
| 20:08.24 | enyc | for jessie, libc6 has to be 'patched' (minimally) to 'allow' 2.6.28 (simple comparison check) |
| 20:08.57 | DocScrutinizer05 | libc6 in container just needs to play nice with the old kernel we have. You can ensure this since we have source of both the kernel and the libc6 |
| 20:09.25 | enyc | since this is simply changing '32' to '28' in a version-check, i wonder if the devuan libc6 maintainer would be happy to carry that patch in devuan, as its' harmless to everobyd else running newer kernels anyway, in my view. |
| 20:09.35 | DocScrutinizer05 | this is really sytsem development 101 |
| 20:09.46 | enyc | i.e. not need custom build / rebuild on every security update, etc etc |
| 20:10.04 | *** join/#maemo L29Ah (~L29Ah@31.173.81.18) |
| 20:39.47 | enyc | oh, devuan doesn't override glibc package anyawy, hrrm |
| 20:46.42 | *** join/#maemo Vajb (~Vajb@85-76-42-250-nat.elisa-mobile.fi) |
| 20:48.56 | *** join/#maemo dafox (~dafox@92.69.239.110) |
| 21:11.51 | *** join/#maemo Vajb (~Vajb@85-76-42-250-nat.elisa-mobile.fi) |
| 21:28.34 | *** join/#maemo Kilroo (~Kilroo@cpe-71-71-97-50.triad.res.rr.com) |
| 21:40.40 | *** join/#maemo Vajb (~Vajb@85-76-42-250-nat.elisa-mobile.fi) |
| 21:47.21 | Maxdamantus | 07:19:09 < DocScrutinizer05> kernel LOC 10,118,757(2.6.28)->12,532,667(2.6.32) |
| 21:47.27 | Maxdamantus | <PROTECTED> |
| 21:47.47 | Maxdamantus | (git diff --stat v2.6.28 v2.6.32) |
| 21:48.20 | *** join/#maemo Vajb (~Vajb@85-76-42-250-nat.elisa-mobile.fi) |
| 21:49.08 | enyc | Maxdamantus: what about 2.6.28 'stock' to maemo-power 2.6.28 ? |
| 21:49.50 | Maxdamantus | 1321 files changed, 339414 insertions(+), 10614 deletions(-) |
| 21:50.01 | Maxdamantus | oh wait, that's not -power |
| 21:50.20 | Maxdamantus | That's difference between mainline 2.6.28 and stock maemo 2.6.28 |
| 21:50.24 | enyc | Maxdamantus: more to the point, WHICH 2.6.28 version EXACTLY was maemo's kernel based on |
| 21:50.37 | enyc | Maxdamantus: is there 2.6.28.1 2.6.28.2 sort of thing, or does it not work like that ?? |
| 21:50.57 | Maxdamantus | mainline 2.6.28 to -power53 is: 2010 files changed, 374761 insertions(+), 15117 deletions(-) |
| 21:51.45 | Maxdamantus | I guess I can keep comparing the patch releases to find which one is most similar. |
| 21:51.59 | enyc | Maxdamantus: yes please =) kernel.org has 2.6.28 upto 2.6.28.10 |
| 21:52.21 | enyc | Maxdamantus: though does the maemo source just have a release/makefile with the extraversion in it |
| 21:54.38 | Maxdamantus | The initial v2.6.28 release seems to be closest. |
| 21:54.59 | Maxdamantus | https://gist.github.com/Maxdamantus/f2deb46fd06a4b819c292e901c66546c |
| 21:55.45 | Maxdamantus | (the diff is from mainline to maemo 2.6.28 |
| 21:55.45 | Maxdamantus | enyc: no. It has other changes too. |
| 21:56.43 | Maxdamantus | Hm, there's a debian/changelog in my maemo tree with 14k lines in it though. |
| 21:57.03 | Maxdamantus | So just subtract around 15k from all of those "insertions" counts. |
| 21:58.04 | Maxdamantus | Hm. There are also additions under Documentation/arm/OMAP/, so maybe it's actually a fork of some omap branch somewhere. |
| 21:58.33 | enyc | Maxdamantus: post patch/list ?? |
| 21:58.45 | enyc | Maxdamantus: i wonder how much is actually very much patches, and how much is just inserting huge piles of new drivers etc etc... |
| 21:58.54 | Maxdamantus | https://gist.github.com/Maxdamantus/43ab8cefdb22179ff4d36e640cfb96ff |
| 21:59.44 | Maxdamantus | Random modifications to a bunch of the fs drivers further suggests it's not a direct fork from mainline 2.6.28 |
| 22:01.21 | enyc | Maxdamantus: hrrm yes looking myself toooo puzzling |
| 22:01.31 | enyc | Maxdamantus: i wonder whats going on |
| 22:02.37 | enyc | Maxdamantus: that said, key is just to pickout whats' needed atop 2.6.32-latest 'stock' and see if that patches relatively cleanly..... |
| 22:09.37 | enyc | that said, looks like kernel changes to 2.6. 29 30 31 32 added lots of OMAP support/changes anyway ....... good thing or bad thing |
| 22:12.11 | Maxdamantus | I can't find references to various blobs for the `fs` changes in any commits in my repository other than ones relating to N900. |
| 22:12.36 | enyc | humm err arr err |
| 22:12.36 | Maxdamantus | Wonder if kernel.org has a way to search for blobs in .. all repositories .. probably not. |
| 22:12.44 | enyc | dont quit e understand implication |
| 22:13.16 | Maxdamantus | Well, eg: `git rev-parse n900-2.6.28:fs/ext3/super.c` gives back "f4be66e3d62133a36f5b81714aa5f2b16f26e75b" |
| 22:13.32 | enyc | i'm not familaiar wit that rev-parse |
| 22:13.38 | enyc | what is this telling us? |
| 22:14.01 | enyc | that the 2.6.28 changes can't really be found anywhere? |
| 22:14.20 | Maxdamantus | so the 2.6.28 stock maemo kernel has an fs/ext3/super.c file with that checksum (basically; prepend "blob 84547\0" to teh beginning of the file) |
| 22:14.53 | enyc | so whats the significance of those weird blobs on the beginning? |
| 22:15.09 | Maxdamantus | and I can't see that exact file in any reachable commit in my repository other than the ones I've made from those maemo sources and the branches I've fetched from Pali here. |
| 22:16.02 | Maxdamantus | The significance is that I think it indicates that nokia's changes aren't a direct branch from mainline 2.6.28 |
| 22:16.12 | Maxdamantus | and that there's probably another development branch somewhere that they used. |
| 22:16.35 | Maxdamantus | unless they themselves actually did those modifications to `fs` .. I guess that could be plausible, depending on what the changes aro. |
| 22:18.37 | enyc | yes, dothey look significant? |
| 22:19.07 | enyc | i'm thinking .... git // work-in-progress befre 2.6.28 itself released ? |
| 22:20.07 | Maxdamantus | Hm. Some of the changes seem to be from after 2.6.30. |
| 22:20.42 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:1:7061:3b2a:37df:ded3) |
| 22:22.53 | Maxdamantus | eg, the changes include those from commit 85c7859190c4197a7c34066db14c25903c401187, which is in the mainline master branch, based on v2.6.30-rc8 |
| 22:23.09 | enyc | http://elinux.org/N900#Kernel_git_repository_for_N900 |
| 22:23.48 | enyc | seems to suggest couldn't JUST use a latest 4.12 kernel compile right with old maemo because dsp//powervr drivers |
| 22:24.31 | Maxdamantus | Right, but I think you can use that 4.xx branch to run Maemo. |
| 22:24.37 | Maxdamantus | It's just not compatible with mainline. |
| 22:24.48 | enyc | what you mean? |
| 22:24.53 | enyc | to run stock maemo ?? |
| 22:25.00 | enyc | or slow because driver missing? |
| 22:25.05 | enyc | *confused* |
| 22:25.28 | Maxdamantus | I think you're meant to be able to use https://github.com/pali/linux-n900 to run stock Maemo. I might be mistaken. |
| 22:26.05 | Maxdamantus | has only tried a 3.18 or something kernel from there a year or two ago, and didn't try running stock Maemo. |
| 22:26.13 | Maxdamantus | actually, 3.14 |
| 22:26.27 | enyc | will pali just tell us what the expected state is?!?!? |
| 22:27.03 | enyc | fwiw, http://people.canonical.com/~mpoirier/n900/2.6.35.10/patches/ <- interesting |
| 22:28.27 | Pali | what is the problem? |
| 22:30.50 | *** join/#maemo navtis (~ircchatte@81.2.83.123) |
| 22:30.53 | enyc | Pali: we'd like to know (a) what the limitainso of stock-maemo with a 4.12 etc n900 kernel latest are |
| 22:31.40 | Pali | HW support/kernel drivers is in table on http://elinux.org/N900 |
| 22:31.51 | Pali | you can find in which version was what introduced in mainline kernel |
| 22:31.58 | enyc | Pali: yes, i see 2 red blobs, what practiceal problems that causes? |
| 22:32.09 | enyc | Pali: tidspbridge and PowerVR won't be workable ? |
| 22:32.32 | enyc | Pali: is that it? does that make stock maemo fail because driver unavailable? |
| 22:32.45 | Pali | if you want to run Maemo, look at steps: http://wiki.maemo.org/Porting/Kernel |
| 22:33.02 | Pali | -n900 branches in my git tree contains some patches |
| 22:33.05 | enyc | oooooooooooooh |
| 22:33.26 | Pali | there is ported PowerVR driver |
| 22:33.43 | Pali | fixes for wifi |
| 22:33.54 | Pali | maemo compatibility layer (where still needed) |
| 22:34.38 | Pali | no idea if bluetooth is working... |
| 22:35.07 | Pali | patches for camera are not (finished) in my git repo |
| 22:35.17 | Pali | and tidspbride does not work at all |
| 22:35.39 | enyc | i see didn't know all this |
| 22:36.43 | enyc | whats' the tidspbridge used for? |
| 22:36.49 | Pali | pavelm now playing with camera, so we can expect working camera in new+1 or +2 mainline kernel version |
| 22:37.10 | enyc | i see i see |
| 22:37.17 | enyc | so a workable kernel is well on way...? |
| 22:37.48 | Pali | tidspbridge is bridge driver for TI DSP processor |
| 22:37.57 | enyc | yes, but whats that used for? |
| 22:38.47 | Pali | DSP processor used e.g. for video encoding/decoding |
| 22:39.08 | Pali | maybe there are also applications which uses it for audio |
| 22:39.15 | Pali | or other multimedia processing |
| 22:39.43 | Pali | do not know who else uses DSP in Maemo... if there are more applications in Maemo-Extras |
| 22:42.04 | enyc | right |
| 22:43.20 | enyc | talking of wifi, is WPA host / 'hostapd' ever a possibility with that adapter? |
| 22:45.02 | Pali | theoretically with software implementation |
| 22:45.39 | sunshavi | pali: Sebastian Reichel was working on bluetooth. But probably You know that. btw camera is very slow on n900, perhaps pavel version is quicker |
| 22:45.54 | Pali | wifi firmware supports packet injection and monitor mode which should be enough for implementing AP mode |
| 22:46.03 | Pali | wl1251 driver has both support |
| 22:46.22 | Pali | but I do not know any software-based wifi AP implementation |
| 22:47.04 | Pali | IIRC there are some problems with bluetooth on n900, do not know if those problems were fixed or not |
| 22:47.56 | Pali | last time I talked with pavel, he told me that camera for him is working... and I see patches periodically on mailing list |
| 22:48.08 | Pali | so we can expect full-working camera also in mainline |
| 22:50.10 | sunshavi | pali: nice to know |
| 22:53.46 | *** join/#maemo mike727 (d31f1b25@gateway/web/freenode/ip.211.31.27.37) |
| 22:58.36 | *** join/#maemo navtis (~graham@123.83.2.81.in-addr.arpa) |
| 23:10.39 | *** part/#maemo navtis (~graham@123.83.2.81.in-addr.arpa) |
| 23:20.10 | *** join/#maemo th652 (~user@host81-132-35-21.range81-132.btcentralplus.com) |
