From owner-freebsd-x11@freebsd.org Tue May 8 16:51:11 2018 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B65EFBB678 for ; Tue, 8 May 2018 16:51:11 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 D1ED7787E4 for ; Tue, 8 May 2018 16:51:10 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.208] (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id a628fb20 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 8 May 2018 09:51:08 -0700 (PDT) Subject: Re: current state of Intel support To: "Zane C. B-H." , freebsd-x11@freebsd.org References: <52dd5fb08cbaa1fb61f9d2f85c1a3e84@vvelox.net> From: Pete Wright Message-ID: <9b9f3530-7bd4-e5c9-0443-36d6d622af1d@nomadlogic.org> Date: Tue, 8 May 2018 09:51:07 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <52dd5fb08cbaa1fb61f9d2f85c1a3e84@vvelox.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2018 16:51:11 -0000 On 05/08/2018 01:01, Zane C. B-H. wrote: > I am curious, where are we at on 11 stable when it comes to support > for newer Intel chipsets? Just wondering how usable X is when it comes > to x5-Z8350 Cherry trail or the like. the current state of the drm-next-kmod should be in sync with the linux-4.9 kernel, so if a device is supported on that revision on linux then chances are it will just work on drm-next.  there is work happening to bring the codebase up to sync with the linux-4.11 kernel as well. the benefit of drm-next-kmod being a port is that you can benefit from the work being done on 12-CURRENT in 11-STABLE as they port codebase is the same between both of those branches I believe. cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA