From owner-freebsd-current@freebsd.org Thu Sep 17 13:48:11 2015 Return-Path: Delivered-To: freebsd-current@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 5B1A39CE5E7 for ; Thu, 17 Sep 2015 13:48:11 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3A8E713B0 for ; Thu, 17 Sep 2015 13:48:11 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 37D8B9CE5E5; Thu, 17 Sep 2015 13:48:11 +0000 (UTC) Delivered-To: current@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 3767D9CE5E4 for ; Thu, 17 Sep 2015 13:48:11 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloud.theravensnest.org", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E03A413AE for ; Thu, 17 Sep 2015 13:48:09 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from dhcp-172-17-234-62.eduroam.wireless.private.cam.ac.uk (global-1-31.nat.csx.cam.ac.uk [131.111.184.31]) (authenticated bits=0) by theravensnest.org (8.15.2/8.15.2) with ESMTPSA id t8HDlnkJ050535 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Sep 2015 13:47:51 GMT (envelope-from theraven@FreeBSD.org) X-Authentication-Warning: theravensnest.org: Host global-1-31.nat.csx.cam.ac.uk [131.111.184.31] claimed to be dhcp-172-17-234-62.eduroam.wireless.private.cam.ac.uk Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: Intel Haswell support - Any updates? From: David Chisnall In-Reply-To: Date: Thu, 17 Sep 2015 14:47:43 +0100 Cc: Adam McDougall , "current@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> To: "Lundberg, Johannes" X-Mailer: Apple Mail (2.2102) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 13:48:11 -0000 On 17 Sep 2015, at 14:41, Lundberg, Johannes = wrote: >=20 > However, the problem now is not the driver right? But the whole = graphics > stack which has to be rewritten to work with new generation graphics = like > KMS, Wayland, etc? There are lots of different components here that you=E2=80=99re = conflating: - KMS is the thing that allows the kernel to be responsible for setting = the graphics mode, restoring it on context switches and so on. This has = worked on FreeBSD for a while. - GEM / TTM are memory managers, they allow the kernel to manage memory = (video memory and main memory allocated to the GPU) for GPU-using = drivers. These work on FreeBSD, but the supported version lags Linux = slightly. This is the focus of current work. - The i915 driver. This is the graphics driver for Intel GPUs. It uses = KMS and the memory manager functionality. Importing a newer version will = be possible once the underlying parts are done. - Wayland is a userland application that sits on top of DRI drivers, = just as X.org does. Most of the things Wayland needs that don=E2=80=99t = work on FreeBSD are not graphics related. The problem is that the developers *also* conflate them. Upstream i915 = developers will add KPIs to GEM / TTM / KMS to make their lives easier = and these features need bringing across to FreeBSD. David