From owner-freebsd-x11@freebsd.org Sat Feb 6 00:50:24 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5AAADA9E754 for ; Sat, 6 Feb 2016 00:50:24 +0000 (UTC) (envelope-from jean-sebastien.pedron@dumbbell.fr) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2AF2C1EF3 for ; Sat, 6 Feb 2016 00:50:24 +0000 (UTC) (envelope-from jean-sebastien.pedron@dumbbell.fr) Received: from [176.158.145.63] (helo=[192.168.75.14]) by mail.made4.biz with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86 (FreeBSD)) (envelope-from ) id 1aRr4w-0005s3-GX for freebsd-x11@freebsd.org; Sat, 06 Feb 2016 01:50:22 +0100 Subject: Re: Does FreeBSD support OpenGL 3.3? References: <20160115103123.097be7d9@fujitsu> <5698A68D.8080202@dumbbell.fr> <20160115214315.4ee47348@fujitsu> To: freebsd-x11@freebsd.org From: =?UTF-8?Q?Jean-S=c3=a9bastien_P=c3=a9dron?= Message-ID: <56B5434E.8070907@dumbbell.fr> Date: Sat, 6 Feb 2016 01:50:22 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <20160115214315.4ee47348@fujitsu> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Feb 2016 00:50:24 -0000 Le 15/01/2016 19:43, Eax Melanhovich a écrit : > So for now only OpenGL 3.2 is provided. How can I figure out if it's > some sort of bug / wrong configuration or the best I can get on this > hardware? I'm pretty sure Ivy Bridge can do better than OpenGL 3.2. This must be a limitation due to our kernel driver. We'll see if the next update fixes this for you. -- Jean-Sébastien Pédron