From owner-freebsd-x11@freebsd.org Sat Apr 22 19:20:50 2017 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 0B85ED4B0B2 for ; Sat, 22 Apr 2017 19:20:50 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id DCCBFBD6 for ; Sat, 22 Apr 2017 19:20:49 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id D8E45D4B0AF; Sat, 22 Apr 2017 19:20:49 +0000 (UTC) Delivered-To: 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 D84CED4B0AD; Sat, 22 Apr 2017 19:20:49 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9F766BD2; Sat, 22 Apr 2017 19:20:49 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-io0-x229.google.com with SMTP id p80so30557611iop.3; Sat, 22 Apr 2017 12:20:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=4uoxAnEUMuBYIiag5G8m1bQIOYjYRhPiKM3isr+ZPOY=; b=th58zj786418UOyn1D77lV3tyczzxWifMJeQ8/Yxs3XzRT6Af3m257eIvwaxhBf28e V6kWhfaNl3wkMB6UTGcS/hXTmMAsjBLthUyX9oOpegHm7dLGpyEDZVYf0hOjT8exhyo+ Jadg42Pcw5yNotyj6AC8UOiwFHsLqsW7NzI75S4skQKab70VFf+JzWkq+2WF+eHD1FUM AyZ77nykcxv6yzMEWbinXkPU6F3K+WDYd3VTjqEVwmaMnGZ8RivuOWICkrUNFeAmu3+Y JNA522I67qgK76hpAsZTeiW1/Pu3e57r5E6Vkd4UKLfC98Q2L2q+HuIm8/ggIqN2YahF lHfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=4uoxAnEUMuBYIiag5G8m1bQIOYjYRhPiKM3isr+ZPOY=; b=DaxmNp6enesVR2YJlu8ZnFyHYNiDMwOAu0VY6+WwaWx0xTHMm76AIAmB9+CAHP702K +sQp8SMctDqNY7F1Bidbo7SKzQ3IqCIUvNa1Au53iP6RhbXUi3pwgaOl9bo48Y8uMAge xKjDBvNAF3XMXHe5C+jUb8HjR7l47a/nCYvTm+wpNAdqRz4TX7AcVtZDFmC4DrIV4F7z bQnNmJjHA8ZZXBhWIX98z40kwtzPQ54NSGuGlStJ5tmnTlODQiakccBtHTk3kOb1SOvs oOmOUDEE4SNT+IoDJiZYuazS1UE5Yq4wUwP1Fyp47HkLk56jqfSGOSRgFzBs/Dv975yk fz7w== X-Gm-Message-State: AN3rC/6GV2U50qe28O1J6xy2Tt6D+FzH0eZ5Su1KetDFFdzZqSg75F18 Fj6Fi8lO91uDEg== X-Received: by 10.98.93.147 with SMTP id n19mr17805605pfj.226.1492888848972; Sat, 22 Apr 2017 12:20:48 -0700 (PDT) Received: from raichu ([2604:4080:1102:0:ca60:ff:fe9d:3963]) by smtp.gmail.com with ESMTPSA id 3sm2796802pfe.20.2017.04.22.12.20.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 22 Apr 2017 12:20:48 -0700 (PDT) Sender: Mark Johnston Date: Sat, 22 Apr 2017 12:20:46 -0700 From: Mark Johnston To: Eric McCorkle Cc: Hans Petter Selasky , x11@freebsd.org, multimedia@freebsd.org Subject: Re: Status of i915 (drm-next commits) in HEAD Message-ID: <20170422192046.GB11436@raichu> References: <8d4600d1-8676-1284-3350-ebcba954efb6@selasky.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.23 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, 22 Apr 2017 19:20:50 -0000 On Sat, Apr 22, 2017 at 09:39:00AM -0400, Eric McCorkle wrote: > How often is drm-next getting synced with master these days? The most recent merge brought us up to r317039. > The current version is getting panics in the ath driver that seem to > have been fixed in head... There haven't been any modifications to sys/dev/ath in the past month, so I'm not sure which fixes you're referring to. > > On 04/21/2017 05:26, Hans Petter Selasky wrote: > > On 04/21/17 02:43, Eric McCorkle wrote: > >> Hello, > >> > >> I lost track of the status of the drm-next work, specifically how much > >> of it has made its way into head. > >> > >> More to the point, I'm running broadwell graphics (HD5500 and HD6100) > >> cards; are these supported under HEAD, or do I need to keep building off > >> the drm-next branch? > >> > > > > Hi Eric, > > > > drm-next is close to becoming a port for -current. > > > > You still need to build drm-next for it to work. > > > > --HPS