Date: Thu, 17 Sep 2015 19:00:15 +0200 From: =?UTF-8?Q?Jean-S=c3=a9bastien_P=c3=a9dron?= <dumbbell@FreeBSD.org> To: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <55FAF19F.9090701@FreeBSD.org> In-Reply-To: <55FA7324.5010603@icloud.com> References: <55FA7324.5010603@icloud.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Omi9RXjqAIGvohvOv5xcm9ie5iag7IQOs
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Hi everyone!
I'm very sorry I didn't communicate at all on the i915 update project.
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.
Obviously, do not expect something stable in the coming couple days.
Thank you for your patience :)
To answer various questions in this thread:
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.
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.
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.
Now about other related tasks:
o A Mesa update will be committed Real Soon Now=99. It will unlock
GLAMOR and OpenCL support.
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.
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.
Sorry, it's a bit short for such a large topic. It's difficult to expand
more during a conference :)
--=20
Jean-S=E9bastien P=E9dron
--Omi9RXjqAIGvohvOv5xcm9ie5iag7IQOs
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQJ8BAEBCgBmBQJV+vGkXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz
OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMRuYQAOC4JlLww2FdzQJWOquh2L1h
+Mq0O2eoaxyUo413XEajd2Go+OA4nM5kXYmJV6XB+slL7nuYL6NhkTBvewKq07HD
LjdNuDRCS7gSNPqOr215PULQ8JY0hxUtk2ON3GWTrh38aGTIo3Y0np+3DOGI4vvI
uGwIW7Wj7pxltpXIYl4p7Wuhe8+FwpNDSFglhD1pDCiRqD1PpV/ZjiP9PRy8W19d
F8Unkr2g8b+RG0eKJUAcpLb/63RJhbb/RSBgJe0PIHwxlymsLRsajjgtvRwJkuYS
uhSMTcaepT269MnRLV0WHPALfGpEjYOmCRWx3GFQlSntIoi5a17IF9GKPScYlj0k
FNZtQfSIRgJYKhUfo6HXvYaaKYHc+SJOzSRtm9DgRVTI+dx88CkLg9fkuu3DKDcN
w8KvZYZyHLuvg4Xo1h7GsYD2iMVF9DK/hOah3fZBZZrQFB/CFgTpGTpb+Seb32e8
Q1qb3SIPSvqKvoPUHByzrkBh1Z5eqmQqL7P9trnbPgHtMNu8Qi5YTEdIKvnbOsWn
a0VS9lVeeAEBOfc9h7gwmKIKn1RuEGKIvfS6FD6DM/oVSG/Zh78JLYbd26jUpT+N
qtOPAxMwyLgDrsZx3SaJbUHqZKIBWGMIl2Oov6UFmpRk9kvLxqQjLQm1iitgWs4U
zqm+qmGOZnRYBldphegW
=C2k1
-----END PGP SIGNATURE-----
--Omi9RXjqAIGvohvOv5xcm9ie5iag7IQOs--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55FAF19F.9090701>