Hello community,

here is the log from the commit of package xorg-x11-drv-omapfb for 
openSUSE:12.2 checked in at 2012-07-02 12:56:46
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:12.2/xorg-x11-drv-omapfb (Old)
 and      /work/SRC/openSUSE:12.2/.xorg-x11-drv-omapfb.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "xorg-x11-drv-omapfb", Maintainer is ""

Changes:
--------
--- /work/SRC/openSUSE:12.2/xorg-x11-drv-omapfb/xorg-x11-drv-omapfb.changes     
2012-06-25 16:17:58.000000000 +0200
+++ 
/work/SRC/openSUSE:12.2/.xorg-x11-drv-omapfb.new/xorg-x11-drv-omapfb.changes    
    2012-07-02 12:56:47.000000000 +0200
@@ -1,0 +2,5 @@
+Mon Jul  2 08:03:48 UTC 2012 - [email protected]
+
+- Only enable armv7l and armv7hl build since it has asm neon optimization 
which is unsupported on armv5
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ xorg-x11-drv-omapfb.spec ++++++
--- /var/tmp/diff_new_pack.qzYnGf/_old  2012-07-02 12:56:47.000000000 +0200
+++ /var/tmp/diff_new_pack.qzYnGf/_new  2012-07-02 12:56:47.000000000 +0200
@@ -14,17 +14,20 @@
 
 # Please submit bugfixes or comments via http://bugs.opensuse.org/
 #
+
+
 Name:           xorg-x11-drv-omapfb
 Summary:        X.Org X server -- Omapfb display driver (NEON optimized)
 License:        GPL-2.0+ and MIT
 Group:          System/X11/Servers/XF86_4
 Version:        0.1.1.20110503
 Release:        0.0
-ExclusiveArch:  %{arm}
+ExclusiveArch:  armv7l armv7hl
 Url:            http://cgit.pingu.fi/xf86-video-omapfb/
 Source0:        xf86-video-omapfb-%{version}.tar.bz2
 Source1:        20-omapfb.conf
-Requires:       xorg-x11-server Mesa
+Requires:       Mesa
+Requires:       xorg-x11-server
 BuildRequires:  autoconf
 BuildRequires:  automake
 BuildRequires:  libtool

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to