**** BEGIN LOGGING AT Tue Jun 26 02:59:58 2012 Jun 26 07:25:15 freesmartphone.org: 03morphis 07cornucopia * rcc892666c74f 10/fsogsmd/src/lib/at/atsms.vala: fsogsmd: lib: at: use id provided as parameter of SMS message acknowledgement Jun 26 07:25:16 freesmartphone.org: 03morphis 07cornucopia * rdc54959d8484 10/fsogsmd/ (src/lib/at/atcommands.vala tests/testatcommand.vala): fsogsmd: lib: at: add implementation of AT+CSMS command Jun 26 07:25:17 freesmartphone.org: 03morphis 07cornucopia * r5efde8aabc62 10/fsogsmd/ (src/lib/at/atcommands.vala tests/testatcommand.vala): fsogsmd: lib: at: add implementation of AT+CMGF command Jun 26 07:25:19 freesmartphone.org: 03morphis 07cornucopia * r613a2caa99b5 10/fsogsmd/ (src/lib/at/atcommands.vala tests/testatcommand.vala): fsogsmd: lib: at: extend AT+CNMI with testing mode Jun 26 07:25:20 freesmartphone.org: 03morphis 07cornucopia * rf080d1bd1ae4 10/fsogsmd/tests/testatresultiter.vala: fsogsmd: tests: one more test case for the AtResultIter class Jun 26 08:12:58 morphis: pong Jun 26 09:25:08 if you care about wifi on freerunner any help is appreciated: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679085 Jun 26 11:19:48 freesmartphone.org: 03morphis 07cornucopia * rca0717e6e349 10/fsogsmd/src/lib/sms.vala: fsogsmd: lib: extend sms handler to be able to configure it Jun 26 11:19:48 freesmartphone.org: 03morphis 07cornucopia * r4f1bedbc71be 10/fsogsmd/src/lib/at/atchannel.vala: fsogsmd: lib: at: configure SMS handler on main channel initialization Jun 26 11:19:48 freesmartphone.org: 03morphis 07cornucopia * r2d2828a0d62a 10/fsogsmd/src/lib/ (at/atsms.vala sms.vala): fsogsmd: lib: at: configure SMS service mode and respect supported modes Jun 26 12:11:17 freesmartphone.org: 03morphis 07cornucopia * r8bf1db912380 10/fsogsmd/src/lib/at/atsms.vala: fsogsmd: lib: at: extend warning about a failing AT+CNMA command Jun 26 12:11:18 freesmartphone.org: 03morphis 07cornucopia * r2e46854149eb 10/fsogsmd/src/ (3 files in 3 dirs): fsogsmd: lib: drop unneeded parameter id from acknowledgeSmsMessage method Jun 26 13:04:42 morphis: a question wrt 2e46854149eb02144004302e10c89b5e6854042a. Is it wise to remove the parameter completely? I reckon the 05.05 does not need the parameter, but could we think of a modem that might need it or could make use of it? in that case we can just not use the parameter in the AT case, but keep the signature. Jun 26 13:05:08 mickey_office: yes, I thought about this Jun 26 13:05:28 but with Samsung IPC and msmcomm I didn't discovered any use of this parameter Jun 26 13:05:43 mickey_office: and as it's a private API anyway Jun 26 13:06:22 mickey_office: good to see you're watching the commit log :) Jun 26 13:06:26 :) Jun 26 13:06:39 I removed it as I looked over things to clean up Jun 26 13:06:53 ok Jun 26 13:08:33 mickey_office: btw. why did you implemented all the modem initialization stuff without respecting the responses? Jun 26 13:10:36 morphis: well, not all the init stuff, if you consider things like the charset negotiation. My reasoning was that either the command works, or - if it doesn't - we can't do anything about it, but try our best to continue as usual. i didn't want to add facilities such as resending the command multiple times or so for the simple init commands. do you see a case where this could be a problem? Jun 26 13:12:51 mickey_office: I was just wondering Jun 26 13:13:07 as we never really know for example in which SMS service mode we're Jun 26 13:14:49 if we're just issueing AT+CSMS=1 and don't consider it's response Jun 26 13:17:55 for sure we should not resend commands multiple times but take into advance their response so we can react if they don't succeed and expected capabilities are not supported (would reduce the number of workaronds we have to implement in a modem plugin somehow) Jun 26 13:22:25 sure, might be an improvement Jun 26 13:26:28 mickey_office: do you already had some time to look at my multi-device and device-status proposals? Jun 26 13:26:58 morphis: not yet, sorry, i will look at it soon Jun 26 13:27:37 ok Jun 26 13:28:03 mickey_office: should we discuss both things per mail or directly in our wiki? Jun 26 13:29:03 hmm, mail might be better, just to keep all the subscribed folks updated as well, and then write the conclusions to the wiki Jun 26 13:36:37 ok Jun 26 13:43:57 ok, I've tweaked the pinmux in uboot a bit. still incomplete (need time to do it) but at least camera is now working on galaxy nexus. Just need to reverse-engineer OMAPFlash and finish modem firmware loader now Jun 26 13:56:50 Alex[sp3dev]: is your u-boot code somewhere available? Jun 26 13:58:57 morphis: yes. https://gitorious.org/i9100-proper-linux/i9100-uboot/commits/tuna_clean . it has a somewhat sometimes working usbtty, but no fastboot or DFU. so we're deciding on whether to implement them or reimplement omapflash Jun 26 13:59:37 it replaces samsung SBL so only xloader and chip's internal rom are closed Jun 26 14:00:06 ok Jun 26 14:00:55 morphis: I'm also working on galaxy s2 and galaxy nexus support for libsamsung-ipc. for now I only have the firmware loader working on S2. I plan to finish it this week Jun 26 14:01:05 isn't there already an u-boot with fastboot or DFU support available? Jun 26 14:01:17 ok Jun 26 14:01:49 Alex[sp3dev]: is there much to change for the galaxy nexus in libsamsung-ipc? Jun 26 14:01:57 morphis: do you know if GPS will work with the closed-source gps lib and replicant RIL? does it need some activator from the modem side? Jun 26 14:02:24 morphis: probably not much to change, just the IPC/HDLC header format. the firmware loader is standalone, so you just need to call one function Jun 26 14:02:26 no, sorry Jun 26 14:02:36 great Jun 26 14:02:51 morphis: https://github.com/astarasikov/samsung-xmm6260-fw-loader it works for i9100 now, i9250 is incomplete Jun 26 14:03:10 morphis: I assume you have no hardware to test? Jun 26 14:03:19 i9250 is which device? Jun 26 14:03:23 just a Nexus S Jun 26 14:03:32 morphis: i9250 is galaxy nexus Jun 26 14:03:42 sand i9100? Jun 26 14:03:49 i9100 is galaxy s2 Jun 26 14:04:31 ah ok Jun 26 14:06:47 quite complex the firmware loader Jun 26 14:08:12 morphis: I should've used C++ instead.. and I plan to refactor the code when nexus works. but yes, the boot protocol is a bit compilcated, even more than nexus s Jun 26 14:15:07 why C++? Jun 26 14:16:32 keep in mind you need to integrate it in a c based environment Jun 26 14:16:55 morphis: because then it would be possible to just put a try-catch block in one place, and instead of doing a proper goto-fail blocks just throw exceptions everywhere Jun 26 14:17:47 :) Jun 26 14:19:29 I am off Jun 26 14:19:31 bye Jun 26 15:19:53 this is stupid. you need to register @ ti to download omapflash from TI, but you can get it and source at TI gforge. ok, that simplifies writing a linux loader Jun 26 15:33:15 SHR: 03Martin.Jansa 07shr-makefile * rf692c25df1da 10/conf/shr-core/bblayers.conf: shr-core: bblayers.conf: bump LCONF_VERSION to match oe-core Jun 26 15:34:22 SHR: 03Martin.Jansa 07meta-smartphone * rfc433f7dc394 10/meta-shr/conf/distro/shr.conf: meta-shr: use OEBasic signature handler Jun 26 15:34:32 SHR: 03Martin.Jansa 07meta-smartphone * rf3954414b67e 10/meta-shr/recipes-shr/3rdparty/pisi_0.5.3.bb: pisi: don't package conf.example in PN-doc Jun 26 17:02:15 SHR: 03shr-devel 07buildhistory * r4ee37c4c7f21 10/packages/ (289 files in 289 dirs): packages: Build 201206261748 of shr 20120626 for machine om-gta02 on opmbuild Jun 26 18:03:39 SHR: 03shr-devel 07buildhistory * rd632145103e2 10/packages/ (277 files in 277 dirs): packages: Build 201206261911 of shr 20120626 for machine nokia900 on opmbuild Jun 26 18:05:59 JaMa: do you use git rebase on the shr branch of meta-openembedded-contrib Jun 26 18:08:03 yes Jun 26 18:09:25 that causes a lot of forced updates (which should be avoided) you should really use pull since it (unlike rebase) doesn't rewrite history. rebase is really meant for non-publicly shared branches for that reason Jun 26 18:09:53 s/pull/merge/ Jun 26 18:09:54 losinggeneration meant: that causes a lot of forced updates (which should be avoided) you should really use merge since it (unlike rebase) doesn't rewrite history. rebase is really meant for non-publicly shared branches for that reason Jun 26 18:10:55 I know what rebase does and we discussed it with other devs and in the end I won, because I'm (almost) only one updating those branches Jun 26 18:11:12 the point is that shr branches is meant only as queue for patches for upstream (master) branches Jun 26 18:11:59 and without rebase it's easy to not notice that e.g. PR bump was already applied in upstream and the change in shr branch doesn't have own PR bump anymore Jun 26 18:12:50 if someone is willing to step up and maintain shr branches and send patches to upstream from his own branch without rebasing it.. feel free Jun 26 18:28:38 I guess it's really your choice how you want to do it (being the only maintainer) but it does make any collaboration more difficult Jun 26 18:32:07 you can still send patches against master or whole pull requests directly.. Jun 26 18:32:27 SHR: 03shr-devel 07buildhistory * r301a4278f169 10/packages/om_gta04-oe-linux-gnueabi/shr-version/ (latest shr-version/latest): packages: Build 201206262012 of shr 20120626 for machine om-gta04 on opmbuild Jun 26 18:33:36 sure, but following your branch specifically is a mess Jun 26 18:46:37 losinggeneration: mergeing upstreamable changes from shr/import or shr/merge to oe-classic without rebase was even worse mess (and I'm not going to do that again) Jun 26 18:51:14 like I said, you're the maintainer, you're free to keep you branch an inconsistent state to others using it if you need to Jun 26 19:00:59 SHR: 03shr-devel 07buildhistory * re7bfdceea8fc 10/images/crespo/eglibc/chroot-image/ (build-id image-info.txt installed-package-sizes.txt): images: Build 201206262041 of shr 20120626 for machine crespo on opmbuild Jun 26 19:01:02 SHR: 03shr-devel 07buildhistory * r8d19c0c60e0b 10/packages/crespo-oe-linux-gnueabi/shr-version/ (latest shr-version/latest): packages: Build 201206262041 of shr 20120626 for machine crespo on opmbuild Jun 26 19:14:19 hm HP released the webOS community edition: http://blog.openwebosproject.org/ Jun 26 19:16:50 it includes the LunaSysMgr Jun 26 19:16:57 the heart of the webos experience Jun 26 19:19:13 it can be run in software mode Jun 26 19:29:04 SHR: 03shr-devel 07buildhistory * r846d9e7da107 10/packages/palmpre-oe-linux-gnueabi/shr-version/ (latest shr-version/latest): packages: Build 201206262110 of shr 20120626 for machine palmpre on opmbuild Jun 26 19:41:51 LunaSysMgr looks like well written C++ code Jun 26 19:42:06 morphis: hi Jun 26 19:42:10 jake42: heyho Jun 26 19:42:12 did you want to tell me something? Jun 26 19:42:16 yes Jun 26 19:42:20 :) Jun 26 19:42:27 I had something but don't remember now what it was :) Jun 26 19:42:54 just tell me when you remember Jun 26 19:50:31 jake42: will do Jun 26 19:56:58 SHR: 03shr-devel 07buildhistory * r28cf16a5470f 10/packages/palmpre2-oe-linux-gnueabi/shr-version/ (latest shr-version/latest): packages: Build 201206262138 of shr 20120626 for machine palmpre2 on opmbuild **** ENDING LOGGING AT Wed Jun 27 02:59:58 2012