From owner-freebsd-current@freebsd.org  Fri Sep 28 20:46:58 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 CF55910B9127
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 28 Sep 2018 20:46:58 +0000 (UTC)
 (envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
 [128.95.76.21])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "troutmask", Issuer "troutmask" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 6436F81D9D
 for <freebsd-current@freebsd.org>; Fri, 28 Sep 2018 20:46:58 +0000 (UTC)
 (envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (localhost [127.0.0.1])
 by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w8SKkvVL003460
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Fri, 28 Sep 2018 13:46:57 -0700 (PDT)
 (envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
 by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w8SKkuHZ003459;
 Fri, 28 Sep 2018 13:46:56 -0700 (PDT) (envelope-from sgk)
Date: Fri, 28 Sep 2018 13:46:56 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Matthew Macy <mat.macy@gmail.com>
Cc: Warner Losh <imp@bsdimp.com>, fullermd@over-yonder.net,
 freebsd-current <freebsd-current@freebsd.org>
Subject: Re: drm2 in base
Message-ID: <20180928204656.GD2631@troutmask.apl.washington.edu>
Reply-To: sgk@troutmask.apl.washington.edu
References: <20180928180002.GA957@troutmask.apl.washington.edu>
 <20180928194739.GH32731@over-yonder.net>
 <20180928200102.GA2631@troutmask.apl.washington.edu>
 <CANCZdfq0E=euENS_ougvDXB_p5pji6vwOhf0nMCuN_jEQmg6hQ@mail.gmail.com>
 <CAPrugNrf1BwDXXwxrdh-eeqNa=yr1f1ERApmcaPfV4h2KeS4oQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPrugNrf1BwDXXwxrdh-eeqNa=yr1f1ERApmcaPfV4h2KeS4oQ@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Sep 2018 20:46:59 -0000

On Fri, Sep 28, 2018 at 01:30:59PM -0700, Matthew Macy wrote:
> 
> Bug reports are addressed as they come in. If issues haven't come up
> it likely reflects a scarcity of users.
> 

It is likely that -current users are still using drm2 from
base (or have sufficiently new hardware that drm-stable-kmod
works for them).  I saw Glen's post about the updated
release schedule, and decided to be pro-active in moving
to drm-*-kmod to counter the possibility that someone
might remove drm2 from head as soon as the FreeBSD-12 branch
exists.

-- 
Steve