=== bjf is now known as bjf_afk [09:47] hi [09:48] is there a way to get a armv7 version of Ubuntu 9.04? [09:51] no [09:51] well, there is but involves that you rebuild everything yourself [09:51] v6 then? [09:51] right, karmic will be v6+vfp [09:52] jaunty is v5 with some libs being vfp [09:52] ok. is there a repo for karmic? [09:52] janrinze: Do you know the "How does this differ from the work of mojo.handhelds.org " section of https://wiki.ubuntu.com/ARM FAQ ? Maybe mojo.handhelds.org can help you. Not sure, though [09:52] ports.ubuntu.com [09:53] i have used mojo before.. on XScale.. but that only had armv5. maybe the latest ones have better support though. [09:53] mojo has stopped with interpid [09:53] and they use nonstandard architecture names for their packages [09:53] * dirk2 learned again something ;) [09:53] which makes it close to impossible to crossgrade from mojo to ubuntu [09:53] yep.. i noticed the activity at mojo had stopped.. [09:54] i though because Ubuntu now started to support arm they move to the main ubuntu support activities. [09:55] https://blueprints.launchpad.net/ubuntu/+spec/mobile-karmic-arm-cloud-builds might be instresting for you for a ful v7 rebuild [09:55] oops.. 'thought' [09:55] *full [09:55] but its still in the works [09:56] ogra: ok.. a bit too much for me a.t.m. [09:57] well, karmic's userspace should work for you [09:57] so as far as i can see only OE/Angstrom does full armv7/armv6 builds [09:57] see the rootfs from scratch wikipage from the topic if you want a rootfs [09:58] ogra: that will only prebuilt binaries, right? [09:58] right, with jaunty we tried to support at least some of the debian architectures which forced us into v5 ... there is more v7 HW now so karmic does v6+ [09:59] that will only assemble a rootfs tgz from the archive [09:59] ogra: using debs with prebuilt binaries for armv6? [10:00] yes [10:02] ogra: the script on the webpage will install jaunty, how to change that to get karmic? [10:03] just change 'echo "deb ${MIRROR} jaunty ${COMPONENTS}" >/etc/apt/sources.list' ? [10:03] oh, sorry, right, i'm about to add a --dist option :) just change the two occurences of jaunty in it to karmic for now [10:03] there is another line with jaunty [10:03] ok. [10:03] sed will be my friend ;-) [10:05] ogra: in karmic the arch is still armel? [10:05] yes, that wont change [10:05] ok.. will that prevent karmic from running on XScale? [10:06] not sure, i dont have any XScale HW [10:07] hmm.. will a dist-upgrade work with jaunty? [10:08] sure [10:10] ok.. just added karmic to apt-sources [10:11] should i keep jaunty in the sources.list too? [10:13] well, just make sure your jaunty is up to date with the latest upgrades [10:13] ok. [10:13] before you dist-upgrade to karmic [10:13] then you can just comment out jaunty [10:14] ok. [10:17] ogra: jaunty defaults to getting the imx51 linux headers. is there a OMAP3 package too? [10:18] no [10:18] ok. [10:18] there are third party packages for beagleboards [10:19] http://elinux.org/BeagleBoardUbuntu [10:19] not sure how much they help on XScale though [10:20] the XScale is not my concern a.t.m. was just curious. [10:20] i run on ubuntu jaunty the BB [10:21] ah [10:21] i do have a XScale platform which i would like to upgrade one time ;-) [10:22] ok.. will do dist-upgrade now. [10:22] * janrinze is making more coffee and starts thinking about what to do in the next 8 hours or so. [13:06] * janrinze is still looking at the dist-upgrade progressing.. === Meizirkki_ is now known as Meizirkki === bjf_afk is now known as bjf === cbrake_away is now known as cbrake [16:15] the only way to get gcc to compile inline NEON instructions is to use -mfpu=neon -mfloat-abi=softfp. Will that still be compatible with libraries such as libc? === ScriptRipper_ is now known as ScriptRipper === cbrake is now known as cbrake_away === rjune__ is now known as rjune