From owner-freebsd-x11@FreeBSD.ORG Sun Feb 9 19:03:57 2014 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7D5E997E for ; Sun, 9 Feb 2014 19:03:57 +0000 (UTC) Received: from fep12.mx.upcmail.net (fep12.mx.upcmail.net [62.179.121.32]) by mx1.freebsd.org (Postfix) with ESMTP id BBCA51D11 for ; Sun, 9 Feb 2014 19:03:56 +0000 (UTC) Received: from edge03.upcmail.net ([192.168.13.238]) by viefep12-int.chello.at (InterMail vM.8.01.05.13 201-2260-151-135-20130320) with ESMTP id <20140209190348.JCKG76925.viefep12-int.chello.at@edge03.upcmail.net>; Sun, 9 Feb 2014 20:03:48 +0100 Received: from [127.0.0.1] ([178.84.134.112]) by edge03.upcmail.net with edge id QK3n1n01o2Rg3Ey03K3oap; Sun, 09 Feb 2014 20:03:48 +0100 X-SourceIP: 178.84.134.112 Message-ID: <52F7D113.8050900@rainbow-runner.nl> Date: Sun, 09 Feb 2014 20:03:47 +0100 From: Koop Mast User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Java Boy , "freebsd-x11@freebsd.org" Subject: Re: Mesa 10.0.3 is a bug fix release References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 140209-0, 09-02-2014), Outbound message X-Antivirus-Status: Clean X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2014 19:03:57 -0000 On 8-2-2014 20:43, Java Boy wrote: > Guys > will mese update you working on get the above fixes in it? ( http://www.mesa3d.org/relnotes/10.0.3.html) > > regards > In our xorg-dev staging/developement repo the Mesa in the experimental branch has been updated to 10.0.3. This version will not make it to ports for a while yet because it does not work with our intel KMS kernel driver. -Koop