[03:18] anyone know what "for thumb inter-working we require an architecture which supports blx" means when i try building node.js in an ARM environment? [03:20] blx is probably an instruction [03:20] http://infocenter.arm.com/help/topic/com.arm.doc.kui0100a/armasm_cihfddaf.htm [03:21] IIUC it's how you tell the CPU to swap from arm instructions to thumb instructions [03:22] Sounds like you're on an M profile ARMv7 core and you simply can't have that. [03:22] know how to add it? [03:22] Get a different CPU [03:22] lol [03:23] ok, know a way around it? [03:23] Or it may be you're compiling for a lowest-common-denominator that doesn't include that, although your actual target hardware does [03:23] It may also be that BLX is only needed because that's what node.js source knows how to use, and you can either HTFS or node.js, or compile it to thumb-less ARM [03:24] um, huh [03:27] all i know is i have a Texas Instruments OMAP3530 system-on-chip with ARM Cortex-A8 [03:28] FWIW on oneiric, apt-get source nodejs; ./configure --without-ssl worked for me [03:28] that would seem odd [03:28] thumb is part of armv7 [03:29] and there is no other way to switch between thumb and arm other than BLX [03:31] trying --without-ssl [03:31] same error [03:34] lilstevie: I suspect he's doing -march armv4 or something, implicitly. [03:35] i tried make CFLAGS=-march=armv5t earlier, but no go [03:36] lilstevie: ARMv7-M apparently lacks BLX [03:36] Ref. previous link [03:38] should it be "make CFLAGS=-march=armv5t" or "make CFLAGS='-march=armv5t'"? [03:42] -march is going to fail [03:42] :p [03:42] well not going to fail [03:42] but is fail [03:43] if you are targetting ubuntu-arm you should be targetting armv7 [03:43] so -march=armv7 [03:43] thought armv7 didn't support blx? [03:43] all armv7 except armv7-m do [03:43] ah [03:44] ok, do i add CFLAGS=-march=armv7 to make or configure? [03:45] nm, obvioulsy not configure since that didn't work [03:47] CFLAGS may not be being passed the way you expect [03:47] hrmm, "make CFLAGS=-march=armv7" returns "target CPU does not support ARM mode" [03:51] 0.o [03:53] ok, looking through macro-assembler-arm.cc, i found the error message with "If you know what CPU you are compiling for you can use -march=armv7 or similar", but how am i suppose to use it [03:53] You probably need to pass it to waf in some manner like ./waf --extra-ccflags [03:53] Note also nodejs v8 code appears to be C++ not C, so CXXFLAGS not CFLAGS [03:54] ah [03:54] Or both, or whatever [03:54] Usually when dealing with this kind of thing you end up having to debug / rewrite upstream's idiotic makefile / configure.ac / wscript / whatever [03:54] lol [04:00] well, "make CXXFLAGS=-march=armv7" gave me the no arm support error, bot "make CXXFLAGS=-march=armv5t" is still going [04:19] yay, still going [04:34] dammit, now getting: pure virtual method called. terminate called withough an active exception [04:34] Why are you compiling nodejs anyway [04:35] for koush [04:35] oops [04:35] for koush's tether app, so it can run on arm systems (specifically, openpandora) [04:35] NotJimCarrey: I mean, why don't you just apt-get install it [04:36] tried using it, but got errors [04:36] Did you investigate them? [04:36] think koush modified it for tap/tun support [04:38] how can I get audio over hdmi (ubuntu 11.10 on pandaboard)? [04:38] if i run the script with the node.js from the angstrom repo, i get "unable to open tun/tap device" [04:38] That's more likely to be either a permissions issue or you don't have a tun or tap device yet [04:39] well, running it sudo because it uses adb [04:39] blergh [04:39] Well, whatever. === Jack87|Away is now known as Jack87 === Quintasan_ is now known as Quintasan [10:30] infinity, Bug 890261 [10:30] Launchpad bug 890261 in ubiquity "can not execute oem-config in a chrooted environment" [Medium,New] https://launchpad.net/bugs/890261 [10:30] ogra_: Danke. [11:24] ogra_, http://kernel.ubuntu.com/git?p=jani/ubuntu-ac100.git;a=shortlog;h=refs/heads/packaging-chromeos-ac100-3.0 [11:25] UBUNTU SAUCE commit, seventh from top [11:25] that should be the quietening patch [11:25] but it doesnot seem to have effect on mine either [11:29] weird weird [11:29] probably the bits we actually see are not using the proper kernel interface [11:31] (the logging functions i mean) [11:32] it all seems to come from non std drivers [11:32] i.e. the < ... > i see seem to come from tegrapart [11:39] janimo, http://git.chromium.org/gitweb/?p=chromiumos/third_party/kernel.git;a=commitdiff;h=7abaad6c574bbdc0dd66820eaf006857dac6c4e7 [11:39] sight [11:40] (commit from tonight) [11:40] *sigh even [11:49] ogra_, yeah, I hopemarvin24 picks those up too and takes out the unneeded options from defconfig. I'll NFS and the other important ones so we keep the config delta minimal [11:50] janimo, well, i'm not really thrilled about losing power management completely [11:51] ogra_, well if it seems that is does not affect ac100 we can leave it on [11:51] right [11:51] the latest kernel (3.0.8 from stable) is stable so far [11:51] seems a bit broad to just disable it for all tegra [12:29] hello there [12:30] i have a little question. i see, there are kernel-flavours for different arm-based devices. but they use the same repository, i guess. am i right? === mythos_ is now known as mythos [12:53] sorry, but where do i find an arm-rootfs for a qemu-chroot environment? [12:55] or is debootstrap the way to go? [13:02] mythos: kernel can be easily cross-compiled. For other components, there are various solutions but generally native ARM build is the safest (tough often slowest) [13:02] *though [13:03] thank you, OlivierN1 [13:03] but i'm not so far that i can go on a real hardware [13:04] janimo: if the kernel turns out to be stable, you may activate the frontswap option in the next cycle [13:04] so i would be happy, if i got a running chroot environment with qemu-static-arm, so i can start to mess around [13:04] so people don't need to mess around with zram/swap stuff anymore [13:05] marvin24, 3.0.13 you mean? [13:06] janimo: no, it is there in 3.0.8 already [13:06] just not on by default [13:06] mythos: other people here can help on the qemu front. Personally I use native build. [13:06] ok, 3.0.8 is stable using your stable tree [13:06] been running since yesterday without lockup [13:06] nice! [13:07] any news on 3.0.13? Is that the latest version that chromeos works on? [13:07] still haven't found the bug in 3.0.13 <- not so nice [13:07] OlivierN1, no problem. i found a good tutorial for debian using multiarch. i'm going to try and hope for the best =) [13:17] hmm.... where do i find the arm-debs for eg maverick? ^^" [13:23] ah, found it: ports.ubuntu.com [14:21] lilstevie, do you know if anyone is working on a 3.x based transformer kernel? [14:22] i'd like to know that too :) [14:46] janimo: at present no [14:47] janimo: working towards it though [14:47] lilstevie, ok, thanks :) [14:47] anything in common with the ac100/chromeos tree? [14:47] It'd be nice if we could share the same package in ubuntu for as many tegra based hw as possible [14:47] janimo: more in common with ventana [14:48] janimo: that is possible [14:48] janimo: ac100 bl reports harmony while tf101 reports ventana, so no messy hacks would be required either [15:11] OlivierN1, for a native built-environment, do you use a nfs-rootfs for the arm-device? [15:12] mythos: brb [16:20] mythos: you may use NFS, SD card, eMMC, USB stick, etc. But the fastest by far (at least on Panda board) is a USB hard drive, especially for native build. [16:20] OlivierN1, thanks for the advice =) [16:29] i was able to get a chroot environment, so i'm quite happy =D === zyga is now known as zyga-afk [16:47] how is one supposed to create .config for http://dev.omapzoom.org/?p=integration/kernel-ubuntu.git;a=commit;h=f0fb3e7b7b2f8c791802e136293e8aadaac14119 ? [16:47] not using debian or ubuntu [16:48] then why do you ask in an ubuntu channel ? [16:49] because it is ubuntu kernel and I just want to get the configs out of it to see them as whole [16:49] so wondering what command does the kernel config for omap4 there [16:49] they are in the debian dir split in multiple chunks usually [16:49] and merged at build time [16:50] so omap4_defconfig doesn't do it as I assumed. [16:51] omap4_defconfig will work if yuo just use make (its an upstream config after all) but not get you the same as an ubuntu package [16:52] well, I want to have the same as in ubuntu thus asking [16:52] if you want the ubuntu config you will have to use dpkg-builpackage or call debian/rules which triggers the various scripts before rolling the package [16:52] hmmp [16:53] ok, where are the .deb files for that kernel there is config in those :) [16:53] but you are probably better off to download the binary package from the archive, unpack it and pull /boot/config-$kernelversion out of the package [16:53] either on launchpad or in the pool on prots.ubuntu.com [16:53] *ports. [16:55] Sage: this page may help: http://omappedia.com/wiki/Ubuntu_kernel_for_OMAP4 (section 4.1) [16:56] OlivierN1: well on fedora it is not so straight forwardhttp://pastie.org/3173223 [16:57] err http://pastie.org/3173223 [16:58] ti-ubuntu-3.0-1281.7 <- this is what I'm looking for atm. but can find only these https://launchpad.net/ubuntu/+source/linux-ti-omap4 [16:58] Why live in the past? [16:59] if you mean that 3.2 thing those are not in http://dev.omapzoom.org/?p=integration/kernel-ubuntu.git;a=summary [16:59] http://loki.0c3.net/~adconrad/config-3.2.0-1403-omap4 <-- The current config [17:00] ok, thx. And any knowledge if that works on blaze as well (screen, touch etc)? [17:01] Maybe? Not sure, don't have a blaze. [17:01] Sage: at least ti-ubuntu-3.0-1281.7 works on Blaze (LCD and touch screen are OK, sound record/playback is upcoming) [17:02] OlivierN1: ok, where to get the tarball and .deb for that? [17:03] * Sage really don't know where to find those in launchpad [17:03] Sage: TI public PPA is here: https://launchpad.net/~tiomap-dev/+archive/release [17:03] (but it does not contain 3.x kernel for now) [17:04] https://launchpad.net/ubuntu/+source/linux-ti-omap4 has all debs that were ever built in ubuntu [17:04] OlivierN1: exactly :) [17:05] OlivierN1: you don't happen to have .deb for that ti-ubuntu-3.0-1281.7 or even just the config from /boot/? [17:06] Sage: basically TI PPAs is always a little behind TI trees. For now we do not consider ti-ubuntu-3.0-1281.7 as stable enough to upgrade PPA [17:07] OlivierN1: yes, well. You said ti-ubuntu-3.0-1281.7 works on blaze so you have compiled it and have config somewhere? [17:08] sure [17:08] I'm really looking just kernel that has been tested on blaze and works, don't care so much if it is stable or not, just want to boot the damn thing and see and then think stability :) [17:12] OlivierN1: want to share the config? :) === zyga-afk is now known as zyga [17:40] Sage: config-3.0.0-1281: http://pastebin.com/2HKn0wvS [18:35] OlivierN1: thx === Jack87 is now known as Jack87|Away === zyga is now known as zyga-afk [20:12] Where can I find the source archives/.debs for Ubuntu ARMEL debs? [20:16] ports.ubuntu.com?