IRC log for #maemo-ssu on 20141224

01:19.52*** join/#maemo-ssu freemangordon (~ivo@46.249.74.23)
02:08.08*** join/#maemo-ssu futpib (~futpib@176.96.237.217)
03:20.34*** join/#maemo-ssu sparetire_ (~sparetire@unaffiliated/sparetire)
07:29.05*** join/#maemo-ssu dhbiker (~dhbiker@APN-122-72-178-gprs.simobil.net)
07:42.09*** join/#maemo-ssu RedW (~redw@89-73-179-171.dynamic.chello.pl)
07:42.18*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
07:56.09Palimerlin1991: can you delete libdevlock-dev package from cssu-devel?
07:56.31Paliit is only single -dev package and we do not have any other single -dev packages cssu-devel
07:59.24Palioups
07:59.35Palis/libdevlock-dev/libsysinfo-dev
08:09.57Palimerlin1991: note: when you builds packages in scratchbox, use: $ fakeroot debian/rules clean; git clean -fdx; dpkg-buildpackage -rfakeroot -I.git -us -uc -sa
08:10.20Paliit will clean and remove all non git files before creating packages, so process should be fully deterministic
08:10.59Palisometimes, some packages does not clean generated documentation files which cause that files could come from older versions...
08:21.45merlin1991Pali: i'm actually using git reset --hard; git clean -dfxe .gitignore;dpkg-buildpackage.
08:21.59Paligood
08:22.49Palinew dosfstools and fmtx-middleware packages are now in cssu-devel
08:24.45merlin1991what's new in dosfstools?
08:25.52merlin1991and libsysinfo-dev is removed now
08:31.46Paliremoving dirty bit when is set
08:31.55Paliupstream patch
08:32.37Palisome OSes set dirty fat bit when mounting FS and removing it when umounting... fsck tool should remove it when repairing FS
08:33.52PaliI have 3.13 kernel on laptop and it show warning in dmesg when fat FS was not properly umounted (dirty bit was not cleaned):
08:33.52Pali[    8.746065] FAT-fs (sdb2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
08:40.53Palimerlin1991: my script told me that also libdevlock-dev is in cssu-devel
08:42.38merlin1991Will remove it when i get back home
08:42.44merlin1991Btw happy xmas :)
09:21.23*** join/#maemo-ssu dhbiker (~dhbiker@APN-122-109-91-gprs.simobil.net)
09:23.20*** join/#maemo-ssu _rd (~rd@p4FD1C018.dip0.t-ipconnect.de)
09:30.18*** join/#maemo-ssu dhbiker (~dhbiker@APN-122-109-91-gprs.simobil.net)
09:30.39*** join/#maemo-ssu povbot_ (~supybot@office.pov.lt)
09:30.39*** mode/#maemo-ssu [+v povbot_] by ChanServ
10:44.51*** join/#maemo-ssu LauRoman|Alt (~LauRoman@5-14-167-74.residential.rdsnet.ro)
10:48.21*** join/#maemo-ssu futpib (~futpib@176.96.237.217)
11:20.50*** join/#maemo-ssu rd_ (~rd@p4FD1C018.dip0.t-ipconnect.de)
11:21.10*** join/#maemo-ssu _rd (~rd@p4FD1C018.dip0.t-ipconnect.de)
11:32.23*** join/#maemo-ssu LauRoman (~LauRoman@5-14-158-89.residential.rdsnet.ro)
11:39.42*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
11:49.06merlin1991hm why can't qemu-img have some sort of progress indicator
12:17.28*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
12:48.14*** join/#maemo-ssu _rd (~rd@p4FD1C018.dip0.t-ipconnect.de)
12:58.37*** join/#maemo-ssu sparetire_ (~sparetire@unaffiliated/sparetire)
13:25.41APicWrite a Patch
13:29.20merlin1991meh the time it takes untill that would arrive in debian-stable :D
13:42.14merlin1991Pali: currently uploading to cssu-testing-testing
14:05.37*** join/#maemo-ssu NishanthMenon (~nmenon@nat/ti/x-umrqizukulardzsu)
14:12.16merlin1991hm the upstream here is horrible :D
14:26.07*** join/#maemo-ssu NIN101 (~core@n900.quitesimple.org)
14:45.40*** join/#maemo-ssu xes (~xes@unaffiliated/xes)
15:06.01merlin1991hey xes, did I ever tell you to play my guinea pig for cssu-testing?
15:08.07*** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm)
15:10.19*** join/#maemo-ssu javispedro (~javier@Maemo/community/contributor/javispedro)
15:17.12xesmerlin1991: hi! ..sorry?
15:17.47merlin1991there's a repo called testing-testing where a select few get the change to have their device messed up in case I did something wrong with a release :D
15:18.07merlin1991s/change/chance/
15:29.42bencoh:]
15:31.38merlin1991Tmaemo10 incoming soon (TM) changelog is ready already: http://wiki.maemo.org/Community_SSU/Changelog#Tmaemo10
15:32.11sixwheeledbeast\o/
15:37.44merlin1991but it will take some time for the update to hit the repo, my upstream sucks big time here
15:54.12merlin199180KB/s according to scp
15:54.13merlin1991wohoo
15:54.31merlin1991and it's only 242M in total :D
15:56.57bencoh:D
16:17.32*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
16:26.55*** mode/#maemo-ssu [+o merlin1991] by ChanServ
16:27.14*** topic/#maemo-ssu by merlin1991 -> Maemo Community Seamless Software Update "CSSU" channel, http://wiki.maemo.org/Community_SSU | Known bugs: http://j.mp/communityssu-bugs | Channel logs: http://mg.pov.lt/maemo-ssu-irclog/ | Sources: http://gitorious.org/community-ssu/ | Latest version: Testing(2014-12-24): 21.2011.38-1Tmaemo10; Stable(2014-09-03): 21.2011.38-1Smaemo7
16:27.20*** mode/#maemo-ssu [-o merlin1991] by ChanServ
16:27.37merlin1991as per topic change, Tmaemo10 is out :)
16:43.48*** join/#maemo-ssu _rd (~rd@p4FD1C018.dip0.t-ipconnect.de)
17:10.07M4rtinKmerlin1991: nice! :)
17:10.49*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
17:11.10keriowoo!
17:11.16kerioreleased? or in testing-testing?
17:19.53Palimerlin1991: btw look at state file which I sent to you... there are some packages which are in -devel for a long time but not in -testing nor in new changelog
17:22.30sixwheeledbeastkerio I would assume in the wild.
17:22.47sixwheeledbeastgoes in search of testing device
17:27.19*** join/#maemo-ssu _rd (~rd@p4FD1C018.dip0.t-ipconnect.de)
17:29.46sixwheeledbeastpresses update for the second time
17:30.27sixwheeledbeast\o/
17:54.29*** join/#maemo-ssu thedead1440 (~thedead14@unaffiliated/thedead1440)
18:06.17*** join/#maemo-ssu _rd (~rd@p4FD1C018.dip0.t-ipconnect.de)
18:22.52*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
19:07.17*** join/#maemo-ssu _rd (~rd@p4FD1C018.dip0.t-ipconnect.de)
19:31.43*** join/#maemo-ssu _rd (~rd@p4FD1C018.dip0.t-ipconnect.de)
19:40.50*** join/#maemo-ssu freemangordon (~ivo@46.249.74.23)
20:07.51Siceloby the way, i'm on thumb .. so update affects me or not?
20:09.51PaliNishanthMenon: hi
20:10.02NishanthMenonPali, hi
20:10.59PaliNishanthMenon: do you know something about L3_PM_ADDR_MATCH_* omap registers?
20:12.00NishanthMenonPali, i dont :(
20:12.13PaliI found only few info in veeery big TI OMAP35 PDF...
20:12.36Paliand there is only something about reserved usage
20:12.54NishanthMenonPali, it might be in the High Security TRM which is under NDA and non-public
20:13.41NishanthMenonunless the platform manufacturer decided to make it public, at engineering level we cant ... we only got approval for GP devices support in upstream
20:14.01Palido you know somebody who working on HS omap aes driver?
20:14.14NishanthMenonnope :(
20:14.22Paliit is in mainline kernel, so somthing could be public...
20:14.46NishanthMenonmainline != SoC company's work always.. it tends to be contributed over various folks
20:32.44sixwheeledbeastSicelo: yes it will
20:35.30Sicelothanks. just changed batteries to update
20:41.20PaliNishanthMenon: do you know if it is possible to check on omap3 if particular address has write permission?
20:41.42Palior read permission
20:47.17PaliNishanthMenon: it looks like that L3 firewall is also on GP devices... or not?
20:47.27NishanthMenonPali, I cannot comment
20:47.50NishanthMenonbest I can suggest is e2e.ti.com
20:48.14NishanthMenonPali, even if I do look up internal documents, commenting or providing info in public domain will violate my terms of employment :(
20:48.43NishanthMenonor for that matter providing information to folks not in approved list results in the same :(
20:49.27Paliok
20:49.50Paliand can you comment informations provided in public PDF documents?
20:50.02NishanthMenonPali, please use e2e.ti.com
20:50.07Paliok
20:57.34merlin1991Pali: it would be great if you could generate the state file again, i'll look into all packages that are not in testing yet
21:04.09Sicelowhat is a definitive way to check if you're on thumb?
21:04.30*** join/#maemo-ssu LauRoman|Alt (~LauRoman@5-14-158-89.residential.rdsnet.ro)
21:04.38Siceloasking because after update, Control Panel > About CSSU no longer shows Thumb
21:06.57Palimerlin1991: see email
21:07.15PaliNishanthMenon: ah, that page need registration :-(
21:07.34NishanthMenonPali, they need to know who to respond to. Sorry :(
21:07.39PaliSicelo: check if some debian package has thumb in version
21:08.13PaliNishanthMenon: is there any irc channel?
21:08.22NishanthMenonPali, usually encryption related stuff falls under some export control guidance and it typically limited to very few countries
21:08.26Siceloi did `dpkg -l | grep "*thumb*" .. returns nothing
21:08.44NishanthMenonPali, IRC for support? no, official support is only over e2e.ti.com :(
21:09.04PaliNishanthMenon: ok
21:09.45PaliSicelo: then you do not have any thumb package
21:10.46Sicelomeans that update shouldn't be done by thumb users .. i was on thumb :)
21:10.51Sicelowill re-update
21:10.59PaliNishanthMenon: anyway, are you still doing any automatic tests of kernel builds on n900?
21:11.48NishanthMenonPali, yes - it has been broken for days now. tmlind says it works for him. I am guessing something to do with u-boot or something like that on my setup. not had time to back to lab to dig in
21:13.05NishanthMenonPali, https://github.com/nmenon/kernel-test-logs/blob/next-20141221/omap2plus_defconfig/n900.txt is what i have
21:13.28NishanthMenonPali, I am using chained bootloader dowload over serial port
21:14.10PaliKernel hung.. GIVEN UP RETRIES
21:14.23NishanthMenonPali, yeah.. been the state for a few days.. :(
21:14.29PaliWhen I tested uboot I used only usb
21:14.37NishanthMenonit kinda waits for 10 mins for kernel log to show up before giving up
21:14.59Palido you have correct cmdline in kernel?
21:15.08NishanthMenonbootargs=console=ttyO2,57600n8 vram=16M earlyprintk rootwait ip=dhcp root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
21:15.49Palifor booting in qemu (with serial console) I'm using console=tty0 console=ttyO2
21:16.18NishanthMenonhttps://github.com/nmenon/kernel-test-logs/blob/v3.18/omap2plus_defconfig/n900.txt
21:16.23NishanthMenonbased on v3.18 tag
21:16.27NishanthMenonit broke with v3.19-rc1
21:16.38Paliand pavelm wrote that there is some problem with booting from mmc
21:16.56NishanthMenonI dont really know what the heck happened.. but i know it is very recent
21:17.20NishanthMenonhttps://github.com/nmenon/kernel-test-logs/blob/v3.19-rc1/omap2plus_defconfig/n900.txt is v3.19-rc1 log
21:18.57Paliif you are still doing these tests on n900 and you see problems with kernel, can you send email to ML?
21:19.24Palimaybe some other people will know what they changed and it could help to bisect problems easier
21:21.10NishanthMenonPali, ok. will build with early_printk and see if I get to see something. serial downloads usually take around 20 mins to come back with results :)
21:21.11Palifreemangordon look ^^^^
21:21.30NishanthMenonrebuilds v3.19-rc1
21:22.06Palido you have some (C) Nokia serial console for N900?
21:22.37NishanthMenonPali, yes - an ex Nokian who joined TI was kind enough to donate his serial JIG for the TI farm
21:23.15Paliwow :-)
21:23.41Paliand are you using standard n900 device or some modified/development?
21:23.52NishanthMenonPali, unfortunately our test setup is capable of ethernet or serial download and it heavily tied down to u-boot commands :( - so did not have much of an option.
21:23.59NishanthMenonstandard n900 with jig
21:24.36NishanthMenoni cannot incorporate flasher OR fastboot etc into the setup without spending months fixing the test framework - not really my focus
21:26.57NishanthMenonfires off early_printk image to farm and decides to go for coffee with the message "serial downloading" on screen :P
21:29.08merlin1991Thanks Pali
21:31.37PaliNishanthMenon: chained bootloader is: Nokia XLoader --> NOLO --> U-boot?
21:32.26NishanthMenonPali, oui
21:34.23Paliok, now I'm going offline...
21:34.27Palibye all

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.