**** BEGIN LOGGING AT Tue Jan 04 02:59:58 2011 Jan 04 05:49:57 hi, does DEB_BUILD_ARCH = armel for the native builders? Jan 04 08:05:30 morning Jan 04 10:02:57 micahg: Yes; but it's usually a bad idea to check this Jan 04 11:12:58 is there a link for geexbox image for arm platform? Jan 04 11:57:09 looking at the u-boot packaging i now understand why lool didnt want to do the package split Jan 04 11:57:11 sigh Jan 04 12:00:03 no compat file, no build deps, debian/rules looks horrid ... Jan 04 12:00:56 why cant people just use a proper build system instead of making up debian/rules by hand Jan 04 12:08:15 ogra: I actually committed an u-boot-tools package in the Debian git repo this morning Jan 04 12:08:29 oh, cool Jan 04 12:08:37 this rules file is just painful Jan 04 12:12:38 lool, any ETA when that will be in debian (i need it asap so i'm pondering to add it as patch for ubuntu) Jan 04 13:43:44 GrueMaster, can you remember what failed in your testing of omap from natty master Jan 04 13:57:15 lool: what's the proper way to check if something is an arm build vs not arm? Jan 04 14:00:53 micahg: 'arm build' as 'build on arm' or as 'build for arm'? Jan 04 14:01:07 hrw: build on arm Jan 04 14:01:54 'uname -m' may be but debian packagers will want to kill you for it probably Jan 04 14:02:38 right, I was looking at DEB_BUILD_ARCH, but apparently, that's not the best way? Jan 04 14:07:28 micahg: why you need check? Jan 04 14:07:57 hrw: --enable-thumb2 fails the firefox build on non-armel builds Jan 04 14:08:12 ah Jan 04 14:08:39 rules2: ifneq (,$(findstring $(DEB_TARGET_ARCH),armel hppa ia64 sparc)) Jan 04 14:09:09 micahg: so use DEB_TARGET_ARCH check Jan 04 14:09:30 DEB_BUILD_ARCH = amd64 DEB_TARGET_ARCH = armel is 100% proper btw Jan 04 14:10:26 * micahg is getting DEB_TARGET_ARCH not supported on maverick Jan 04 14:11:05 let me check how gcc do that Jan 04 14:11:19 micahg: It's uncommon to check the architecture of the buildd Jan 04 14:11:26 micahg: Usually you test what you're building /for/ Jan 04 14:11:49 DEB_HOST_ARCH is the Debian architecture of the machine the package will run on Jan 04 14:11:55 rules.defs: TARGET_VARS := $(shell dpkg-architecture -f -a$(DEB_TARGET_ARCH) 2>/dev/null) Jan 04 14:11:58 rules.defs:DEB_TARGET_ARCH ?= $(call vafilt,$(TARGET_VARS),DEB_HOST_ARCH) Jan 04 14:12:06 ops Jan 04 14:12:27 micahg: It would also be best to test the GNU CPU or something similar rather than the Debian architecture name; for instance the Debian armhf port is very similar to armel, but wont be covered by your test Jan 04 14:12:46 sorry - it is done by different way in gcc Jan 04 14:13:32 micahg: Perhaps you could explain your specific problem? I'm not sure I can comment on which var you should use, as you only asked about native builds but I might have missed when you explained what you're building Jan 04 14:13:54 hrw: The packages like gcc which have the concept of a target architecture are fairly rare Jan 04 14:13:56 lool: well, I need to add a build option to arm only for firefox Jan 04 14:14:38 micahg: Right, that's a good example of a case where you'd test DEB_HOST_ARCH, and *not* DEB_BUILD_ARCH Jan 04 14:14:59 micahg: The main difference is when cross-compiling; when cross-compiling, DEB_BUILD_ARCH might be amd64 while DEB_HOST_ARCH is still armel Jan 04 14:15:37 ah, so HOST_ARCH is the right one, ok, that's good to know for the future Jan 04 14:21:41 thanks lool Jan 04 14:30:43 micahg, I think it's a simpler change to not check at all and let ff configure drop the option if it is not suitable for the current arch Jan 04 14:49:06 janimo: I tried with it on for amd64 and the build failed Jan 04 14:50:32 micahg, did it pass march arm to gcc? Jan 04 14:50:37 micahg: Just saw your firefox changes; would you mind if we discussed these for a sec? Jan 04 14:51:45 lool: actually, I'm about to catch a bug, can we chat in a few hours? Jan 04 14:51:48 *bus Jan 04 14:52:00 micahg: Sure; I will send you an email Jan 04 14:52:09 janimo: I have to check the build log Jan 04 14:52:13 lool, you mean the change in the latest upload or something else? Jan 04 14:52:16 lool: thanks Jan 04 14:52:27 janimo: Yes, the THUMB2 one Jan 04 14:52:58 lool, I suggested that one to micahg to fix the FTBFS. Tested on a panda before that. Jan 04 14:53:18 the details may need to be done differently but I think that flag needs to be passed Jan 04 14:53:40 janimo: Yup; do you want to be Cc:ed? Jan 04 14:53:50 lool, sure Jan 04 14:53:55 Hmm apt-cache showsrc janimo wont give me your email address Jan 04 14:54:08 jani at ubuntu.com Jan 04 14:54:35 * lool <- tired Jan 04 14:54:36 janimo: thanks Jan 04 15:03:05 lool, is there any ETA for the debian u-boot upload or do we need to add the package split as ubuntu patch to get it in this week ? Jan 04 15:03:23 (i think you disconnected above when i asked before) Jan 04 15:12:00 ogra: I've contacted Clint this morning to ask him to review these changes; they will hit Debian NEW in any case, so that will probably take some time; however, it wouldn't be too bad to copy the NEW package in Ubuntu Jan 04 15:12:59 lool, do you get any notification you could forward if that happens ? Jan 04 15:16:29 (i mean if it hits NEW, I'll care for teh sync requests etc) Jan 04 15:57:52 ogra: Unfortunately, one can't sync from NEW; if I'm doing the upload, I'll tell you once it's done Jan 04 15:58:02 thanks Jan 04 16:02:22 Morning (barely). Jan 04 16:03:49 ogra: rsalveti: apw: The issues I saw with the previous omap kernel prior to the break was that it literally didn't boot. I couldn't get any feedback past u-boot loading the kernel. Not even output from earlyprintk. Jan 04 16:05:54 I'm installing the new kernel now. Jan 04 16:13:53 GrueMaster: yeah, I'll also try it here, and then try to fix it if it doesn't work Jan 04 16:14:37 Hmm. Currently, it appears to be stuck on installing the linux-headers package. Jan 04 16:16:39 installing things in general is slow i think if you have the older dpkg Jan 04 16:17:03 doesn't seems to boot, will now debug to see why Jan 04 16:17:18 Looks like I was getting a segfault loop of some sort. Rebooting. Jan 04 16:17:59 rsalveti, thanks Jan 04 16:18:09 rsalveti, are u gettting any console output at all ? Jan 04 16:19:01 apw: nops Jan 04 16:19:22 rsalveti, that sound fun to debug Jan 04 16:20:00 apw: :-) Jan 04 16:20:12 sounds like an issue with the console driver Jan 04 16:20:30 do you have a monitor attached or do you try purely with serial ? Jan 04 16:20:36 hm, ok, got something with earlyprintk Jan 04 16:29:42 folks, the weather report for Dallas is cold next week Daytime 8.3C and nighttime -2.77 Colder then usual around here Jan 04 16:30:04 For some of you that is warmer then you are at but for us it's cold Jan 04 16:32:03 ouch, very cold for me hehe Jan 04 16:32:13 it's around 30C everyday around here Jan 04 16:32:17 good to know Jan 04 16:32:49 I vote we relocate to Sao Paulo. Jan 04 16:33:03 hehe :-) Jan 04 16:33:10 at least i wont catch a cold Jan 04 16:33:33 we have constantly around -3°C here (day and night) Jan 04 16:38:19 ogra: apw: GrueMaster: ok, did boot, you now need to use ttyO2 instead of ttyS2, like panda Jan 04 16:38:23 because of the newer console driver Jan 04 16:38:31 awesome Jan 04 16:38:32 but I'm now getting tons of mmc i/o errors Jan 04 16:38:41 probably a different issue, more debugging Jan 04 16:38:45 I had tried that when I tried the older kernel. Jan 04 16:38:48 rsalveti, sounds good! Jan 04 16:39:06 apw: will test it more around here, and compare the config with linaro's one Jan 04 16:39:07 GrueMaster, the kernel he is testing is two -rc's newer than the one you tested before xmas Jan 04 16:39:49 I know. Jan 04 16:40:02 Just saying that I had tried both serial port settings. Jan 04 16:42:08 GrueMaster, good to know, as that means things have improved by osmosis Jan 04 16:45:15 apw: ogra: GrueMaster: full maverick desktop up and running Jan 04 16:45:28 rebooted and now I didn't get any i/o error Jan 04 16:45:34 * rsalveti trying again Jan 04 16:45:37 wohoo Jan 04 16:46:00 apw, so can we get omap3 back ? Jan 04 16:46:02 no calltrace during the bootlog Jan 04 16:46:18 I believe this could be a good start Jan 04 16:46:28 then we can just improve over the time, with more testing and etc Jan 04 16:46:39 yeah Jan 04 16:46:43 at least I believe it's good enough to get images Jan 04 16:48:32 rsalveti, did you say that you have booted this one successfully ? Jan 04 16:48:40 yes he did :) Jan 04 16:48:46 apw: yup, 2 times Jan 04 16:48:52 GrueMaster, does it boot for you too ? Jan 04 16:49:04 who cares about GrueMaster :P Jan 04 16:49:07 let me know try with a normal beagle Jan 04 16:49:12 tried with a beagle-xM Jan 04 16:49:15 *now Jan 04 16:49:16 I'm having other non-kernel related issues atm. Will try again shortly. Jan 04 16:49:28 he always manages to break even the super solid things ;) Jan 04 16:49:52 It's my job, that's what I do. Jan 04 16:50:09 I was hell with my toys. Jan 04 16:50:19 lol Jan 04 16:51:02 haha Jan 04 16:52:23 ogra, ok tehcnically i can get this renabled yes, so you are going to use this kernel not the linaro in your images, thats the decision Jan 04 16:52:37 and your team is going to sign up to keeping it tested and working Jan 04 16:52:49 yes Jan 04 16:52:54 and yes Jan 04 16:52:56 :-) Jan 04 16:54:11 bring it, big guy. Jan 04 16:55:38 rsalveti: Did your patch for the serial port error on XM ever get integrated into the maverick kernel? Jan 04 16:56:05 i think i saw some noise about it this week Jan 04 16:56:17 GrueMaster: it's commited already I believe Jan 04 16:56:26 let me check again Jan 04 16:58:11 yup, mail says "applied" Jan 04 16:58:43 ok, haven't seen it in proposed yet. Jan 04 16:58:51 not uploaded Jan 04 16:59:04 yeah -proposed is somewhat behind Fix Committed over this xmas perios Jan 04 16:59:06 not uploaded, it's commited at the master-next Jan 04 16:59:07 period Jan 04 17:00:00 ogra: apw: GrueMaster: ok, also working fine at my beagle c4 Jan 04 17:00:04 so it seems to be good enough Jan 04 17:00:05 yay Jan 04 17:00:43 ogra, so we are saying beagle is the target for the omap kernel Jan 04 17:00:52 apw, XM Jan 04 17:00:59 apw: yep, xM will be our main use case Jan 04 17:01:04 as it's now quite popular Jan 04 17:01:10 and faster than a normal beagle Jan 04 17:01:28 so the acceptance criteria for that omap kernel is 'works on Beagle XM' Jan 04 17:01:38 ++ Jan 04 17:03:41 yup Jan 04 17:07:35 MADISON, Wis. - Madison police are looking for a burglar who gave back a bottle of tequila after the homeowner hit him in the head. Jan 04 17:07:39 oops Jan 04 17:07:40 wrong window ;) Jan 04 17:31:14 apw: the config seems fine comparing with the older one from maverick and with linaro's one Jan 04 17:31:41 rsalveti, thanks for the confirmation Jan 04 20:55:37 My 8G Class 10 SD cards finally came in. Woohoo! Jan 04 20:56:33 luck bastard Jan 04 21:02:09 8g class= nice, new class? :D Jan 04 21:02:39 class 10 isnt that new Jan 04 21:03:05 rsalveti, do you need any? i can buy them at the discounter and bring you some to the rally Jan 04 21:03:46 ogra: would be good to have, I have none around Jan 04 21:03:57 ogra: how much it cost usually around there? Jan 04 21:04:31 i'll have to check, i'll just bring a few, if you dont want them (or they are to expensive) i'll take them back again Jan 04 21:04:53 ogra: cool, would like at least 2 :-) Jan 04 21:05:00 ok Jan 04 21:05:07 np, just to know, here the problem is that I can't find them easily Jan 04 21:05:12 or without spending too much money Jan 04 21:05:27 I bought 2 8G for just under $30. Last cycle, they were $45 each. Jan 04 21:05:38 nice, good price Jan 04 21:06:09 amazon.com Jan 05 00:16:10 hi everyone - can someone tell me the state of CPU power management (cpufreq/cpuidle) for the omap4 port of ubuntu, and suggest a place where power management discussions take place? Jan 05 00:26:00 elesueur: latest omap 4 kernel for natty should support pm already Jan 05 00:26:10 elesueur: for omap 4 try #pandaboard Jan 05 00:26:27 thx, will ask at #panda Jan 05 00:27:10 elesueur: our tree http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-natty.git;a=shortlog;h=refs/heads/ti-omap4 Jan 05 00:27:31 and at https://launchpad.net/ubuntu/+source/linux-ti-omap4 you can find the deb files Jan 05 00:28:40 * rsalveti brb Jan 05 00:46:21 out of interest, which cross compiler are you using to compile kernels? Jan 05 01:44:35 elesueur: the one available at ubuntu already Jan 05 01:44:39 from linaro Jan 05 01:44:45 rsalveti: ping Jan 05 01:45:04 if you're using maverick or natty at your desktop, just try searching for packages with arm in the name and you'll find Jan 05 01:45:05 TheUni: pong Jan 05 01:45:09 ah, good timing, you're here :) Jan 05 01:45:18 yup :-) Jan 05 01:45:48 rsalveti: are you still looking at xbmc as a possiblity for the stb distro? I ask because we're working on our roadmap for 11.0 Jan 05 01:45:52 TheUni: was going to ping you until the end of this week, how is xbmc going? Jan 05 01:46:04 TheUni: it all depends on the current state Jan 05 01:46:10 rsalveti: going great. finally completed our merge to git today Jan 05 01:46:19 that was the first big priority after stable Jan 05 01:46:20 we can for sure add to the archive, and then use it by default for 11 Jan 05 01:46:31 cool Jan 05 01:46:39 rsalveti: ok, tell you what... Jan 05 01:47:11 we have 1 big merge to go.. where all code is being rearranged to help with buildsystem and packaging woes Jan 05 01:47:31 how bout i ping you after it's merged and we can evaluate the state of things? Jan 05 01:47:33 TheUni: hm, ok, any important feature to add? or just buildsystem related changes? Jan 05 01:47:39 TheUni: sure! Jan 05 01:48:08 rsalveti: new features in the next version ofcourse, but we see this as a major cleanup version as well Jan 05 01:48:22 oh, ok, good Jan 05 01:48:28 we'd love some help from the ubuntu side of things with packaging and etc. Jan 05 01:48:44 (developing good habits, i mean) Jan 05 01:49:30 TheUni: sure, can help on that Jan 05 01:49:41 ok great. will ping you soon. should be going in as soon as we can get it rebased and tested a bit Jan 05 01:49:42 just ping me when you think you're in a good shape Jan 05 01:49:50 yep. thanks :) Jan 05 01:49:50 nice Jan 05 01:49:56 np :-) **** ENDING LOGGING AT Wed Jan 05 02:59:58 2011