=== ScriptRipper_ is now known as ScriptRipper
=== NCommander is now known as ApportRetracerPo
=== ApportRetracerPo is now known as NCommander
[09:27] <pan1nx> Can anyone enlight me about which ARM architecture is our ubuntu-arm compilation/build packages done for?
[09:35] <persia> amitk, Are you sure about +NEON as a base requirement, rather than simply some optimisations (like vfp for jaunty)?
[09:36] <amitk> persia: it is going to be an optimisation for ffmpeg and related libraries, I guess.
[09:36] <persia> amitk, That makes more sense to me.  I didn't think a lot of stuff had NEON yet.
[09:45] <NCommander> Does anyone have hardware that can use +NEON?
[09:45] <amitk> beagle?
[09:48] <pan1nx> https://wiki.ubuntu.com/Specs/ARMLibraryOptimization
[09:48] <pan1nx> shouldn't we mention the NEON there then?
[09:49] <pan1nx> so far it lists: Ubuntu ARM includes support for ARMv5t+ instruction sets, with optimisations available for ARMv6, ARMv7, and VFP routines where appropriate.
[09:49] <persia> pan1nx, No.  That was a jaunty spec.
[09:49] <persia> (and then it got stuck, and now it's kinda in limbo)
[09:50] <persia> The issue is, in part, that it's *hard* to get that right: the differences between generations seem to be larger for ARM.
[09:51] <pan1nx> I tried to find some blueprints on this topic and failed
[09:51] <persia> The blueprints system tends to be a bit hard to navigate, unfortunately.
[09:51] <pan1nx> LOL
[09:51] <pan1nx> I guess this discussion should be moved to #launchpad
[09:52] <pan1nx> but do you have one from the last UDS on this topic?
[09:52] <persia> Well, they're well aware of it.
[09:52] <persia> I didn't follow ARM that closely in Barcelona.  You might see if the schedule is still up at summit.ubuntu.com, and if so, use that to guess which might be the right spec.
[10:07] <pan1nx> persia, looked there but still couldn't find a clear spec about the build
[10:07] <persia> pan1nx, There may not be such a clear spec.  There's a few factors involved.
[10:08] <pan1nx> the closest blueprint i could find was https://blueprints.edge.launchpad.net/ubuntu/+spec/mobile-karmic-arm-cloud-builds
[10:08] <persia> Firstly, that the toolchain packages would have most of the details exposed inherently, and changes to the toolchain don't usually get specifications (because they happen so early in the cycle).
[10:09] <persia> Secondly, that most sorts of runtime-code-selection optimisations need to be done on a per-package basis, and so often will end up happening independently (and often in Debian, rather than in Ubuntu alone).
[10:10] <persia> Thirdly, Specs are being drafted currently, for inclusion in karmic, and it may be that if there is a spec, it's not done yet.
[10:12] <pan1nx> ok
[10:12] <pan1nx> good to know...
[10:12] <pan1nx> I will follow this closely
[10:12] <pan1nx> :D as usual :D
[10:29] <persia> pan1nx, Really, download the source of the toolchain, and check that.  It's your best guide.
=== ApOgEE-- is now known as ApOgEE
=== ApOgEE is now known as ApOgEE-
[10:55] <pan1nx> persia, where do I download that toolchain?
[10:56] <pan1nx> so far I found the best doc to be this one:
[10:56] <pan1nx> https://wiki.ubuntu.com/MobileAndEmbedded/ARM-EL-port
[10:56] <persia> pan1nx, apt-get source
[10:57] <persia> pan1nx, It's the Ubuntu toolchain, so, for instance, if you want to look at gcc, run `apt-get source gcc`
[10:57] <persia> Well, actually, it's a bit more complicated.
[10:57] <persia> For gcc, you'll want the "gcc-4.4" package.
[10:57] <persia> And you'll want to make sure you have karmic deb src lines in your /etc/apt/sources.list
[11:06] <pan1nx> ok
[11:06] <pan1nx> thanks persia
=== bradf is now known as bjf