We check Ubuntu, Opensuse and Fedora in our regular testing. So at least, the 3 distros should be added as support. Best Regards, Jiajun

Have spoken to Scott R, seems he's been working on the Poky reference manual so I will need to rebase once he's pushed his changes. Feel free to review but do not merge this set. Thanks, Paul --

If you can quantify what "enough 3D speed" means, then perhaps that can be assessed. There really aren't many applications around at the moment to make this an issue. I'd be more interested in it's

This is better bug report: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50099 Regards, -- Martin 'JaMa' Jansa jabber: Martin.Jansa@...

Sorry, this was my mis-understanding of Darren's comment. Version of lttng-ust is 0.15. Initially I tried to do something with tcmode-default, setting lttng-ust similar to meta-xlib which also had a

Which version of lttng-ust is this exactly? In addition to what Darren is saying about how this should be papered-over at the recipe level until gcc itself is fixed... -- Tom

Sorry, I didn't mean for this to be a final solution, just a means to determine the problem. Removing neon eliminates the vector floating point, which we do not want to do. The correct fix for this is

[YOCTO #1381] lttng-ust generates an ICE when building for armv7, so change it to armv5 | vfprintf.c:956:1: error: unrecognizable insn: | (insn 3968 3967 3969 145 (set (subreg:SI

Thanks to Darren for helping with this one. Sau! The following changes since commit b2266beeb357bae938830f559845f5f3deb4f916: usermanual: The git fetcher defaults to the git protocol (or file)

Given the increased interest in preempt-rt support, I think it would make sense to do so. It certainly adds a further burden to the release process. Beth? -- Darren Hart Intel Open Source

Quoting Gordan Bobic <gordan@...>: It does seem outlandish, but it is kind of cool. Is it going to give enough 3d speed? The next gen tegra is supposed to have a 24 core GPU. It is probably

Are we building and delivering RT images for the release? If not then there is no need. Sau!

The big win for hard float ABI (emphasis mine) is functions that return floating point values. I personally care about this, but we also know returning floats is "bad" so we sort of avoid it. I agree

Just the general ones that have caused people to say softfp+neon isn't enough (outside of povray :)). -- Tom

I presume we need a linux-yocto-rt_3.0.bbappend as well? -- Darren -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel

Are you referring to a specific performance measure? Jason, Koen, are there any such config bits? We are currently using the cortexa8-neon tune configuration from oe-core. -- Darren Hart Intel Open

Unfortunately there is no way I could make it, but on the subject of 3D support on ARM, Luke recently mentioned something that initially seemed outlandish but upon closer examination doesn't seem like

UPDATE: we've not had many people confirm interest in this event yet, which is a shame. If you would like to join us for this session, please reply and let me know. If we don't get enough interest by

Hi all, We now have the mechanism for fixing bug #1096 [1] i.e. showing a warning if the user is running a build on a distro that has not been tested; however to make this work what we now need is

Well, are there some softfp related config bits we need on the yocto side that meta-ti has, in order to bring that performance back in line? -- Tom