Date: Sat, 22 Apr 2017 12:20:46 -0700 From: Mark Johnston <markj@FreeBSD.org> To: Eric McCorkle <eric@metricspace.net> Cc: Hans Petter Selasky <hps@selasky.org>, x11@freebsd.org, multimedia@freebsd.org Subject: Re: Status of i915 (drm-next commits) in HEAD Message-ID: <20170422192046.GB11436@raichu> In-Reply-To: <f675d9ee-fed7-9957-283e-332a1e156d6f@metricspace.net> References: <f09ef027-2169-bd59-7482-d8fbb1bd371c@metricspace.net> <8d4600d1-8676-1284-3350-ebcba954efb6@selasky.org> <f675d9ee-fed7-9957-283e-332a1e156d6f@metricspace.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170422192046.GB11436>