IRC log of #maemo-ssu for Wednesday, 2012-11-21

*** infobot has quit IRC00:08
*** _rd has quit IRC00:12
*** mickname has quit IRC00:14
*** mickname has joined #maemo-ssu00:14
*** arcean has quit IRC00:19
*** Senicius_ has joined #maemo-ssu00:20
*** Senicius has quit IRC00:24
*** macmaN has quit IRC00:24
*** macmaN has joined #maemo-ssu00:25
*** Senicius_ is now known as Senicius00:25
*** arcean has joined #maemo-ssu00:29
*** _rd has joined #maemo-ssu00:48
*** trumee has left #maemo-ssu00:56
*** _rd has quit IRC00:57
*** dhbiker has joined #maemo-ssu01:10
*** dhbiker has quit IRC01:11
*** dhbiker has joined #maemo-ssu01:15
*** nox- has joined #maemo-ssu01:36
merlin1991DocScrutinizer05: install testing the regular way, then install http://cdnm.at/~christian/maemo/cssu/testing-testing-enabler_0.1_all.deb and wait for ham to find the update01:46
DocScrutinizer05hmm, might be a tad late today... I'll see01:46
DocScrutinizer05well, I might just start01:47
merlin1991also testing should be applied on top of 1.301:47
DocScrutinizer05:nod:01:47
DocScrutinizer05 booot baby booooooooooooot01:48
DocScrutinizer05*cough* shaking hands01:48
DocScrutinizer05*sigh* and date/time/lang picker01:49
DocScrutinizer0521.2011.38.1, seems OK01:51
DocScrutinizer05?01:51
merlin1991yep01:52
*** Martix has quit IRC01:56
DocScrutinizer05wow, that virdin keymat has a quite different feeling to the typing01:56
DocScrutinizer05ummmmm "testing"01:56
DocScrutinizer05'Community SSU (testing)' - yessir!01:57
DocScrutinizer05OH DAMN, I forgot to do a BM backup! ;-P01:58
DocScrutinizer05Community SSU enabler - yessir01:59
DocScrutinizer05merlin1991: on the "community SSU Agreement" please remove the empty lines so user doesn't have to scroll to see the remaining 2 lines02:01
DocScrutinizer05(which are "After installation, launch the enabler from the menu...")02:01
DocScrutinizer05and should be: "After installation, close this app manager and launch the enabler from the menu..."02:03
DocScrutinizer05fsck u, 11 updates available libqtm-foo-bar02:05
DocScrutinizer05and tv-out-applet02:05
DocScrutinizer05NO SIR!02:05
*** Pali has quit IRC02:06
merlin1991run only the cssu update02:06
merlin1991(includes the rest)02:06
DocScrutinizer05already running - btw in applauncher it's only called "Maemo CSSU"  (no *-enabler)02:06
DocScrutinizer05I hope somebody takes notes and edits stuff accordingly02:07
DocScrutinizer05again, "Maemo5 community SSU pkg 1Tmaemo5.1" and 11 other updates available. Luckily maemo is on top02:08
DocScrutinizer05no backup please02:09
DocScrutinizer0545.9MB download02:09
DocScrutinizer05this *might* take a while02:09
DocScrutinizer05so...02:12
DocScrutinizer05and should be: "After installation, close this app manager and launch the "Maemo SSU" app from the menu..."02:13
DocScrutinizer05offline modus \o/02:13
DocScrutinizer05wiki needs advice to install/update "Maemo 5 Community SSU Packe02:15
DocScrutinizer05package" ONLY02:15
DocScrutinizer05and NOT click "install all"02:16
DocScrutinizer05err "update all"02:16
DocScrutinizer05maybe an according text could even show up in description of "Maemo 5 Community SSU Package"02:17
DocScrutinizer05after "Community SSU package. " before " Includes...."02:17
DocScrutinizer05like: "Maemo 5 Community SSU Package" \n "CLICK HERE and 'OK'. Includes..."02:19
DocScrutinizer05since "Maemo 5 Community SSU Package" \n "Community SSU package. ..." Is a *tad* redundant02:20
DocScrutinizer05"update successfull!" \o/02:20
DocScrutinizer05reboot worked02:21
DocScrutinizer05now do errr, what?02:21
DocScrutinizer05http://cdnm.at/~christian/maemo/cssu/testing-testing-enabler_0.1_all.deb should install from microB, no?02:21
DocScrutinizer05merlin1991: ^^^02:21
merlin1991microb filemanager dpkg -i, whatever you prefer :)02:22
DocScrutinizer05dpkg -i BWAHAHA02:23
DocScrutinizer05DAFAQ!!!02:25
DocScrutinizer05what's wrong with DHCP and dnsmasq on this shit?02:25
merlin1991hm?02:25
DocScrutinizer05cdnm.at can't be found02:25
merlin1991did it reconnect to wireless after the reboot?02:25
DocScrutinizer05yep02:26
DocScrutinizer05but DNS is fubar02:26
DocScrutinizer05google.de not found02:26
DocScrutinizer05*sigh*02:27
DocScrutinizer05I guess it hasn't acquired a new full DHCP lease02:27
DocScrutinizer05just continuing to use the old one, or sth02:27
DocScrutinizer05AHAAAA, di- and re-connecting fixed it02:28
DocScrutinizer05errr, open with HAM?02:29
DocScrutinizer05iirc this never worrked, right?02:29
DocScrutinizer05works02:30
DocScrutinizer05ok, installed, what's next?02:31
DocScrutinizer05and wait for ham to find the update02:31
DocScrutinizer05mhm02:31
merlin1991wait for ham to run its equivalent of apt-get update and then look at the updates page :)02:31
DocScrutinizer05yeah, (no updates) but busy02:32
DocScrutinizer05here we are02:32
DocScrutinizer051Tmaemo602:33
DocScrutinizer053.5MB02:33
DocScrutinizer05YESSIR!02:33
*** arcean has quit IRC02:34
DocScrutinizer05update: PA????!?02:34
merlin1991yep02:34
DocScrutinizer05PA-esound-compat - hualp!02:34
DocScrutinizer05ohwhell, already go and install that shite!02:35
DocScrutinizer05'continue!'02:35
DocScrutinizer05no backup please!02:35
DocScrutinizer053.49MB02:36
DocScrutinizer05I'd almost be tempted to disable friggin screenblanking during update02:36
DocScrutinizer05programmatically02:37
DocScrutinizer05kinda sucks02:37
DocScrutinizer05OS updated, reboot...02:38
DocScrutinizer05NOKIA02:38
DocScrutinizer05WAAH, shaking hans02:38
DocScrutinizer05seems it still works02:39
DocScrutinizer05kinda funny detail: no orientation lock in systray/menu02:39
merlin1991dafaq?02:40
DocScrutinizer05not thst I'd miss it02:40
DocScrutinizer05well, I might since desktop already rotates02:40
merlin1991hm in the control file status-area-orientationlock-applet (>= 1.0+0cssu4)02:40
merlin1991you sure it isn't there?02:41
DocScrutinizer05it's in menu ;-P02:41
DocScrutinizer05sorry, late here02:41
DocScrutinizer05so what else you want me to fsck with?02:42
merlin1991you could play around with the changes in ke-recv02:42
DocScrutinizer05now that i've raped my virgin N90002:42
merlin1991see /etc/defauls/ubsnetwork02:42
DocScrutinizer05hardly02:42
merlin1991s/defauls/defaults/02:42
DocScrutinizer05no rootsh, no ssh02:43
DocScrutinizer05see >>[2012-11-21 01:23:13] <DocScrutinizer05> dpkg -i BWAHAHA02:44
merlin1991ah now I'm getting some context :D02:44
* DocScrutinizer05 scrutinizes screen for first micro-scars02:46
DocScrutinizer05I'll remove battery on put it back into its coffin. Ask me tomorrow if you want more messing around with this T602:48
DocScrutinizer05and seems we should help chem|st out of his deadlock, so eventually we'll see a S5 before T7 rolls out02:49
DocScrutinizer05if that's not been clear, 'basic functionality approved by jOERG.' Please edit the texts accordingly02:50
DocScrutinizer05...as suggested above02:51
DocScrutinizer05the applauncher has no "enabler" icon02:51
DocScrutinizer05and the requester should have no empty lines, so the edited last sentence is initially visible02:51
DocScrutinizer05it's not obvious that there's sth to scroll02:52
*** M4rtinK has quit IRC02:59
*** infobot has joined #maemo-ssu03:38
*** ChanServ sets mode: +v infobot03:38
*** dhbiker has quit IRC03:45
*** dhbiker has joined #maemo-ssu03:47
*** Sicelo has quit IRC03:48
*** Sicelo has joined #maemo-ssu03:49
*** dafox has quit IRC03:53
*** nox- has quit IRC04:05
*** kolp has quit IRC04:09
*** infobot has quit IRC04:28
*** amiconn_ has joined #maemo-ssu05:23
*** amiconn has quit IRC05:23
*** amiconn_ is now known as amiconn05:23
*** DocScrutinizer05 has quit IRC06:03
*** DocScrutinizer05 has joined #maemo-ssu06:04
*** mickname has quit IRC06:23
*** mickname has joined #maemo-ssu06:26
*** freemangordon has joined #maemo-ssu08:18
*** luf has joined #maemo-ssu08:20
*** kerio has joined #maemo-ssu08:39
*** kerio has quit IRC08:58
*** Sicelo has quit IRC09:10
*** Sicelo has joined #maemo-ssu09:10
*** kerio has joined #maemo-ssu09:27
*** chainsawbike has quit IRC09:40
*** chainsawbike has joined #maemo-ssu09:41
*** infobot has joined #maemo-ssu10:12
*** ChanServ sets mode: +v infobot10:12
*** Pali has joined #maemo-ssu10:55
*** M4rtinK has joined #maemo-ssu11:02
*** BCMM has joined #maemo-ssu11:04
freemangordonmerlin1991: http://pastebin.com/1V7KmVFj11:08
freemangordonthe code is at the end11:08
merlin1991hm and what should I do now? :D11:09
freemangordonNFC11:09
freemangordon:D11:10
* freemangordon runs away11:10
freemangordon:P11:10
freemangordonmerlin1991: anyway, latest valgrind works almost like charm11:11
freemangordonso we can check all of the stuff in CSSU11:11
tadzikwell, valgrind is usually going crazy on glib/gtk11:11
tadzikbut yeah, this is exceptinoal :)11:11
freemangordontadzik: hmm, this one is 3.8111:12
luffreemangordon: where you get the code?11:12
tadzikI remember debugging my xmpp client with it. Gtk throwing up its own errors, glib its own, loudmouth and openssl as well...11:12
freemangordonand excluding the fact i had to revert libpuls0 to non-thumb, everything else works11:12
freemangordonluf: from their site11:12
tadzikeven hello worlds from gnome site weren't free of valgrind errors :)11:12
tadzikI guess that has something to do with custom memory allocators that glib uses11:13
freemangordonG_SLICE=always-malloc G_DEBUG=gc-friendly11:13
tadzikoh, TIL :)11:13
freemangordonluf: ./configure, make11:13
freemangordonluf: though configure needs some trickery. I'll tar.gz and upload it later. /opt/valgrind that is11:14
jon_yfreemangordon: cool, you have valgrind on the n900 working?11:15
tadzikhah. That'd be "slow" redefined :)11:15
lufjon_y: it's not so big problem.11:16
lufjon_y: I have also working valgrind on n900.11:17
freemangordonluf: 3.61?11:19
freemangordonthe one in extras-devel?11:20
lufI don't remember the version. But I don't compile it. I find some leaks in obexd ...11:20
lufI'm sorry I don't remember. I think some newer. But maybe from repository.11:20
freemangordonwhen I find some time i'll fire it agains h-d and h-h11:20
freemangordonluf: it is 3.6.1 in repos11:21
luffreemangordon: and yes obexd and bluez is very slow under valgrind on N900 :)11:21
merlin1991freemangordon: better prepare yourself for serious mindfuck when you do that :D11:22
freemangordonluf: I am sure it is11:22
lufI have valgrind 3.6.011:22
freemangordonmerlin1991: didn't we have some bug raised agains pixman?11:22
*** Timo has joined #maemo-ssu11:22
lufSorry 3.6.111:22
lufSo from repos.11:23
merlin1991freemangordon: lemme check11:23
freemangordonmerlin1991: I am on my way to office, bbl11:23
merlin1991freemangordon: couldn't find a bug on that11:25
*** arcean has joined #maemo-ssu11:27
*** andre__ has joined #maemo-ssu11:30
*** andre__ has joined #maemo-ssu11:30
*** dafox has joined #maemo-ssu11:44
freemangordonmerlin1991: is pixman in CSSU at all?12:19
merlin1991err I don't even know what pixam exactly is12:20
merlin1991*pixman*12:20
freemangordonoops, sorry, libpixman12:21
freemangordonmerlin1991: http://maemo.org/packages/package_instance/view/fremantle_sdk_free_i386/libpixman-1-0/0.16.2-5+0m5/12:23
merlin1991hm afaik we have no source package pixman12:24
freemangordonwell, we'd better have one then :D12:24
freemangordonlemme try to find some repo12:25
DocScrutinizer05mooo12:27
merlin1991freemangordon: what's the bug to fix?12:31
merlin1991DocScrutinizer05 aka "the cow"12:31
* merlin1991 thinks new -testing will go out tonight12:32
DocScrutinizer05~moo12:32
* infobot mooooooooo! I am cow, hear me moo, I weigh twice as much as you. I am cow, eating grass, methane gas comes out my ass12:32
freemangordonLOL12:32
freemangordonmerlin1991: Invalid read of size 112:33
freemangordonat 0x48344E8: strncmp (mc_replace_strmem.c:547)12:33
merlin1991DocScrutinizer05: isn't there a cow joke in apt aswell?12:33
merlin1991yep apt-get moo exists :D12:33
tadzikand aptitude moo :)12:34
Paliaptitude moo12:36
Paliaptitude moo -v12:36
Paliaptitude moo -vv12:36
Paliaptitude moo -vvv12:36
Paliand add more 'v' :D12:36
*** lizardo has joined #maemo-ssu12:37
merlin1991anybody know the origin of the moo joke?12:37
* merlin1991 is too young to know12:38
*** BCMM has quit IRC12:39
*** Martix has joined #maemo-ssu12:41
freemangordonmerlin1991: pixman seems like upstream animal12:42
freemangordonhttp://cgit.freedesktop.org/pixman/refs/tags12:42
*** Martix has quit IRC12:44
merlin1991now we just have to compare the source from the sdk with the 0.16.2 tag12:44
*** Martix has joined #maemo-ssu12:46
*** Martix has quit IRC12:57
*** Martix has joined #maemo-ssu12:57
freemangordonmerlin1991: yeah12:58
merlin1991and pray that it isn't a tarball + patches like some other packages in fremantle12:59
* merlin1991 looks @ sqlite12:59
freemangordonmerlin1991: I got the sources from maemo SDK repo, there is no debian/patches dir12:59
freemangordonhmm, maybe we can upgrade to lates13:00
freemangordont13:00
merlin1991hm if you're willing to check everything for regessions/api changes ;)13:01
freemangordonwell, at least we can upgrade to 16.613:04
merlin1991freemangordon: well basically, why?13:04
*** Martix has quit IRC13:04
freemangordoni bet there is a bunch of NEON optimizations13:05
* merlin1991 goes over the log13:06
merlin1991or rather watches git clone13:06
freemangordonaah13:06
merlin1991fsckd ath9k driver keeps failing hrere13:06
merlin1991s/hrere/here/13:07
infobotmerlin1991 meant: fsckd ath9k driver keeps failing here13:07
merlin1991hm apart from the assertion change the diff from 0.16.2 to 0.16.6 is minimal13:10
freemangordonmerlin1991: is our bug fixed?13:12
merlin1991I still didn't grasp what our bug is13:13
freemangordonmerlin1991: invalid memory acces13:13
freemangordons13:13
merlin1991I've seen no changes related to that13:13
merlin1991all there is is a change on handling of alphamaps13:14
freemangordonmerlin1991: if (strncmp (plat, "v7l", 3) == 0)13:16
freemangordonthat one makes an invalid memory access according to valgrind13:17
merlin1991well that looks ok depending on where the fuck "plat" points13:18
freemangordonmerlin1991: could be false alarm13:26
freemangordonhttp://old.nabble.com/valgrind%3A-r13019%3A-Implement-a-fake--proc-self-auxv-file-for-linux-systems.-td34515798.html13:28
Palifreemangordon, where is git repo of linux kernel for n900?13:32
PaliI want to boot some upstream kernel for maemo5 and test bme replacement13:33
PaliDocScrutinizer05, merlin1991, freemangordon, in /etc/event.d/rcS-late is code which writing some info to /sys/kernel/debug/panic_info_buff which is written to mtdoops when kernel crash13:38
Paliwhat do you think to patch it to write also 1) kernel version string and 2) CSSU version ?13:39
Palinow it writing only output of osso-product-info13:39
*** Martix has joined #maemo-ssu13:40
freemangordonPali: what git repo?13:46
Palifreemangordon, 3.x kernel for maemo513:47
freemangordonPali: have to ask Skry13:49
SkryI have 3.5 in github but that's not intended for maemo but the device itself for other os13:49
freemangordonSkry: yeah13:49
freemangordonPali: my patches are on merlin1991's server13:50
freemangordonbut maybe you don;t need them13:50
freemangordonssi and sgx13:50
Paliok13:51
freemangordonaiui you don't need X to test bqxxx13:51
PaliX will be good too :-)13:52
Palihildon-status-menu for battery applet13:52
Palifreemangordon, what do you think about adding kernel & cssu version to panic info buffer?13:53
freemangordonPali: well, not a bad idea. though i'll prefer kernel in CSSU first :)13:54
Paliok13:54
Palifreemangordon, do you know how to get CSSU version string?13:55
Palimaybe that which is in about cssu dialog in control panel13:56
freemangordonPali: NFC13:57
merlin1991Pali: well cssu version is in mp-fremantle-community-pr13:58
merlin1991you could ie use dpkg, though is /var/ mounted at that point?13:58
Paliok, I found it: https://gitorious.org/community-ssu/libcpaboutcssu/blobs/master/src/libcpaboutcssu.c#line2613:58
Pali/var/ ... /dpkg is in rootfs13:58
merlin1991Pali: that call is overly complex xD13:59
Paliany other idea how to get that version string?13:59
merlin1991I did find a call to dpkg to get the version14:00
* merlin1991 checks logs14:00
SkryPali: if you get charger working with upstream kernel could you notify me and perhaps send me some patches? I did try it something like a month ago and got it to a point where driver reports it's charging and something is definetely happening in background, but bq27xxx reports that battery is still discharging.14:00
PaliSkry, now charging and battery drivers was pushed to battery git tree14:00
PaliI need to write proper glue between isp and bq2415x drivers for charger type detection14:01
Paliand sent that patch to upstream kernel too14:01
PaliSkry, I will write to you14:01
DocScrutinizer05Pali: ((write also 1) kernel version string and 2) CSSU version)) all thumbs up for that14:03
SkryPali: ok, thanks. And in case you would like to test it out yourself I have some patches and .config for 3.7 if you happen to need such.14:03
Palimerlin1991, maybe this? $ dpkg-query -W -f \${Version} mp-fremantle-community-pr14:03
merlin1991Pali: yep14:03
merlin1991just found it myself :D14:03
PaliSkry, yes I'd like to use new version :-)14:04
Palido you have git tree for that?14:04
DocScrutinizer05sweet: cat /sys/kernel/debug/omap_gpio14:05
Paliand for kernel version, should I use? $ uname -a14:06
DocScrutinizer05uname -a sounds like a good choice14:06
SkryPali: only local for now, but it follows linux-omap. I have tested it with arch linux, it works but musb is currently not working, though I think it is fixed in upstream already.14:06
SkryI've had quite some lost of interest lately so haven't been that active with it14:07
DocScrutinizer05Pali: please don't expect /var/*/dpks to be in rootfs14:08
DocScrutinizer05users may and actually do optify it14:08
DocScrutinizer05so at very least have a fallback for gentle fail-over14:09
PaliDocScrutinizer05, I will call dpkg-query command. if it fails (e.g. optified) then it will write empty string to panic buf14:09
DocScrutinizer05fair enough14:09
SkryPali: I'll rebase my tree to latest in linux-omap master and see if there's anything new, adapt my few patches and send them to you with config later today, ok?14:09
Palibut now I see that panic buf is filled after MOUNTS_OK14:09
PaliSkry, ok14:09
DocScrutinizer05Pali: just make sure that script doesn't throw error in that case14:10
PaliSkry, can you merge your tree with battery tree?14:10
PaliDocScrutinizer05, now I'm going to fix that rcS-late script to work also on upstream kernel14:10
Pali(adding maemo-command || true)14:10
DocScrutinizer05good :-)14:11
Paliwe have upstart in cssu and rcS-late is in upstart14:11
DocScrutinizer05use ||:14:11
DocScrutinizer05shorter ;)14:11
DocScrutinizer05(I hope that's no bash'ism14:12
DocScrutinizer05)14:12
SkryPali: I'll try it out later today14:12
PaliSkry: http://git.infradead.org/battery-2.6.git/shortlog/HEAD14:12
DocScrutinizer05well, messybox 'knows' `:`14:12
DocScrutinizer05checked it14:13
PaliSkry, see patches for rx51_battery and bq2415x_charger and bq27x00_battery14:13
DocScrutinizer05the totally empty command14:13
Palinice :-)14:13
DocScrutinizer05of course you could do sth like >>   (dpk-query ... || echo "dpk faled, no info on cssu version. user optified /var/*/dpkginfo?") >>/sys/kernel/debug/panic_info_buff14:18
PaliDocScrutinizer05, that script is called after MOUNTS_OK14:20
Paliso when /opt is mounted14:20
Paliso if dpkg fail then system is in very very broken state or cssu is not installed14:20
DocScrutinizer05you're free to edit the || echo string anyway14:20
Palis/cssu/cssu metapackage/14:20
infobotPali meant: so if dpkg fail then system is in very very broken state or cssu metapackage is not installed14:20
DocScrutinizer05or simply do dpkg 2>&1 ||:14:21
Paliwe do not want very very long string in panic info buffer14:22
DocScrutinizer05we don't?14:22
DocScrutinizer05why notß14:22
DocScrutinizer05?14:22
Paliyes, because buffer is small14:22
Paliand it is written to mtdlog14:22
DocScrutinizer05well, dunno it might have some 16k or sth14:22
DocScrutinizer05and mtdlog is huuuge14:23
PaliI think "<unknown>" is ok14:23
DocScrutinizer05whatever you like14:23
PaliI think that osso-product-info also write <unknown> when SW version in CAL is removed14:23
DocScrutinizer05sure14:24
DocScrutinizer05btw I gave a rant about a related topic in here, some weeks ago14:25
DocScrutinizer05can't recall14:25
DocScrutinizer05some file in /etc/* we ought fill with cssu-product-info14:26
DocScrutinizer05found some reference to it in rcs-late or sth14:26
Pali/etc/event.d/rcS-late14:27
Palicommited: https://gitorious.org/community-ssu/upstart/commits/master14:29
DocScrutinizer05dafaq, seems busybox froze on :<cr> ??14:29
DocScrutinizer05or my wifi ssh lags like hell14:29
DocScrutinizer05sth odd with my iron900 wifi connection14:30
PaliAAAA, busybox grep does not have -R14:31
Palionly (small) -r14:32
*** kolp has joined #maemo-ssu14:32
DocScrutinizer05preinit, line 19714:34
merlin1991Pali: why do we need the lowmem fix?14:34
DocScrutinizer05release=`cat /etc/osso_software_version`14:34
Palimerlin1991, because lowmem is maemo extension14:35
PaliI want to boot some upstream kernel and that rcS-late script failing here...14:35
Pali/etc/osso_software_version -> I do not have this file14:37
DocScrutinizer05I *think* every CSSU update should `echo 2011.38.1Tmaemo5 >/etc/osso_software_version`14:37
DocScrutinizer05Pali: that's the point14:37
DocScrutinizer05Pali: so it's relatively low risk to create it, with proper content14:38
Paliand there is something other: every cssu upgrade calling: osso-product-info -s OSSO_VERSION="RX-51_2009SE_21.2011.38-1_PR_MR0" 2> /dev/null || exit 014:38
Paliand it always write new string to CAL14:38
Paliand if is same, it write it too14:39
Palithis is bad14:39
DocScrutinizer05no issues here with  osso-product-info -s14:39
DocScrutinizer05why do you think it'14:39
DocScrutinizer05s bad?14:39
Paliuseless CAL write14:40
kerioPali: fix osso-product-info then :)14:40
DocScrutinizer05hmmm14:40
Palikerio, osso-procuct-info is closed14:40
DocScrutinizer05I don't think it's useless14:40
PaliI will fix it in postinst14:41
Pali$ if test "$(osso-product-info -q OSSO_VERSION)" = "RX-51_2009SE_21.2011.38-1_PR_MR0"; then exit 0; fi14:41
DocScrutinizer05actually I love 'history' in CAL14:41
DocScrutinizer05I don't see why we're concerned about it14:42
Paliso above "if" fix writing to CAL same version string14:42
DocScrutinizer05I love it writing even same string to CAL, where's the problem in it doing that?14:43
Palimess in CAL14:43
DocScrutinizer05lol14:43
DocScrutinizer05your fix will only change that to another kind of mess14:44
Paliand also wear leveling...14:44
DocScrutinizer05I don't see how's that new mess any better than the old14:44
DocScrutinizer05oh well, wear leveling14:44
Paliif you upgrade CSSU metapackage for testing 1000000x cal can be damaged14:44
DocScrutinizer05not really14:45
DocScrutinizer05you need at least 10^5 times that14:45
kerioa million erases doesn't sound like much, over the whole mtd partition14:45
DocScrutinizer05since not every write to CAL already does a page erase14:45
Palido you trust libcal??14:45
PaliI not14:46
kerioi trust libcal14:46
DocScrutinizer05not a good rationale for a "fix"14:46
keriocan the onenand be repartitioned?14:46
kerioor is the layout static from something closed?14:47
DocScrutinizer05yes. but NOLO and flasher can't14:47
DocScrutinizer05the latter, kerio14:47
DocScrutinizer05afaik14:47
kerioDocScrutinizer05: use initfs as cal from the kernel side, or something14:47
kerioNOLO only *reads* from cal, right?14:48
DocScrutinizer05well, nope14:48
DocScrutinizer05it writes flags there14:48
keriooh, heh14:48
kerioi'm not sure i trust *that* actually14:49
DocScrutinizer05anyway, there's no demand for any fixing regarding CAL yet14:49
DocScrutinizer05neither for waer leveling nor for any other reason14:49
DocScrutinizer05it's absolutely fine the way it works right now, in my book14:50
PaliNOLO has own mtd layout. it using CAL, kernel and initfs15:02
freemangordonPali: we have libcal REed, look at it for how writes are handled15:02
Palibut kernel can use other layout15:02
Paliif you replace NOLO you can reparition as you want15:02
DocScrutinizer05actually a NOLO binary patcher "repartitioner" would be a rather nice tool15:15
PaliDocScrutinizer05, I forgot that partition layout is stored in CAL15:21
Palibut problem is that format of layout is unknown15:21
DocScrutinizer05really?15:21
Paliyes15:21
*** dafox has quit IRC15:21
Palibut I do not know if NOLO using it15:22
DocScrutinizer05that's kinda weird since CAL already starts at $random-addr in MTD15:22
Paliwhen I booted NOLO in qemu without kernel it shown me serial console15:22
DocScrutinizer05so the partition with CAL contains info about own starting addr15:22
Paliand there is command to show mtdparts15:22
Paliand in nolo there was separate partitin for xloader and separate for nolo15:23
Palibut in /proc/mtd is only ONE partition for bootloader15:23
Pali$ calvaria -d mtd1dump -n part_table15:24
PaliCAL key for partition is "part_table"15:24
kolpJust curious, what's CAL?15:29
*** Raimu-X has joined #maemo-ssu15:29
*** mickname_ has joined #maemo-ssu15:30
*** chainsawbike_ has joined #maemo-ssu15:33
DocScrutinizer05~cal15:33
infobotwell, cal is a calendar. try $(cal 1752)15:33
DocScrutinizer05dang15:33
DocScrutinizer05IroN900:~# cat /proc/mtd15:34
DocScrutinizer05dev:    size   erasesize  name15:34
DocScrutinizer05mtd0: 00020000 00020000 "bootloader"15:34
DocScrutinizer05mtd1: 00060000 00020000 "config"15:34
DocScrutinizer05config=CAL15:34
*** chainsawbike has quit IRC15:34
*** mickname has quit IRC15:34
*** Skry has quit IRC15:34
*** Raimu has quit IRC15:34
*** chainsawbike_ is now known as chainsawbike15:34
DocScrutinizer05http://talk.maemo.org/showthread.php?t=2046515:34
DocScrutinizer05~$(cal 1752)15:36
DocScrutinizer05~factinfo cal15:37
infobotcal -- created by cafuego <cafuego@caffeine.ipv6.cafuego.net> at Tue Jun 10 07:37:04 2003 (3452 days); it has been requested 9 times, last by DocScrutinizer05, 3m 25s ago.15:37
DocScrutinizer05kolp: less -f /dev/mtd1ro15:38
DocScrutinizer05part-table is very first entry15:39
DocScrutinizer05alas quite obscure, and we know fremantle boots even when CAL got nuked (nandtester checked that for us ;-D )15:40
*** dafox has joined #maemo-ssu15:41
merlin1991I've got one n900 where cal seems to be fsckd15:41
DocScrutinizer05strings /dev/mtd1ro|less; for beginners15:41
*** dafox is now known as Guest6826315:41
kolpDocScrutinizer05: ty15:42
DocScrutinizer05yw15:42
DocScrutinizer05kolp: NEVER think of writing to CAL!15:42
DocScrutinizer05it's not restorable15:43
DocScrutinizer05(first approach)15:43
*** arcean has quit IRC15:43
DocScrutinizer05(now for 2nd, advanced approach:)15:43
kolpMkay, though I didn't intend to :)15:43
DocScrutinizer05merlin1991: so why don't you try and nandwrite a copy of some other N900 to your nuked CAL?15:44
DocScrutinizer05kerio will love to assist15:44
*** Skry has joined #maemo-ssu16:00
*** Pali has quit IRC16:01
*** arcean has joined #maemo-ssu16:10
*** Skry has quit IRC16:16
*** Timo has quit IRC16:30
*** Timo has joined #maemo-ssu16:39
*** Pali has joined #maemo-ssu16:54
*** luf has quit IRC16:54
*** arcean_ has joined #maemo-ssu16:56
*** FIQ has joined #maemo-ssu16:57
*** arcean has quit IRC17:01
merlin1991hm actually I have 2 devices where osso-product-info mostly says "<unkown>"17:05
*** Skry has joined #maemo-ssu17:06
*** Jade has quit IRC17:20
*** arcean has joined #maemo-ssu17:28
*** arcean_ has quit IRC17:32
*** tg has quit IRC17:34
*** tg has joined #maemo-ssu17:35
*** M4rtinK has quit IRC17:46
*** myuu_- has joined #maemo-ssu17:49
*** dhbiker has quit IRC17:51
*** dhbiker has joined #maemo-ssu17:51
*** myuu_ has quit IRC17:51
*** Pali has quit IRC18:23
kerioDocScrutinizer05: i'll most likely not love to assist >:c18:32
keriomoving a CAL from a n900 to another is probably a road to bricking18:32
keriounless there are 0 bad blocks in the same partition on both N900s, and they have the same hw rev18:32
kerioi think that once you have a copy of cal, you can dump the *contents* and write them on the device to a brand-new CAL with libcal or the reverse engineered one18:33
*** iDont has joined #maemo-ssu18:34
*** ekze has quit IRC18:38
DocScrutinizer05kerio: that's BS, we sorted that out, with nandwrite18:43
DocScrutinizer05nadwrite is made to deal with bad blocks18:44
DocScrutinizer05you're right about hw-rev though, would be nice if they'd match18:45
DocScrutinizer05if your destination mtd partition has more bad blocks than your origin partition, then nandwrite will spit out a warning/error about image to write exceeds available space, that's all18:47
*** NIN101 has joined #maemo-ssu18:57
kerioDocScrutinizer05: what's a bad block there, btw?19:08
kerioa full eraseblock?19:08
kerioif so, i doubt libcal will handle it19:08
kerioi mean, cal is a linked list, you have pointers to the next item19:09
kerioif you have a bad block and you skip that block...19:10
*** NIN102 has joined #maemo-ssu19:16
*** NIN101 has quit IRC19:19
*** corepl has joined #maemo-ssu19:20
*** iDont has quit IRC19:22
*** toxaris has joined #maemo-ssu19:22
*** corepl has quit IRC19:22
*** NIN102 has quit IRC19:22
*** toxarisswe has joined #maemo-ssu19:24
*** l4m3rx has joined #maemo-ssu19:25
*** toxaris has quit IRC19:27
*** toxarisswe has quit IRC19:35
DocScrutinizer05you can bet on libcal handling bad blocks19:44
kerioyeah but it *handles* bad blocks19:45
kerioit doesn't necessarily handle a nanddump of a written cal partition nandwritten on a different partition19:46
keriofreemangordon: would libcal handle that?19:46
DocScrutinizer05hmm, valid concern19:46
DocScrutinizer05btw a linked list would be about the worst data structure for CAL you could possibly think of19:49
DocScrutinizer05I guess it's rather just scanning for labels, basically a grep19:49
DocScrutinizer05since there's absolutely no use in changing the forward pointer in an existing record, on NAND19:50
DocScrutinizer05unless, well... you could define all zeroes or all ones as a void pointer marking last element, and overwrite that with a pointer to new element on a rewrite19:51
*** NIN101 has joined #maemo-ssu19:51
DocScrutinizer05still hardly any useful data structure19:52
DocScrutinizer05simply have tags with magic numbers, grep for those, get the one with newest date, highest index, or whatever19:53
DocScrutinizer05I mean, libcal isn't meant to be speed optimized19:53
DocScrutinizer05check calvaria code if you're interested in details. I didn't19:54
*** NIN102 has joined #maemo-ssu19:54
*** NIN101 has quit IRC19:56
DocScrutinizer05kerio: see https://dev.openwrt.org/browser/packages/utils/calvaria/files/src/calvaria.c#L25, much like I expected20:00
DocScrutinizer05#define HDR_MAGIC       "ConF"20:01
DocScrutinizer05already thought as much :-P20:01
DocScrutinizer05actually that's how I manually parsed less -f /dev/mtd1 so far20:02
kerioDocScrutinizer05: i suppose they wanted to reduce writes as much as they could? idk20:02
DocScrutinizer05without reading any calcaria.c code20:02
keriohow do they figure out where to write once the space is filled?20:04
kerioDocScrutinizer05: when do blocks become invalid?20:06
DocScrutinizer05libcal will scan for an erase page that has no valid records, then erase  that20:07
keriooh so they're marked invalid at some point20:07
keriowhen they're skipped20:07
DocScrutinizer05well, for whatever 'marked as invalid' means20:07
kerioDocScrutinizer05: deleted record, or overwritten record20:07
DocScrutinizer05https://dev.openwrt.org/browser/packages/utils/calvaria/files/src/calvaria.c#L27920:08
DocScrutinizer05basically a record is invalid if there's another more valid record for same label20:09
DocScrutinizer05you could also purge a record by overwriting it without prior page erase20:10
DocScrutinizer05mind you, writing 1s is possible while writing 0s needs page erase (or other way round)20:11
keriowhat's wrong about erasing the page and rewriting it?20:11
DocScrutinizer05takes time and wears out NAND20:12
DocScrutinizer05takes really loooooooooong20:12
kerioreally? :o20:12
DocScrutinizer05like 20ms20:12
DocScrutinizer05or 10020:12
DocScrutinizer05or 120:12
DocScrutinizer05a time you could grep like 10000 CAL partitions for a label20:13
DocScrutinizer05and actually it's the page erase that wears out NAND the most20:14
DocScrutinizer05it's a really brute force physical event that clears nand ersase pages20:14
keriooic20:15
keriois it really a good idea to use a full eraseblock for each element then?20:16
DocScrutinizer05do they do that?20:16
kerioidk, i hope not20:16
DocScrutinizer05I wouldn't think they do20:17
DocScrutinizer05I'd guess they pack some 10s to 100s of elements into one erase page20:17
DocScrutinizer05btw they could as well do something nifty: if only two more erase pages left, they copy all valid elements from a completely filled erase page to an empty one, then erase that page as it's now free20:19
DocScrutinizer05s/an empty one/ empty slots on partially used erase pages/20:20
infobotDocScrutinizer05 meant: btw they could as well do something nifty: if only two more erase pages left, they copy all valid elements from a completely filled erase page to  empty slots on partially used erase pages, then erase that page as it's now free20:20
DocScrutinizer05avoids fragmentation, and simplifies picking a erase page to free20:20
kerioDocScrutinizer05: i wonder what's the best way of implementing a nand-friendly hashtable20:20
DocScrutinizer05I bet there are implementations for that already, probably done as master thesis20:21
DocScrutinizer05I'd say: don't20:22
kerioat a phd level? :o20:22
DocScrutinizer05you don't wanna use a hash table on NAND20:22
kerioit doesn't seem that difficult, you just have to minimize the writing of zeros everywhere20:22
keriotoday's key word is UNDERSTATEMENT20:23
DocScrutinizer05however with my initial suggestion of late writing of forward pointers, you could do. If you also implement a "deleted" flag for late tagging as purged20:23
kerioDocScrutinizer05: i suppose that the big problem here is that you have to be able to parse and write that format from NOLO20:25
kerioso you probably want to keep it simple20:25
DocScrutinizer05at some level however, you'll have to revert to brute force forward scan/grep, as every hash table is incomplete at some point, and then you get no sort order for elements you add later on20:25
DocScrutinizer05kerio: keep in mind NOLO even could load a complete linux to RAM to delegate some tasks like these20:26
DocScrutinizer05depends on flasher only20:27
DocScrutinizer05NOLO as well could expose a *very* basic API to handle NAND (CAL) rewrites, something like word read(addr), write(addr, word), erasepage(pagenumber)20:28
DocScrutinizer05all the rest again up to flasher20:29
DocScrutinizer05so... no problem with complexity of handling CAL rewrites in NOLO20:29
DocScrutinizer05hell, NOLO could even export a simulated JTAG20:30
kerioDocScrutinizer05: usb mtd!20:31
DocScrutinizer05JTAG has 4 pins20:31
DocScrutinizer05flasher would implement an embedded JTAG programmer then20:31
DocScrutinizer05we simply don't know20:32
DocScrutinizer05~wiki jtag20:35
infobotAt http://en.wikipedia.org/wiki/Jtag (URL), Wikipedia explains: "{{Refimprove|date=November 2009}} 'Joint Test Action Group' ('JTAG') is the common name for what was later standardized as the IEEE 1149.1 'Standard Test Access Port and Boundary-Scan Architecture'. It was initially devised for testing printed circuit boards using boundary scan and is still widely used for this application. Today JTAG is also widely used for IC debug ports. In the ...20:35
DocScrutinizer05actually JTAG is the smartest invention since intersil 400420:38
DocScrutinizer05ooops, s/intersil/intel/20:42
DocScrutinizer05or rather, s/4004/IM6100/20:43
*** Martix has quit IRC20:56
*** Martix has joined #maemo-ssu20:57
*** Guest68263 has quit IRC21:20
*** arcean has quit IRC21:21
*** dafox has joined #maemo-ssu21:22
*** arcean has joined #maemo-ssu21:23
*** Pali has joined #maemo-ssu22:21
*** arcean has quit IRC22:32
*** arcean has joined #maemo-ssu22:49
*** dafox has quit IRC22:56
*** lizardo has quit IRC23:00
*** arcean has quit IRC23:24
*** nox- has joined #maemo-ssu23:29
*** M4rtinK has joined #maemo-ssu23:29
*** arcean has joined #maemo-ssu23:32
*** NIN102 has quit IRC23:35
*** freemangordon has quit IRC23:44
*** freemangordon has joined #maemo-ssu23:45
*** peetah has quit IRC23:56
*** peetah has joined #maemo-ssu23:57

Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!