jamesh wrote:What MasterLuke said. XBMC already uses the HW acceleration (it uses dispmanx - Dom does a lot of work on XBMC I believe) which is why is actually pretty damn fast on a Raspi. Its the backend stuff (ethernet etc) that slows it down in my experience, although not enough to be a problem.
It's definitely not just IO that slows down the Pi with XBMC.
One example is playing a video, and pressing escape, so that the menu shows while the video is playing in the background. While the video plays totally smooth when it's just video, showing the menu overlaid the video makes video playback choppy.
I suspect this is the case because the Pi's capabilities aren't used fully. I suspect this is because XBMC just gets a GL surface via DispManX to paint onto what it needs to, instead of acquiring separate surfaces in DispManX for the video and the menu. But I admit I really don't know if this is the case.
That being said, running XBMC in Weston should make no difference. It's how XBMC uses DispManX that should make the difference, and this is independent of whether it's running in a VT or in Weston.