Re: My progress on armhf: xf86-video-msm for armhf attempt. Please test.

2011-09-02 Thread Lennart Sorensen
On Sat, Sep 03, 2011 at 12:26:05AM +0100, Paul Brook wrote: > Obviously if your code assumes [say] a Cortex-A8 and uses NEON assembly > without checking first than all bets are off. There are two ways of > resolving > this: > - Don't do that. > - Hack the makefile to always build with NEON enab

Re: My progress on armhf: xf86-video-msm for armhf attempt. Please test.

2011-09-02 Thread Paul Brook
> On Fri, Sep 02, 2011 at 10:06:55PM +0100, Paul Brook wrote: > > Right. That's almost certainly a bug. My guess would be cargo-cult > > copying or an old hack to workaround borkenness elsewhere. > > OK, so simply removing the explicit CFLAGS settings in the Makefile, > should make the package w

Re: My progress on armhf: xf86-video-msm for armhf attempt. Please test.

2011-09-02 Thread Lennart Sorensen
On Fri, Sep 02, 2011 at 10:06:55PM +0100, Paul Brook wrote: > Right. That's almost certainly a bug. My guess would be cargo-cult copying > or an old hack to workaround borkenness elsewhere. OK, so simply removing the explicit CFLAGS settings in the Makefile, should make the package work correct

Re: My progress on armhf: xf86-video-msm for armhf attempt. Please test.

2011-09-02 Thread Paul Brook
> On Fri, Sep 02, 2011 at 03:10:50AM +0100, Paul Brook wrote: > > Your understanding is incorrect. Thumb interworking is always enabled > > when generating armv5 or later code, plus it is enabled by default for > > all EABI based targets. Both of which are true for armhf. > > Well in that case,

Re: My progress on armhf: xf86-video-msm for armhf attempt. Please test.

2011-09-02 Thread Lennart Sorensen
On Fri, Sep 02, 2011 at 03:10:50AM +0100, Paul Brook wrote: > Your understanding is incorrect. Thumb interworking is always enabled when > generating armv5 or later code, plus it is enabled by default for all EABI > based targets. Both of which are true for armhf. Well in that case, there was