From owner-freebsd-current@freebsd.org Thu Sep 17 19:22:37 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 F03A09CED40 for ; Thu, 17 Sep 2015 19:22:36 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 A8CC91FEA; Thu, 17 Sep 2015 19:22:36 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1ZcelO-000Ivf-Cg>; Thu, 17 Sep 2015 21:22:34 +0200 Received: from x5ce12e0c.dyn.telefonica.de ([92.225.46.12] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1ZcelO-0019uS-4H>; Thu, 17 Sep 2015 21:22:34 +0200 Date: Thu, 17 Sep 2015 21:22:28 +0200 From: "O. Hartmann" To: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= Cc: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917212228.75ec5471.ohartman@zedat.fu-berlin.de> In-Reply-To: <55FAF19F.9090701@FreeBSD.org> References: <55FA7324.5010603@icloud.com> <55FAF19F.9090701@FreeBSD.org> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/JyaEppME6Z7Vn25cI6kSWB3"; protocol="application/pgp-signature" X-Originating-IP: 92.225.46.12 X-ZEDAT-Hint: A 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 19:22:37 -0000 --Sig_/JyaEppME6Z7Vn25cI6kSWB3 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Am Thu, 17 Sep 2015 19:00:15 +0200 Jean-S=E9bastien P=E9dron schrieb: > Hi everyone! >=20 > I'm very sorry I didn't communicate at all on the i915 update project. >=20 > So here is a status update: since this morning, the driver builds fine. > I'm currently attending the XDC (X.Org Developers Conference) and don't > have an Intel laptop to test with me. However, Johannes Dieterich (also > attending the conference) offerred his help, so we will do that today. >=20 > Obviously, do not expect something stable in the coming couple days. > Thank you for your patience :) >=20 > To answer various questions in this thread: >=20 > Why does it take so much time to update? Once Konstantin committed his > i915 update, I was busy with non-FreeBSD activities until last July, > when I slowly started back to work on i915. My goal is to reduce the > diff with Linux as much as possible. But, as opposed to OpenBSD and > DragonFlyBSD, we do not use a Linux compatibility layer which would > dramatically ease our life. My concerns are speed and performance. Isn't any kind of layer consuming pe= rformance - sometimes worse, sometimes negligible. But anyway, HPC isn't a FreeBSD doma= in, so ... >=20 > This layer exists for the OFED/Infiniband drivers: we are almost ready > to move it to a central place, so we can use it in the near future in > the DRM subsystem. it would be nice to see a performance comparison between the "original" in = Linux and then the layered in freeBSD ... >=20 > Another problem I will fix in the near future is the method I used: I > worked on a giant patch instead of doing several incremental commits. > This is unfriendly for external contributors and hard to review. > DragonFly got that right for instance. >=20 > Now about other related tasks: > o A Mesa update will be committed Real Soon Now=99. It will unlock > GLAMOR and OpenCL support. This to hear is like a symphony to my ears ... > o Once Mesa is updated, we can update xserver to 1.17.2. xserver > 1.18 RC 1 works fine (at least for me :). It should be released > for Halloween. ... and even better ;-) > o Wayland. The problem is NOT the output side of the graphics > stack: it is the input part. We miss evdev (ported as a GSoC, > waiting for review and commit), we miss udev, we miss libinput. > This item deserves a dedicated email. One "advantage" of the Berkeley derived UNIXes is that they did not cover t= he mess Linux was in its first years - and, from my personal experiences with security rl= eated govermental stuff - still is! The spoken of facilities are "generic" or are they Linux-unique and have to= be adopted for FreeBSD? >=20 > Sorry, it's a bit short for such a large topic. It's difficult to expand > more during a conference :) >=20 --Sig_/JyaEppME6Z7Vn25cI6kSWB3 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJV+xL0AAoJEOgBcD7A/5N8KhEH/00ffNtLhuGM8igoZway9GKr VohTZLykwFbcgNG6f2ZIY8JFsfQp/IsvxBcDrjGku/Pg7m1mVxKveLKUjrtTd7pU LGnhwFdWlOQgzKOOBG/5kfTfwXtLBMgOTxa4HBRlGeUBdHRfhWQRnjk8BseVrFiO z1d2YHaNca65zZLi3yJx0j0KPxd2uBEQkx+W4bpA+J/TEgKZKGpiMD8hsHuTh7e0 bxoxI1IW8K1zfaG+WDhDi4y3GyuBDmrPM9TQjMPLPAxeyBBSdiAga2AJIFp8+9XF ypjMAzSybIeDsnrulB+N8V/Mn3iCaD/qQxSgLjUYhL1xrgvPa1eIhuF/jvaRlQs= =dRkG -----END PGP SIGNATURE----- --Sig_/JyaEppME6Z7Vn25cI6kSWB3--