**** BEGIN LOGGING AT Wed Dec 23 02:59:57 2009 Dec 23 03:08:19 why Dec 23 03:12:41 Abyssul: electroinduction magnet + harddrive? Dec 23 03:26:16 rwhitby: with zenity, are you attempting a direct port? Dec 23 03:26:41 like, what about adding other dialog types Dec 23 03:26:59 like a "slider" type, that returns a number between 0 and 100 Dec 23 03:32:28 I'm surprised zenity doesn't lready have one of those. Dec 23 03:52:07 zenity again? Dec 23 03:53:52 i cant wait for 1.3.5 to officially come out and see if anything is fixed/changed Dec 23 03:54:03 compared to beta Dec 23 04:02:57 PuffTheMagic: are you anti zenity? lol Dec 23 04:03:32 well, unless I am mistaken, zenity is a cli tool that makes gnome/gtk guis Dec 23 04:03:43 so i cant see how that is of any use on the pre Dec 23 04:12:13 PuffTheMagic: when did the beta go out? Dec 23 04:12:46 i don't understand the zenity stuff either Dec 23 04:15:08 PuffTheMagic Dec 23 04:15:12 for patches Dec 23 04:15:17 and optware Dec 23 04:15:28 like a customize carrier string patch Dec 23 04:15:45 that prompts you using mojo to enter the text you wish to have as your carrier string Dec 23 04:16:22 when you install it Dec 23 04:17:31 hmm... interactive user-input install Dec 23 04:17:45 thats what zenity would allow the patch to do Dec 23 04:17:52 or optware Dec 23 04:19:24 i am still confused how it draws to the screen or grabs the input i suppose .. i was also under the impression of the gnome/gtk stuff :( Dec 23 04:19:35 like Dec 23 04:19:40 for the question message Dec 23 04:19:49 it comes up in the confirmation/dash area saying "yes, no?" Dec 23 04:19:58 or whatever the params its called with tell it to Dec 23 04:20:48 so it's not really zenity per se, but the same idea as zenity allowing the commandline to send notifications for commandline input ? Dec 23 04:21:04 right Dec 23 04:21:06 gotcha Dec 23 04:58:23 bpadalino: zenity-compatible front-end, displaying the user prompting on webos Dec 23 04:58:47 gotcha Dec 23 04:58:48 oil: yeah, we could do a superset if we want, but I do want complete zenity compatibility on the command line Dec 23 04:59:19 (i.e a superset is no problem, as long as the full zenity is there and fully compatible) Dec 23 04:59:33 the rationale is cause then we don't need to document anything - we just point to zenity Dec 23 05:01:10 rwhitby, I built preware completely on 32-bit gentoo, but on fedora am having a problem with their ant package Dec 23 05:02:19 jacques: ok. Dec 23 05:03:16 rwhitby, this mean anything to you: "The import java.net.InterfaceAddress cannot be resolved" Dec 23 05:03:26 jacques: nope Dec 23 05:03:40 I think it's because fedora's and package doesn't use sun's jdf Dec 23 05:03:51 s/jdf/jdk/ Dec 23 05:03:51 jacques meant: I think it's because fedora's and package doesn't use sun's jdk Dec 23 05:13:18 jacques: that's good news that you could get the service stuff working fine from the repo on gentoo, cause gentoo is what PuffTheMagic uses Dec 23 05:15:51 well i have an overlay of ebuilds for some older versions of stuff Dec 23 05:17:09 jacques: yeah fedora switched to icedtea i believe Dec 23 05:17:54 PuffTheMagic: what I mean is that you should be able to reproduce exactly what the autobuilder does on a gentoo checkout of preware/build.git Dec 23 05:17:57 it's strange; they have like 4 different java engines Dec 23 05:18:08 openjdk is the default install Dec 23 05:18:15 but their ant package pulls in java-1.5.0-gcj.x86_64 Dec 23 05:18:37 I had practically no trouble at all on gentoo Dec 23 05:19:10 I just had to install the sun jdk in addition to the jre which I already had Dec 23 05:19:18 (on gentoo) Dec 23 05:19:43 I have the sun jre on fedora too - it's the only thing that worked well with webosquickinstall Dec 23 05:20:09 I'm going to look into installing sun jdk on fedora and then maybe building my own ant Dec 23 05:20:13 jacques: it works on gentoo cause i use gentoo ;) Dec 23 05:20:13 so much for "write once, run anywhere", hey? Dec 23 05:20:38 it build with all javac's Dec 23 05:20:43 gcj does not count Dec 23 05:21:29 I would probbly never look at fedora except it's what we use at work and I have to keep my hand in it Dec 23 05:21:52 since one of my responsibilities is making custom versions of it Dec 23 05:24:49 rpm database recovery? Dec 23 05:25:17 I so prefer the debian available list with the weird text corruption, fix it and it's fine Dec 23 05:41:37 I installed sun jdk on F12 and then used alternatives to set its javac as the default, and then my wolservice completed :-) Dec 23 05:43:19 (wolservice build that is) Dec 23 05:57:32 PuffTheMagic: when you call LSMessageGetPayloadJSON(message); in client.c in wIRCd, do you think the resulting json_t *object needs to be freed by the caller or not? Dec 23 05:57:46 (can't tell from Palm's header files) Dec 23 05:58:13 no its a local var Dec 23 05:58:54 so you don't think that LSMessageGetPayloadJSON allocates memory? Dec 23 05:59:20 (since it could be any size hierarchy of JSON objects as a tree) Dec 23 06:00:24 I was thinking that maybe we need to call json_free_value(&object) on it after we've finished using it Dec 23 06:00:46 (I'm adding an "echo" method to the example service) Dec 23 06:01:38 Hey anyone up Dec 23 06:02:48 gitorious is slow :-\ Dec 23 06:03:29 It would be a nice patch to turn off the vibrate and/or turn off sound on incoming instant messages .. Will make it more of an I'm Dec 23 06:03:32 jacques: yeah, we need to change the way we check out patches from there, so we only pull the tree once for each tag rather than once for each patch Dec 23 06:03:33 I'm getting ~20kiB/s on checkouts Dec 23 06:04:04 Now it takes so long when it vibrates and trys to update the screen Dec 23 06:04:09 rwhitby, yeah I noticed that it was seemingly pulling the same thing over and over Dec 23 06:04:29 jacques: yep, I've got a very naieve implementation in there Dec 23 06:04:58 it should pull it once, tarball it into downloads, and use it from downloads if it's already there. Dec 23 06:05:05 agreed Dec 23 06:06:41 well, it's midnight here and I gotta let my friend get to sleep Dec 23 06:06:43 hmm - it's written to do that actually Dec 23 06:06:52 do there's a bug Dec 23 06:06:52 maybe some check is failing Dec 23 06:06:56 yeah Dec 23 06:06:58 rwhitby: we should move all the patches to the main git server Dec 23 06:07:04 I'll be on from home in a little while Dec 23 06:07:04 then make gitorious mirror our repo Dec 23 06:07:10 untill all urls are fixed Dec 23 06:14:08 PuffTheMagic: answered my own question. object should not be freed by the caller, just like you said (and like you have correctly coded in wIRCd) Dec 23 06:15:11 exampleservice now has an echo method Dec 23 06:15:40 next to add a launch method Dec 23 06:16:27 launch method? Dec 23 06:20:31 rwhitby: what is a launch method and why is it needed? Dec 23 06:26:11 cant imagine why a launch method would be needed Dec 23 06:29:32 that's what you said about zenity too Dec 23 06:31:02 rwhitby: i dont even get how zenity would run in luna, and if you rewrote it for luna then its no longer zenity Dec 23 06:31:30 but it sounds like you are making a "is-running" method just so you can use luna-send to start it Dec 23 06:31:38 whch make no sense with a C service Dec 23 06:31:41 zenity is a command line application Dec 23 06:31:51 it takes arguments on the command line Dec 23 06:31:53 yeah i know what zenity is Dec 23 06:31:56 it displays a gui to the user Dec 23 06:31:56 and make a gui from cli Dec 23 06:32:09 it takes a gui reponse from the suer Dec 23 06:32:09 i dont see how that can be used in luna Dec 23 06:32:21 it returns the gui response on the command line Dec 23 06:32:32 yeah i exactly what it is Dec 23 06:32:52 in this case the gui is not a linked in GTK library, it is a launch of a webOS card, and a service call back with the response from the user. Dec 23 06:33:22 so u dont want zenity Dec 23 06:33:23 using exactly the same method that ipkgservice uses to ask the user a question Dec 23 06:33:29 you want a webos/port/fork of it Dec 23 06:33:53 thats a little different than just saying zenity Dec 23 06:33:58 sigh Dec 23 06:34:28 you should read the backlog more ... Dec 23 06:34:48 reading is boring Dec 23 06:34:54 cause i have time for that Dec 23 06:35:09 yeah, and I have time to repeat myself just for your benefit too ... Dec 23 06:36:18 you were the one that just brought it up.... but it would have taken 2 seconds to say a port of zenity to webos Dec 23 06:36:20 or something like that Dec 23 06:36:37 someone considerate to other's time would say "oh, I've come into the middle of a discussion about zenity on webOS, perhaps I should go back and read what had been said in the last hour, rather than just coming in and saying that it's not needed without any other context for the conversation" Dec 23 06:37:57 for all i knew you guys were gonna leave luna to run some directfb gtk version of zenity.... idk Dec 23 06:38:47 and you brought this up not me... we were talking about the example service Dec 23 06:38:59 I'm talking about the other day, not now. Dec 23 06:38:59 which should not need a "is-running" method Dec 23 06:39:23 I have no idea what you are talking about with an "is-running" method Dec 23 06:39:44 a launch method is what ipkgservice does to launch the webOS card. Dec 23 06:40:15 http://developer.palm.com/index.php?option=com_content&view=article&id=1590#ApplicationManager-launch Dec 23 06:41:40 and it what a zenity front-end will use to launch the webOS card which implements the UI to the user. Dec 23 06:41:56 and therefore needs to be supported by the C service which will be part of the zenity front end Dec 23 06:42:39 (since the service needs to recieve the response sent back from the user by the webOS card) Dec 23 06:43:13 yeah i get how it works Dec 23 06:56:01 PuffTheMagic: awesome work you've done working out how all this C service stuff works, BTW. Dec 23 06:56:26 especially the subscription stuff Dec 23 06:56:50 i know how to use the iterators too Dec 23 06:57:03 for when you use LSSubscriptionProcess Dec 23 06:57:07 or what ever that method is Dec 23 07:03:54 was there any other doco you found other than the header files, or was it all working it out from no information/ Dec 23 07:03:56 ? Dec 23 07:05:09 howdy Dec 23 07:05:49 rwhitby: just playing with the code Dec 23 07:05:54 no other docs Dec 23 07:06:19 oh well Dec 23 07:06:28 libpurpleadapter did give some cluses Dec 23 07:06:29 clues Dec 23 07:11:34 no java needed? Dec 23 07:11:46 tmzt: correct Dec 23 07:12:17 which (as PuffTheMagic correctly continually reminds me) makes it much easier to start and stop services without impacting the rest of the phone Dec 23 07:12:26 i might make python bindings for it ;) Dec 23 07:12:40 since i have to learn python Dec 23 07:13:14 great, java slowdown seems to be one of the issues with pre Dec 23 07:13:29 walling that /proc/cpuinfo another Dec 23 07:13:34 who does that? Dec 23 07:13:48 PuffTheMagic: please do - I put mjson and dbus-python into optware recently, cause I had the same idea of python bindings to the service API for such things as python scriptable profile triggers Dec 23 07:14:14 look at ologicd very cool tricks Dec 23 07:14:15 did u put liblunaservice in it? Dec 23 07:14:22 PuffTheMagic: yep Dec 23 07:14:28 for that kind of situation aware thing Dec 23 07:15:00 tmzt: the lua stuff from openmoko? Dec 23 07:15:21 tmzt: that's exactly what I'm aiming at Dec 23 07:15:45 hmm - I wonder if a port of that might be more appropriate ... Dec 23 07:15:47 yes I think it's lua but the scripts themselves are another language Dec 23 07:16:13 talk to the developer Dec 23 07:16:21 forget who it is right now though Dec 23 07:16:24 * jacques2 really wants to learn lua Dec 23 07:16:41 tmzt: this one, right: http://build.shr-project.org/fsoshrudcon/FSOSHRUDCON09-Ologicd-Didier-Ptitjes.pdf Dec 23 07:17:01 yes Dec 23 07:17:02 but now I'm thinking about ecmascript Dec 23 07:17:03 didjier Dec 23 07:17:20 uh, ptitjes Dec 23 07:17:30 or that, simple and easy towrite Dec 23 07:17:42 not easy to parse as you need some overhead Dec 23 07:17:48 unless you go with gjs Dec 23 07:18:19 hmm, I've played with that to write a gnome3 phone ui but it will be too slow for my device (not cortex) Dec 23 07:19:25 tmzt: ah, I was actually thinking of org.freesmartphone.events: http://www.freesmartphone.org/index.php/Architecture#Events Dec 23 07:19:50 http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Events.html Dec 23 07:19:59 then just use upstart? Dec 23 07:20:19 it has events already Dec 23 07:20:22 it uses yaml Dec 23 07:20:35 yeah, it's for audio and things Dec 23 07:20:44 not advanced enough for ptijles stuff Dec 23 07:20:53 I think he's replacing it Dec 23 07:21:10 http://www.freesmartphone.org/index.php/Brainstorm/fsoeventsd Dec 23 07:21:11 I need a standalone version for my project Dec 23 07:39:02 * rwhitby bbl Dec 23 09:32:21 hello? Dec 23 09:33:24 I'm a error wit preware on launch I get onfeed error Dec 23 09:33:34 having a error* Dec 23 10:21:55 anyone know how to fix a touchstone that keeps cycling through charging on and charging off? Dec 23 10:32:48 pray to the touchstone gods Dec 23 16:36:46 what's good Dec 23 16:42:28 rwhitby: ping Dec 23 17:54:54 infobot: run full diagnostic sweep Dec 23 18:03:07 infobot: make me a sandwich Dec 23 18:03:08 make: *** No rule to make target `me a sandwich'. Stop. Dec 23 18:04:07 haha Dec 23 18:05:14 infobot: make me the perfect woman Dec 23 18:05:16 make: *** No rule to make target `me the perfect woman'. Stop. Dec 23 18:05:30 That sounds wrong... Dec 23 19:01:50 the uptime on my Pre is still bugging me. it's just wrong. Dec 23 19:04:07 has there been any work on adding new audio codecs? I would like ogg-vorbis and FLAC. I'm sure lots of other people would too. Dec 23 19:10:26 infobot: tell rwhitby I'm onto him. Dec 23 19:12:32 http://www.webos-internals.org/wiki/Gstreamer Dec 23 19:14:57 thanks DarkSpecter Dec 23 20:13:15 are the arm6 and arm7 binaries supposed to be different? I can't find where they are built with different compiler options, and readelf does not indicate any differences Dec 23 20:14:59 geist said they were different. Dec 23 20:15:08 one is for pixi other for pre Dec 23 20:17:41 you probably mean armv6 and armv7 Dec 23 20:17:55 (the v is vvvery important) Dec 23 20:17:57 I'm looking at the output of the preware build system. I cannot detect any difference between the arm6 and arm7 binaries. nor can I detect any reason they should be from looking at the Makefiles Dec 23 20:18:15 roxfan: yes, you are correct. sorry :-) Dec 23 20:18:40 armv7 includes some extra instructions which are probably not used in common programs Dec 23 20:19:00 for example NEON simd instructions Dec 23 20:19:22 and am I correctly interpreting that the binaries are using the Thumb instruction set? Dec 23 20:19:55 they might Dec 23 20:20:03 roxfan: so, for most cases (binaries not using the special armv7 instructions) the same binary would run on Pre and Pixi ? Dec 23 20:20:11 both v6 and v7 support thumb and arm modes Dec 23 20:20:30 not sure what's pixi but probably yes Dec 23 20:20:40 lemme check the changes again... Dec 23 20:20:45 my understanding is Thumb gets you smaller binaries but trades off execution speed Dec 23 20:21:08 anyone here have a Pixi ? Dec 23 20:23:44 if I am correctly interpreting readelf output, the Pre distro and Preware are built only with v4 (thumb) instructions: Tag_CPU_arch: v4T Dec 23 20:23:52 hmm it seems there are a couple of thumb instructions in v7 which are not supported in v6 Dec 23 20:24:44 v4t would be weird... v6 has a lot of useful instructions which reduce code size Dec 23 20:25:02 does the Pixi proc have a VFP (hardware floating point) unit? Dec 23 20:25:45 Pre does, and I *think* it's being used: Tag_ABI_FP_exceptions: Needed Dec 23 20:25:55 ARM1136EJ-S Dec 23 20:26:03 hmm, no VFP it seems Dec 23 20:28:11 maybe I need to disassemble some binaries to see which floating point instructions are used Dec 23 20:28:38 it's possible that pixi uses softfloat Dec 23 20:29:53 roxfan: if that's true, and my understanding of the above is correct, I would expect Preware binaries using floating point instructions to fail on the Pixi Dec 23 20:30:19 msm7x27 has a floating point unit Dec 23 20:30:32 aha. Dec 23 20:30:42 http://pdadb.net/index.php?m=cpu&id=a7627&c=qualcomm_msm7627 this is wrong then? Dec 23 20:30:51 or the fpu is not vfp? Dec 23 20:31:19 I'm not sure about vfp, but I know we switched 7x25->7x27 midway partly due to wanting a FPU Dec 23 20:31:36 webkit sure does love floats Dec 23 20:31:52 jacques: i _think_ that it's possible to compile binary with softfloat so that it will use vfp if it's present Dec 23 20:32:31 roxfan: maybe, but I have never encountered such a thing Dec 23 20:33:26 the ways I understand in order of low performance to high are 1) kernel FP emulation 2) softfloat 3) real FP unit Dec 23 20:33:37 since javascript is all floats all the time, i would think that would be important to a web-browser based os. Dec 23 20:33:49 in 1) the kernel traps FP instructions and emulates them - very slow Dec 23 20:34:16 in 2) the toolchain replaces FP instructions with integer code Dec 23 20:34:39 in 3) the hardware FPU handles the FP instructions Dec 23 20:35:32 i think softfloat just uses libc functions for all fp manipulations Dec 23 20:35:48 and so libc can choose to use hw or sw Dec 23 20:36:08 but what about FP instructions which are not the result of a libc call Dec 23 20:36:20 those would not be handles Dec 23 20:36:24 handled Dec 23 20:36:30 they're not supposed to be in binary if it's compiled with softfloat... Dec 23 20:37:47 my point is softfloat is a pervasive toolchain feature. all FP instructions everywhere (libc and apps) are replaced with integer code Dec 23 20:38:22 you cannot generally swap a hard-float and soft-float libc without rebuilding everything Dec 23 20:38:41 hmm, http://www.codesourcery.com/sgpp/lite/arm/portal/kbentry27 Dec 23 20:39:14 movw/movt is the biggest thing you'll see different Dec 23 20:39:22 it's an armv7 thing and the compiler uses the hell out of it Dec 23 20:39:56 maybe i should read the eabi specs... Dec 23 20:40:04 (again) Dec 23 20:41:01 but the use of it does not change anything about the abi, so it's not marked as such in the ELF bits Dec 23 20:42:37 roxfan: I read that page you linked, and basically is says if you build binaries that way, they will not use the hardware floating point unit, but they can interoperate with code which does Dec 23 20:42:40 not the other way around Dec 23 20:43:06 so you can get compatibility by giving up speed Dec 23 20:43:53 geist: yes that's bringing back memories. I recall disassembling code on the Nokia N800 (OMAP2) to prove that hardware float was / was not being used Dec 23 20:44:33 when the N800 came out, it was not using the hardware FPU, nokia used the same toolchain as their previous device, which did not have one Dec 23 20:45:21 we got significant speed increases for some workloads by rebuilding the libc and specific apps Dec 23 20:45:42 I dunno if they ever changed it officially Dec 23 20:46:53 oh, its the 23rd! Dec 23 20:47:02 its festivus! Dec 23 20:47:14 geist: when I look at a readelf dump and see "Tag_CPU_arch: v4T" am I correct that means only armv4 thumb instructions are used? Dec 23 20:49:03 looks like it Dec 23 20:49:09 what was gcc commandline? Dec 23 20:49:50 roxfan: I re-read my statement above and I think it's wrong; the CS page talks about emitting code which uses VFP instructions but can interoperate with code which doesn't Dec 23 20:50:48 which means it's not a compatibility thing, it's for compiling certain sensitive code for extra speed when you know it will be used on a device with a VFP Dec 23 20:51:08 hi all Dec 23 20:51:09 but some of the libs the code will use were not built with VFP instructions Dec 23 20:51:31 Been a while. Dec 23 20:51:32 so softloat then just means that fp parameters are passed in GP registers Dec 23 20:51:36 I havent been in here in forever Dec 23 20:51:48 question, does the open vpn work currently? and if so where can i find some instructions? Dec 23 20:53:00 what are you doing with the vfp ? Dec 23 20:53:47 anybody know? Dec 23 20:53:54 i know nothing about open vpn Dec 23 20:54:13 or any vpn i guess Dec 23 20:55:04 unfortunately i don't do anything vpn related on my pre .. sorry :( Dec 23 20:55:43 roxfan: I'm looking at the Preware build and there are no tuning options passed to the cross-compiler. and the options are identical for the armv6 and armv7 versions of the packages. and the CS xcompiler specs do no tuning AFAICT Dec 23 20:56:07 oh, you want more speed Dec 23 20:56:10 heck v4t might just be the default output Dec 23 20:57:01 disassembly will answer this. well that along with an understanding of the intruction sets :-\ Dec 23 20:57:38 jacques, the overall goal being optimized compile flags for the pre and/or pixi targets ? Dec 23 20:58:21 bpadalino|work: yes, optimal for each device Dec 23 20:58:45 neat Dec 23 20:58:48 bpadalino|work: but also needs to interoperate with the shipped libs :-) which are showing v4t on the Pre Dec 23 20:59:07 as geist mentions, does that change the abi ? Dec 23 20:59:25 roxfan: -mfloat-abi=softfp means passing of args in GP regs, soft-float is a superset of that Dec 23 20:59:56 bpadalino|work: at this point I do not know. Dec 23 21:00:06 http://wiki.debian.org/ArmEabiPort - did you read that page or are you ware of everything it says ? Dec 23 21:00:51 bpadalino|work: I've read that page many times in the last few years, not recently though. I will re-read it Dec 23 21:02:03 do the elfs provided use the eabi or traditional gcc abi ? Dec 23 21:02:05 bpadalino|work: thanks for pointing it out again, I am definitely seeing some relevant things Dec 23 21:02:27 bpadalino|work: my interpretation of readelf is EABI Dec 23 21:02:43 oh, very nice Dec 23 21:03:24 http://pastebin.com/m1543de6b Dec 23 21:03:41 Flags: 0x5000002, has entry point, Version5 EABI Dec 23 21:05:30 interesting .. so does this mean it is using the v4t instruction set for the processor, or just that it's lowest common denominator is v4t compatibility for the library ? Dec 23 21:05:59 bpadalino|work: good question Dec 23 21:07:02 i can imagine it would be bad if it's using the v4t instruction set .. Dec 23 21:07:36 wow, check this out: http://pastebin.com/m5ff62c05 Dec 23 21:08:14 excellent - so busybox is built for armv7 Dec 23 21:08:27 that' good Dec 23 21:08:30 that's rather Dec 23 21:08:35 that's the readelf of busybox: Tag_CPU_name: "CORTEX-A8", Tag_CPU_arch: v7, Tag_VFP_arch: VFPv3 Dec 23 21:08:55 I want the compiler flags which generated *that* binary :-D Dec 23 21:11:24 you're not able to make a binary which has that ? Dec 23 21:11:34 when your machine type is armv7 it doesn't do it, huh ? Dec 23 21:12:18 i am full of questions :( Dec 23 21:14:47 bpadalino|work: I haven't tried yet :-) Dec 23 21:14:50 :) Dec 23 21:15:00 you should feel empowered and go for it Dec 23 21:15:48 oh don't worry. I will. Dec 23 21:16:18 *phew* i was a little worried for a little bit Dec 23 21:16:23 lol Dec 23 21:24:48 any of you use flickr? Dec 23 21:33:43 bpadalino|work: adding "-mcpu=cortex-a8" got me "Tag_CPU_name: "CORTEX-A8"" and "Tag_CPU_arch: v7" but not (yet) "Tag_VFP_arch: VFPv3" Dec 23 21:41:08 though I do get "Tag_ABI_HardFP_use: SP and DP" Dec 23 21:41:26 I'm assuming that's single and double precision Dec 23 21:42:30 sounds like a good assumption Dec 23 21:43:05 what about -mfloat .. what are the valid options ? Dec 23 21:44:20 oh, i see .. so that probably sets the -mhard-float Dec 23 21:44:22 I gave it "-mcpu=cortex-a8 -mfpu=vfp3 -mfloat-abi=softfp" Dec 23 21:44:24 since you get hardfp Dec 23 21:44:42 uses hardware floating point unit, but software floating point ABI Dec 23 21:44:58 ah Dec 23 21:45:00 -mnative should work, no? Dec 23 21:45:07 so it can interoperate wich code which uses the same ABI and software floating point Dec 23 21:45:47 jauderho_: I'm cross-compiling... Dec 23 21:45:55 ah Dec 23 21:47:25 I wonder if anyone is interested in building a 1password app for the pre... Dec 23 21:53:24 hmm, maybe it should be "-mfpu=neon" Dec 23 21:54:01 * jacques feels the urge to do some benchmarking. Dec 23 21:56:37 /usr/lib/jvm/java-1.5-palm/bin/java is also built with Tag_CPU_name: "CORTEX-A8" Dec 23 21:59:32 Dec 23 22:00:08 sup geist Dec 23 22:00:27 lets see Dec 23 22:00:48 we build with -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=softfp Dec 23 22:01:03 sounds like jacques has his answer Dec 23 22:01:16 and Dec 23 22:01:23 -mcpu=arm1136jf-s -mfpu=vfp -mfloat-abi=softfp Dec 23 22:01:37 geist: thank you! Dec 23 22:02:08 the latter is a complete subset of the former, so it would run fine on a cortex Dec 23 22:02:54 geist, any idea what type of impact compiling libc and other supporting libs for a8 would do performance wise versus their current armv4t ? Dec 23 22:09:22 why build for arm11 though? Dec 23 22:09:46 trying to support pixi as well? but is has no neon right? Dec 23 22:10:21 right, so you can either support the whole set with one build, or do 2 specific builds Dec 23 22:11:13 we are already doing two (three including x86) builds Dec 23 22:11:28 but the two arm ones are identical (currently) Dec 23 22:11:37 * jacques does "arm-none-linux-gnueabi-readelf -r java | grep aeabi" Dec 23 22:13:56 so the java binary calls many (31) functions in libm Dec 23 22:14:55 http://pastebin.com/m60a168ac for the curious Dec 23 22:32:09 oh, libm is armv4t ? Dec 23 22:34:16 bpadalino|work: yes, libm looks identical to libc Dec 23 22:36:11 ... -mcpu=brain -mfpu=left_hemispere -mtune=common_sense Dec 23 22:36:47 * DarkSpecter needs sleep it seems Dec 23 22:39:10 jacques, interesting - can you do the readelf on LunaSysMgr to see how that is compiled and how many calls to eabi stuff it has ? Dec 23 22:42:22 bpadalino|work: http://pastebin.com/m43eacbc1 this is the first time I have seen "Tag_NEON_arch: NEONv1" Dec 23 22:42:51 maybe those tags only show up if the binary actually uses those instructions Dec 23 22:43:26 quite possibly Dec 23 22:43:38 so if a binary was built with -mfpu=neon but no neon instrs were generated, the tag would not show up Dec 23 22:44:21 sounds reasonable Dec 23 22:45:14 my grep shows which functions are called, but (naturally) not how many times. Dec 23 22:48:03 right Dec 23 22:48:06 time for me to head home Dec 23 22:48:08 bbl Dec 24 00:01:45 * jacques heads home. Dec 24 00:57:57 morning **** ENDING LOGGING AT Thu Dec 24 02:59:57 2009