**** BEGIN LOGGING AT Tue Sep 27 02:59:57 2011 Sep 27 05:26:45 pabs3: i've raised the same question several days ago. Sep 27 05:27:11 pabs3: mrmoku came with an explanation that despite being a stupid idea it might prove useful for getting additional PR from RMS. Sep 27 05:27:13 sucks that the FSF is promoting this approach http://www.fsf.org/blogs/community/task2-openmoko Sep 27 05:27:31 yeah, that seems to be the reason :( Sep 27 05:41:36 pabs3: it doesn't bring any benefit whatsoever but further complicates the design and makes it harder to user another firmware (thus adding obstacles both for normal usage and RE as well) :/ Sep 27 05:41:51 Should probably someone try to explain it to RMS? Sep 27 05:41:55 agreed Sep 27 05:42:36 yes, definitely the FSF needs to have their position on embedded software fixed Sep 27 05:45:28 pabs3: should we start a consolidated effort (along with Werner wpwrak, lindi- and others)? ;) Sep 27 05:46:00 yes, and get Harald/osmocom guys involved Sep 27 05:46:26 Indeed Sep 27 06:07:22 PaulFertser: hmm effort to do what? Sep 27 06:10:31 pabs3: do you currently need to send the firmware to the gta04 wlan chip on every boot? Sep 27 06:13:24 lindi-: not sure, based on the project description, probably: http://projects.goldelico.com/p/gta04-main/page/FirmwareInjector/ Sep 27 06:15:26 right Sep 27 06:16:57 PaulFertser: i'm afraid rms' position there isn't very realistic. that is, except for option 1). particularly wlan is the sort of technology that needs updates from time to time. Sep 27 06:22:21 PaulFertser: but i think rms just likes his opinion to be unrealistic. my personal conclusion is to simply not touch wlan until we can handle it in a sustainable way. Sep 27 06:23:44 PaulFertser: that is, as a developer. i'm of course glad that others are making the sacrifice of their time to support it on the devices i use :) Sep 27 06:24:57 hmm, that page does not mention RMS anywhere though? Sep 27 06:26:50 lindi-: it says "FSF" right at the beginning :) Sep 27 06:30:38 wpwrak: sure. I just wonder if RMS is still the only one who can make decisions in FSF Sep 27 06:31:15 lindi-: does it matter ? :) Sep 27 06:31:45 well if you know the person behind the idea you can redirect your comments better Sep 27 06:32:37 lindi-: it's not as if the FSF would actively fight anyone making devices that don't meet their ideas of openness. they may be weird at times, but they're not apple or sisvel ;-) Sep 27 06:32:55 wpwrak: yes sure Sep 27 06:33:04 wpwrak: I'm just generally wondering how decision making works in FSF Sep 27 06:33:28 since at least to me it looks like a black box :) Sep 27 06:33:52 wpwrak: they are doing campaigning against apple and google/android devices Sep 27 06:34:50 pabs3: okay, "that don't exactly meet their ideas" ;-) Sep 27 06:36:01 anyways, having to load a firmware on boot is problematic Sep 27 06:36:38 lindi-: in what sense ? Sep 27 06:37:17 wpwrak: well then you need to include sourceless stuff to your distro Sep 27 06:38:14 but surely it is better than running non-free stuff on the main cpu Sep 27 06:40:47 lindi-: yeah, it's ugly but well-contained. the fsf ideas about somehow turning this into hardware doesn't add value. you're not more free in any non-abstract sense if you do this. in fact, you sacrifice a bit of freedom. sounds a bit like cargo cult to me :) Sep 27 06:41:38 wpwrak: well yes it'd be handy if it was in flash that you can update Sep 27 06:43:56 given that all customers of the wlan chip maker have that ability, you can expect the firmware development to depend on it as well. i.e., they won't test until it'll be perfect and works for all times, but they'll ship it when it "works" and fix anything that comes along when it comes along. Sep 27 06:45:30 so unless you happen to have a time machine somewhere in your basement (so that you can, say, get the 2015 version and thus be sure it'll work for the next 4 years), the "immutable firmware" concept doesn't work Sep 27 06:49:30 of course, nothing guarantees that the bugs that will eventually pop up will be fixed. see our experience on the gta02. so if you want to be safe with regard to maintainability, reverse-engineer the firmware or make your own chip :) Sep 27 06:51:08 wpwrak: yep I wasn't suggesting immutable firmware Sep 27 07:03:17 lindi-: good :) the contraption FSF would endorse is basically a chastity belt. i believe in the ability to make my own choices :) Sep 27 07:26:10 SHR: 03Martin.Jansa 07shr-chroot * rc932f451341f 10/ (20 files in 11 dirs): system upgrade Sep 27 07:26:11 SHR: 03Martin.Jansa 07shr-chroot * r13c9575835a8 10/ (184 files in 24 dirs): system upgrade Sep 27 08:05:28 SHR: 03Martin.Jansa 07meta-smartphone * r14028ba503d4 10/meta-fso/recipes-freesmartphone/freesmartphone/cornucopia.inc: meta-fso: cornucopia: bump SRCREV Sep 27 09:46:24 JaMa: hi, I noticed thread about u-boot on N900...any plans for rebasing GTA02 patches on top of latest u-boot and possibly upstreaming them? Sep 27 09:53:34 Martix: I spent a day trying that Sep 27 09:54:10 Martix: I guess it is possible if you can find somebody who knows u-boot and gta02 and has about four months time to play with it Sep 27 09:54:27 Martix: I eventually ended up packaging qi for debian since I wanted to have at least some boot loader Sep 27 10:28:20 good morning Sep 27 10:34:13 SHR: 03morphis 07meta-smartphone * r5eb540b71dd2 10/meta-samsung/conf/machine/crespo.conf: meta-samsung: crespo machine: prefer zImage as kernel image type Sep 27 10:34:15 SHR: 03morphis 07meta-smartphone * r3b49c3895803 10/meta-aurora/recipes-aurora/images/aurora-image.bb: meta-aurora: aurora-image: include fso2-compliance task Sep 27 10:34:22 SHR: 03morphis 07meta-smartphone * r441e39a3aa2a 10/meta-aurora/recipes-aurora/images/aurora-image.bb: meta-aurora: aurora-image: turn on debug features as default for now Sep 27 10:34:23 SHR: 03Martin.Jansa 07meta-smartphone * ra5ec42a02fd4 10/ (meta-aurora/README meta-fso/README meta-shr/README): meta-aurora,meta-shr,meta-fso: update README Sep 27 10:34:23 SHR: 03morphis 07meta-smartphone * r1c171a2f63ff 10/meta-aurora/recipes-core/tasks/task-base.bbappend: meta-aurora: task-base: port over fix from meta-shr to exclude gsmd and it's dependencies Sep 27 10:34:23 SHR: 03morphis 07meta-smartphone * r5d73e2a68e44 10/meta-aurora/recipes-aurora/images/aurora-image.bb: meta-aurora: aurora-image: add relevant aurora and qt parts of the image Sep 27 10:34:24 SHR: 03morphis 07meta-smartphone * rd4e653a229ab 10/meta-palm/recipes-core/initscripts/ (initscripts/palmpre/umountfs initscripts_1.0.bbappend): meta-palm: initscripts: add specific version of the umountfs script Sep 27 10:34:24 SHR: 03morphis 07meta-smartphone * r4ffc590f1ac2 10/meta-aurora/recipes-aurora/aurora/aurora-base.inc: meta-aurora: aurora: bump SRCREV for latest changes Sep 27 10:34:28 SHR: 03Martin.Jansa 07meta-smartphone * ree4e0092061a 10/ (7 files in 7 dirs): meta-shr, meta-aurora: drop files no longer needed Sep 27 10:34:28 SHR: 03morphis 07meta-smartphone * r7015843c6394 10/meta-aurora/recipes-aurora/aurora/ (4 files in 2 dirs): meta-aurora: import more aurora specific recipes from oe-dev Sep 27 10:34:28 SHR: 03Martin.Jansa 07meta-smartphone * r0771d6fcf8b8 10/meta-openmoko/recipes-graphics/mesa/ (mesa-dri/glamo.patch mesa-dri_7.11.bbappend): meta-openmoko: mesa-dri: add glamo support Sep 27 10:34:28 SHR: 03morphis 07meta-smartphone * r51eeda24e5cc 10/meta-palm/recipes-qt/qt4/ (qt4-embedded/palmpre/qte.sh qt4-embedded_4.7.3.bbappend): meta-palm: qt4-embedded: add specific qte.sh profile script for the palmpre device Sep 27 10:34:28 SHR: 03morphis 07meta-smartphone * r141169eb1365 10/meta-aurora/conf/distro/aurora.conf: aurora: remove blacklist entries no longer needed and blacklist external toolchains Sep 27 10:34:38 SHR: 03morphis 07meta-smartphone * rb59843791c06 10/meta-palm/recipes-kernel/linux/linux-palmpre_git.bb: meta-palm: linux-palmpre: bump SRCREV for latest version Sep 27 10:34:38 SHR: 03Martin.Jansa 07meta-smartphone * rd52ca99f5875 10/ (4 files in 3 dirs): BSPs: switch from xserver-xorg to xserver-xf86(-dri)-lite Sep 27 10:34:38 SHR: 03Martin.Jansa 07meta-smartphone * r7ea46388cf67 10/meta-shr/conf/distro/include/preferred-shr-versions.inc: SHR: prefer tslib from git (from meta-aurora) Sep 27 10:34:38 SHR: 03morphis 07meta-smartphone * re685f4fd1b3f 10/meta-aurora/recipes-aurora/images/aurora-image.bb: meta-aurora: aurora-image: do not include full qt suite but just some parts of it Sep 27 10:34:38 SHR: 03morphis 07meta-smartphone * rbabb11dba20c 10/meta-fso/recipes-freesmartphone/freesmartphone/msmcomm.inc: msmcomm: bump SRCREV to latest version Sep 27 10:34:38 SHR: 03Martin.Jansa 07meta-smartphone * r14028ba503d4 10/meta-fso/recipes-freesmartphone/freesmartphone/cornucopia.inc: meta-fso: cornucopia: bump SRCREV Sep 27 10:35:39 SHR: 03morphis 07meta-smartphone * r2f45cd1984fa 10/meta-palm/recipes-graphics/tslib/ (tslib/include-cy8mrln-header.patch tslib_git.bbappend): meta-palm: tslib: add machine specific configuration options for palmpre machine Sep 27 10:35:39 SHR: 03morphis 07meta-smartphone * r19efd6ed8353 10/meta-aurora/recipes-aurora/images/aurora-image.bb: meta-aurora: aurora-image: add missing aurora-systemmanager to image Sep 27 10:35:39 SHR: 03morphis 07meta-smartphone * r059eecdab26c 10/meta-aurora/recipes-aurora/aurora/ (4 files in 2 dirs): meta-aurora: import aurora-theme and aurora-systemmanager from oe-dev Sep 27 10:35:39 SHR: 03morphis 07meta-smartphone * r5cec7370ff0c 10/meta-shr/recipes-core/initscripts/initscripts_1.0.bbappend: meta-shr: initscripts: respect following prepends after we touched FILESEXTRAPATHS Sep 27 10:35:39 SHR: 03morphis 07meta-smartphone * rc47e10e5d148 10/meta-aurora/conf/distro/aurora.conf: meta-aurora: remove aurora distro configuration; we will now use SHR as base distribution Sep 27 10:36:40 SHR: 03morphis 07meta-smartphone * rf36a1ed467ba 10/meta-aurora/README: meta-aurora: mention meta-shr as dependency Sep 27 10:43:40 SHR: 03Martin.Jansa 07meta-smartphone * r1a27c7618920 10/meta-fso/recipes-freesmartphone/freesmartphone/msmcomm.inc: meta-fso: msmcomm: bump SRCREV Sep 27 10:45:34 sorry again and hook updated to report only master branch changes Sep 27 12:20:53 SHR: 03Martin.Jansa 07meta-smartphone * rd51a1499dfa3 10/meta-shr/recipes-connectivity/openssh/ (openssh/sshd_config openssh_5.8p2.bbappend): openssh: alter sshd config to allow empty password if someone really wants to Sep 27 13:27:45 Martix: there is bootmenu patch for n900 u-boot so maybe part of openmoko u-boot patch will be resolved upstream, but I'm not interested in merging the rest (as there is usable Qi) Sep 27 13:28:44 GarthPS: updated ld.conf.cache in shr-chroot will maybe help you with libstdc++ issue (or run ldconfig before switching to bitbake user..) Sep 27 13:28:50 old u-boot is also usable, but older Sep 27 13:29:53 I mean that I don't need newer u-boot at all for om-gta02 Sep 27 13:30:12 n900 support depends on it, that's why I was interested in it Sep 27 14:14:39 how can i re build the shr-image ? Sep 27 14:19:09 http://shr-project.org/trac/wiki/Building%20SHR#Buildinganimage Sep 27 14:20:28 pabs3: i see but i want to start again, not continue last build Sep 27 14:21:04 lxsameer: then delete your tmp directory Sep 27 14:21:45 HeinervdmOff: i want to hold my downloads, is it ok to delete the tmp folder? Sep 27 14:21:53 lxsameer: yes Sep 27 14:22:01 the downloads are in the downloads folder Sep 27 14:22:02 you should have a "downloads" folder Sep 27 14:22:09 thanks guys Sep 27 14:25:03 hmm there is not a better way to rebuild the image ? this one is a bit heavy.. but yeah it is efficient! :) Sep 27 14:27:02 GarthPS: if he says that he don't want to continue the previous build, i don't think has already build the image Sep 27 14:27:15 i think he is still building the dependencies Sep 27 14:34:34 HeinervdmOff: yeah sure. Sep 27 15:37:47 JaMa: does n900 index need rebuilding? I get checksum erros for some day now :) Sep 27 15:38:31 possible as now it's building pre images Sep 27 15:38:41 and it failed yesterday and day before Sep 27 15:39:01 NOTE: Running task 2137 of 3838 Sep 27 15:43:09 ok Sep 27 15:45:30 I just have to say, I'm really liking oe-core w/layers in contrast to the legacy monolithic oe structure Sep 27 15:46:20 good for you :) Sep 27 15:46:31 * JaMa doesn't like it so much :) Sep 27 15:47:28 JaMa: I'm sure your opinion of it is much more valid than mine since I've not worked with it nearly as long as you ;) Sep 27 15:51:06 * mrmoku actually dislikes it ;) Sep 27 15:54:20 maybe it's just because things are broken up into more logical categories (which could have been done with the legacy tree instead of having ~2000 program/library directories all in a single recipes directory) Sep 27 15:55:26 * losinggeneration shrugs Sep 27 15:55:49 losinggeneration: yeah, but having those split into thounds of different repositories makes things difficult Sep 27 15:55:52 yes with layers it better split but everything is more difficult, hard to explain, debug and you probably wont notice something nice when it happens in some other BSP layer you're not watching closely Sep 27 15:56:06 indeed Sep 27 15:56:50 and the layers are far from nice plugable boxes from that yocto PR diagram :) Sep 27 15:57:20 once you add some layer you can screw upgrade-paths from whole feed if you later decide to remove it Sep 27 15:57:58 and layer dependencies are sometimes circular etc.. Sep 27 15:58:32 that last one sounds like a bug to me Sep 27 15:59:07 not really as ie aurora-image is now valid target if you're building with SHR as distribution Sep 27 15:59:17 that's why I've added meta-aurora layer to shr-core bblayers Sep 27 16:00:02 but on the other hand.. morphis expects some bbappends (which are used by SHR as distributio) to be used so he can expect some behavior from system Sep 27 16:00:45 so if someone will decide to build aurora-image then he should also adopt some bbappends from meta-shr (that's why he added meta-shr to meta-aurora README as dependency) Sep 27 16:02:51 * JaMa off, bye Sep 27 16:06:41 just the way that was described, it sounds like a one way dependency (aurora depending upon shr) Sep 27 16:10:22 When i press the TS on my FR i can clearly hear a high-pitch hum. Sep 27 16:10:53 For as long as i keep it pressed Sep 27 17:14:35 freesmartphone.org: 03angelo 07aurora * rbf6ea496771d 10/aurora-applications/app-firstuse/main.qml: aurora-firstuse: use launchApplication instead loadApplication due new aurora-daemon rework Sep 27 17:14:36 freesmartphone.org: 03angelo 07aurora * rf2b49542f227 10/ (479 files in 63 dirs): Merge branch 'master' of git.freesmartphone.org:aurora Sep 27 17:34:14 PaulFertser: doesn't it weird stuff like reducing framerate during ts-A/D ? Sep 27 17:34:46 DocScrutinizer: not on 2.6.29 i think. Sep 27 17:34:48 :) Sep 27 17:34:51 DocScrutinizer: hello there Sep 27 17:35:00 hi Sep 27 17:36:40 DocScrutinizer: declaring TI's copyright on behalf of "the Presidium of the Supreme Soviet" sounds like a nice idea, doesn't it ;) Sep 27 17:37:10 err what? Sep 27 17:38:35 DocScrutinizer: http://lists.openmoko.org/pipermail/community/2011-September/065503.html Sep 27 17:40:12 PaulFertser: :-P Sep 27 17:42:26 hi DocScrutinizer Sep 27 17:42:53 hehe Sep 27 17:43:52 DocScrutinizer, do you remember how to make the n900 charge faster when the wall charger is connected? Sep 27 17:48:17 GNUtoo: did gprs work with manually starting fsonetworkd? Sep 27 17:48:26 no Sep 27 17:48:29 it failed Sep 27 17:48:36 hmm, strange Sep 27 17:48:46 it works fine for me Sep 27 17:49:06 GNUtoo: please elaborate Sep 27 17:49:44 DocScrutinizer, charging takes too much time with the wall charger Sep 27 17:50:00 I'm not sure but I remember that the scripts were able to detect the wallcharger(I know how) Sep 27 17:50:15 but I don't know what to do when the wallcharger is detected Sep 27 17:50:58 I read 2 different scripts Sep 27 17:51:08 and I still don't know where the magic is Sep 27 17:52:17 the magic is in setting max-usb-current to either 100, 500, 850 or unlimited Sep 27 17:52:29 ok Sep 27 17:52:49 how do I do that exactly? Sep 27 17:53:00 i2cset 0xsomething 0xsomethingelse etc... Sep 27 17:53:12 yes Sep 27 17:53:14 :-) Sep 27 17:53:34 and I found the values in the documentation of the chip(datasheet) ? Sep 27 17:53:41 or is there some faster way Sep 27 17:53:58 iirc shadowjk had a nice short summary about register meanings i his charger2 script Sep 27 17:54:04 ok Sep 27 17:54:08 I'll look right now Sep 27 17:54:32 http://enivax.net/jk/n900/charge21.sh.txt ? Sep 27 17:55:53 yup Sep 27 17:56:17 ah right it's in there Sep 27 17:56:21 I missed that 21 script Sep 27 17:56:24 thanks a lot!!!! Sep 27 17:57:03 terrible Sep 27 17:57:23 it's not that good commented as I thought it was Sep 27 17:57:26 Hm, are mozilla guys mad? What's up with their versioning? :/ Sep 27 17:58:34 Table 6. Control Register (READ/WRITE) Sep 27 17:58:36 Memory Location: 01, Reset State: 0011 0000 (30H) Sep 27 17:58:43 B7 B6 Sep 27 17:59:01 00-USB host with 100-mA current limit, 01-USB host with 500-mA current limit, Sep 27 17:59:03 10-USB host/charger with 800-mA current limit, 11-No input current limit Sep 27 17:59:04 (default 00) Sep 27 17:59:49 ok Sep 27 18:00:35 i2cset -y -m 0b11000000 --bus=2 addr=0x6b 0b10000000 == 800mA Sep 27 18:00:56 (fix syntax!) Sep 27 18:01:36 the charger is more than 800mA Sep 27 18:01:44 so I guess I should set to unlimited Sep 27 18:11:02 PaulFertser: in short, yes. They decided bigger is better, so they hope to be on FIrefox 100 by the end of next year Sep 27 18:11:41 losinggeneration: i never liked it anyway :/ Sep 27 18:12:22 their x.x.x releases actually made sense at least. Now it's just x.x I think Sep 27 18:12:50 at least, made sense in the "major.minor.bugfix" release scheme Sep 27 18:16:32 DocScrutinizer, is it normal that my laptop does a noise when I plug my n900 to one of its usb ports? Sep 27 18:16:49 errrr no Sep 27 18:17:32 and tbh I couldn't see how that noise gets generated Sep 27 18:18:00 unless it's on purpose via a daemon and audiocard Sep 27 18:18:18 no Sep 27 18:18:41 oh man, I can't even imagine what would be going wrong if the usb port itself where making a noise when plugged in... Sep 27 18:19:19 GNUtoo: i once had a "magic" noise that dependent on the keyboard layout i used (en or ru). Sep 27 18:19:28 GNUtoo: i had noise with ru and no noise with en. Sep 27 18:19:34 ok Sep 27 18:19:35 lol Sep 27 18:19:54 I had the same noise when 2 charger programs were present at once.... Sep 27 18:20:03 maybe your laptop has a really crappy PMU and that one answers sudden load changes on 5V rail with some noise from the chokes? Sep 27 18:20:22 GNUtoo: turned out the noise was emitted by the PSU because when i switched to ru, i had two extra leds on my keyboard lit. Sep 27 18:20:38 lol ok Sep 27 18:20:48 exactly Sep 27 18:21:03 possible I'll put an allimented hub Sep 27 18:22:10 * DocScrutinizer glares on his fresh 5pin micro-B usb component Sep 27 18:22:19 * DocScrutinizer glares closer Sep 27 18:22:28 * DocScrutinizer feches magn glass Sep 27 18:22:57 it;s like a shrill noise Sep 27 18:30:00 mickeyl, hi Sep 27 18:34:12 does somebody knows how in fso I should get kenrel events? Sep 27 18:34:12 there was a class right? Sep 27 18:36:56 hi morphis Sep 27 18:37:06 heyho Sep 27 18:37:12 do you know userland API || fso ? Sep 27 18:37:20 I want to get kernel events Sep 27 18:37:20 like for instance Sep 27 18:37:25 the charger get plugged in Sep 27 18:37:33 I want to act accordinly Sep 27 18:37:33 uevent you mean? Sep 27 18:37:35 (on n900) Sep 27 18:37:36 yes Sep 27 18:37:43 there was an fso lib for that Sep 27 18:37:48 ye Sep 27 18:37:49 s Sep 27 18:38:19 the kobjectnotifier Sep 27 18:38:23 look in libfsobasics Sep 27 18:38:27 ok thanks Sep 27 18:38:38 I already do this in the palmpre_quirks plugin of fsodeviced Sep 27 18:39:19 ok nice Sep 27 18:39:37 btw how to develop cornucopia now that the devshell is gone? Sep 27 18:40:36 devshell is gone? Sep 27 18:40:44 I got it sometime ago Sep 27 18:40:47 in oe-core Sep 27 18:40:51 bitbake -c devshell .. Sep 27 18:41:14 ah ok Sep 27 18:41:16 I'll retry Sep 27 18:41:27 devshell should never go Sep 27 18:41:35 last time I did -c devshell it didn't work Sep 27 18:41:37 then I will back it up in meta-shr/meta-azrora Sep 27 18:41:40 hm Sep 27 18:41:42 so how does it work now? Sep 27 18:41:45 I -c devshell Sep 27 18:41:48 a console appear Sep 27 18:41:52 but what to type in it? Sep 27 18:41:56 oe_runconf? Sep 27 18:41:59 etc... Sep 27 18:42:00 ? Sep 27 18:42:34 currently I can't try it, QT for qurora is compiling Sep 27 18:44:35 ah ok Sep 27 18:44:40 qt is a mess Sep 27 18:44:44 it needs hours to compile Sep 27 18:44:46 I've fixes Sep 27 18:44:50 for what? Sep 27 18:44:51 ah not for that Sep 27 18:44:56 look here: Sep 27 18:45:07 https://github.com/eukrea/ Sep 27 18:45:15 updates for QT Sep 27 18:45:21 fixes for the SDK Sep 27 18:45:22 etc... Sep 27 18:45:43 they were posted to oe-core and oe-dev etc.... Sep 27 18:45:48 but since they were in release mode.... Sep 27 18:45:49 btw. we need to work on our process to bring things upstream to meta-oe nd oe-core Sep 27 18:45:53 the patches weren't accepted Sep 27 18:46:09 ok Sep 27 18:46:13 release-mode is over I think Sep 27 18:46:16 what do you want to bring upstream? Sep 27 18:46:21 qt patches Sep 27 18:46:22 yes Sep 27 18:46:25 ok Sep 27 18:46:30 I submitted them to the contrib/shr branch Sep 27 18:46:35 ok Sep 27 18:46:41 but who starts the pull request? Sep 27 18:46:49 JaMa? Sep 27 18:47:37 he does? Sep 27 18:47:50 it's unclear Sep 27 18:47:59 so we should write down the process somewhere Sep 27 18:48:03 ok Sep 27 18:48:57 so we can speed up things I think Sep 27 18:48:59 in the README Sep 27 18:49:01 in meta-smartphone Sep 27 18:49:20 we can review the patches on our self and then start the pull request to get them reviewed by the other oe people Sep 27 18:49:41 ok Sep 27 18:50:00 we also need some higher builder coordination Sep 27 18:50:02 since we rebase stuff etc... Sep 27 18:50:07 yes Sep 27 18:50:08 and don't do PRINC etc... Sep 27 18:50:14 but we should Sep 27 18:50:16 or not always do it Sep 27 18:50:27 we need to document what to -c cleansstate Sep 27 18:50:46 most of the time it's on shr wiki tough Sep 27 18:50:50 yes Sep 27 18:50:51 but not always I bet Sep 27 18:51:16 we should always use meta-smartphone + our contrib branches of oe-core and meta-oe Sep 27 18:51:33 and we need to think about how we do releases Sep 27 18:52:00 at least for aurora Sep 27 18:52:17 but how does release scales? Sep 27 18:52:20 because if there is always something in release it block the developement Sep 27 18:52:29 for instance oe-core was blocked Sep 27 18:52:41 but then if shr is in release at another time Sep 27 18:52:47 etc... Sep 27 18:53:00 there would be something blocked at every moment Sep 27 18:53:10 a release should not block development Sep 27 18:53:19 when we do a release we should branch Sep 27 18:53:29 master is open for development all time Sep 27 18:53:30 ok Sep 27 18:53:34 in oe-core it did Sep 27 18:53:42 it should not I think Sep 27 18:53:47 ok Sep 27 18:54:00 but as I understand richard it was not the best way to do the release preparation Sep 27 18:54:14 ok Sep 27 18:54:33 so they failed bad the release process and it won't happen again? Sep 27 18:54:35 *badly Sep 27 18:55:09 I think so Sep 27 18:55:21 ok nice Sep 27 18:55:22 my problem currently is I have not so much time Sep 27 18:55:32 same here Sep 27 18:55:45 btw what is the line to change in aurora? Sep 27 18:55:47 but it will end next or one week later Sep 27 18:55:55 to make it work on om-gta02 Sep 27 18:55:56 aurora is mostly brought to oe-core Sep 27 18:56:01 ah Sep 27 18:56:04 ok Sep 27 18:56:04 I did it already Sep 27 18:56:12 ok so I get it automatically? Sep 27 18:56:15 it should automatically detect the screensize Sep 27 18:56:19 with latest SRCREV Sep 27 18:56:19 ok nice Sep 27 18:56:23 I hope so Sep 27 18:56:26 ah, I feared that Sep 27 18:56:30 is aurora autorev? Sep 27 18:56:31 just tested the compilation :) Sep 27 18:56:35 currently not Sep 27 18:57:01 but you can add AURORA_SRCREV = "${AUTOREV}" to your local.conf Sep 27 18:57:02 ok Sep 27 18:57:04 that should work Sep 27 18:57:05 ok Sep 27 18:57:08 I'll do that Sep 27 18:57:10 thanks a lot Sep 27 18:57:16 no problem Sep 27 18:57:27 so your trying to get aurora ready on om-gta02? Sep 27 18:57:49 no, for now I just want to try aurora Sep 27 18:57:53 and I lack a palm pre Sep 27 18:58:10 and the palm person didn't respond anymore Sep 27 18:58:13 hm Sep 27 18:58:13 bad Sep 27 18:58:20 what about buying one on ebay? Sep 27 18:58:20 so I'm waiting for beeing in italy again Sep 27 18:58:26 where? Sep 27 18:58:29 when you will be there? Sep 27 18:58:35 soon Sep 27 18:58:36 in france? Sep 27 18:58:42 ok Sep 27 18:58:48 they are simlocked Sep 27 18:58:52 I want no simlock Sep 27 18:58:55 else they're useless Sep 27 18:59:50 hm Sep 27 18:59:58 maybe I can buy one for you and send it to you Sep 27 19:00:06 they are all unlocked here in germany Sep 27 19:00:55 I've a better idea Sep 27 19:01:19 we both go to SHRFSO conference Sep 27 19:01:39 how many pres do you already have? Sep 27 19:01:46 because you could sold me yours Sep 27 19:01:54 once you're there Sep 27 19:02:07 hm Sep 27 19:02:11 I have one broken Sep 27 19:02:18 one repair but with bad quality Sep 27 19:02:27 s/repair/repaired/ Sep 27 19:02:34 hmmm Sep 27 19:02:37 and one working which I am using for development Sep 27 19:02:38 I want an usable one Sep 27 19:02:42 ok Sep 27 19:02:43 they are very cheap today Sep 27 19:02:45 50 Euro Sep 27 19:02:49 yes I know Sep 27 19:02:55 but I want a working one at 50E Sep 27 19:03:00 you can get Sep 27 19:03:07 not some palm with broken GPS or broken something Sep 27 19:03:07 everyone is selling his pre today :) Sep 27 19:03:11 ok Sep 27 19:03:24 maybe some collegue has one left Sep 27 19:03:28 paulk, had issues with second hand devices Sep 27 19:03:32 ok Sep 27 19:03:48 and what about batteries? Sep 27 19:04:08 quality? Sep 27 19:04:58 btw. I am mostly done with fsopreferencesd Sep 27 19:05:11 ok Sep 27 19:05:31 quality???? Sep 27 19:05:36 I was talking about batteries, new ones are hard to find? Sep 27 19:06:17 how much are the pre-plus btw? Sep 27 19:06:17 ah ok Sep 27 19:06:23 they have 16G Sep 27 19:06:24 no you can still order them on the internet Sep 27 19:06:32 the pre plus, yes Sep 27 19:07:10 ok Sep 27 19:07:32 because here in my french town they don't sell batteries anymore and tell you to buy a new phone instead Sep 27 19:07:40 :) Sep 27 19:07:50 about your qt patches, they will go upstream? Sep 27 19:07:51 kind of useless, I want a gta02 battery and already have newer phones.... Sep 27 19:07:54 yes Sep 27 19:08:02 ottavio also have some QT patches Sep 27 19:08:23 *otavio Sep 27 19:09:27 ok Sep 27 19:10:26 any news on nexus S btw? Sep 27 19:12:44 still not Sep 27 19:12:58 I have the plan fixed in my head how to proceed but the time is missing Sep 27 19:13:09 I ordered also the components to get the serial console Sep 27 19:13:10 ok Sep 27 19:13:16 then I'll have to help you Sep 27 19:13:17 I guess Sep 27 19:13:19 and started some bits for modem integration Sep 27 19:13:20 if I've the time Sep 27 19:13:23 ok Sep 27 19:13:23 ok Sep 27 19:13:27 that would be nice Sep 27 19:14:10 paulk, got his other nexus S repaired, so I'll get the one that has broken front camera, which is very nice Sep 27 19:14:20