/srv/irclogs.ubuntu.com/2009/06/12/#ubuntu-arm.txt

=== ApOgEE is now known as Ap0g33
=== Ap0g33 is now known as ApOgEE-
* ethanbot2 waves to ethana206:19
persiaSomehow I doubt that worked the way it was intended.06:19
=== ScriptRipper_ is now known as ScriptRipper
=== bjf is now known as bjf_afk
=== cbrake_away is now known as cbrake
=== bjf_afk is now known as bjf
=== Omegamoon is now known as Omegamoon|cookin
=== Omegamoon|cookin is now known as Omegamoon|dinner
loologra: For the record, we wont expect NEON in karmic+, only ARMv6 and VFP v3; our toolchain doesn't output NEON by default anyway17:38
=== Omegamoon|dinner is now known as Omegamoon
Martynre19:57
Martynlool : *nod*20:58
Martynlool : I'm looking to see what it would take to compile karmic w/ full NEON and v7 optimizations20:59
Martynakin to building the i686 port20:59
loolMartyn: why NEON?21:41
loolMartyn: karmic will likely move to v6 + vfp v321:42
loolThere are some advantages to v7 over v6, but not really in a way which we'd use21:43
loolMartyn: NEON isn't picked up by the fsf toolchain yet AFAIK, it might be by the codesourcery one; perhaps you want to rebuild some specific NEON using apps with NEON enabled?  But I don't see much value in using NEON righ tnow21:45
MartynCodeSourcery supports it21:55
Martynlool : Not for ubuntu "we" but for smooth-stone "we" I need as much optimized performance as I can get out of our new SoC21:55
MartynAnd it's a quad-core v7 w/ a huge L221:56
MartynSimilar to what you're going to see out of pegatron and company once the A9MP's start rolling out21:56
loolMartyn: ok, but what's going to use your NEON instructions?22:07
loolDo you plan using a custom toolchain which generates more NEON code?22:08
=== cbrake is now known as cbrake_away
Martynlool : Yep.23:14
Martynlool : Or more specifically, the customers that will be making systems from this architecture will need it23:15

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!