From owner-freebsd-current@freebsd.org Tue May 22 06:50:51 2018 Return-Path: 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 AEAB5EE8C6F; Tue, 22 May 2018 06:50:51 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 1E55D86395; Tue, 22 May 2018 06:50:51 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id f6-v6so29054397wmc.4; Mon, 21 May 2018 23:50:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OsVzucqZ1ZiqjXY0naWFOG0g3/ihFYREOxDXrs7+Jdk=; b=QZsypmxMJyWeOB7Hr/snoWDAbeXNTvo/7u6W4N14MpUWeiKesIfjbSvBrTruq9fQ8g uaXmVwaqu2ZfDsA3osinkOAXm9iZsZCObls5rg8f/aAVC8I+akwwx9MIfYJlCorpfOKM whY15DHPZJsP9719WmOQX8Qf8l2SU2F4zmE5/adgdw6lzSntTxDUvy1pz64EVxs4qyDs /L965gNc+uQrRkbcOqijCeR34UbUXktXMwOXF0BMe6sOdgqUQ9TRG+xoz/epSwhKNPBB RyGEnJL6SpF9qOPrEfH7kyVD45MKgJHE9BEEpKF++wI+V4wZLp4yB3igU5XqYl565kPb Fw7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OsVzucqZ1ZiqjXY0naWFOG0g3/ihFYREOxDXrs7+Jdk=; b=qVse5wAfO2uy6JEpBt6MsOpeC6D4OxCCvrPJL48Xy7MRKBCPcplZo1/LLaxT73il6I dnWhM3oPbzgfITNpjTk+2XD39n6ww9MeItU49d6gtxMgJ21opHc+Mtsv7Az4+jHL31Kr Lxv/dc5gv0leW72tFTJhXZ2bJNQDke3xzNFGjiEGb+HuTu3zVXU35fhEVROZwID0UyCS afmePmiGlmzCUAPHVPOQOl4/IKs6ebYT5VhPz8FOk3ddEmSAIDntOfUMErxen+qD+qTQ UbGfQI4e227hPGjbDQLU5jHZTan2GwcagHX5aWWK6m/xDMqHCm6WPTecKK6ZlUY1kWCs Gdgw== X-Gm-Message-State: ALKqPwdeFnuYg9ApzZLs4mGrdrjToUpk1qfebuTMaXG3qbajtij3DSD5 Nf/y2hRdFzVOIxM+bj21l/mzU2fO+hvfIMXjVP4= X-Google-Smtp-Source: AB8JxZplDUrTcUwFnprohKKyl2Fpu6GvbWRzTwWZqn8hgX3os+BmM4xR22wCgVY0Awf0qXys1bqx5DLe3rH6PCHnQoY= X-Received: by 2002:a1c:be0f:: with SMTP id o15-v6mr174210wmf.104.1526971849587; Mon, 21 May 2018 23:50:49 -0700 (PDT) MIME-Version: 1.0 References: <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> In-Reply-To: <20180521224927.GA9925@troutmask.apl.washington.edu> From: Johannes Lundberg Date: Tue, 22 May 2018 07:50:39 +0100 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: sgk@troutmask.apl.washington.edu Cc: Current FreeBSD , FreeBSD X11 mailing list , "K. Macy" , Niclas Zeising , Oliver Pinter , Rozhuk Ivan , Warner Losh Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2018 06:50:52 -0000 On Mon, May 21, 2018 at 23:50 Steve Kargl wrote: > On Mon, May 21, 2018 at 03:20:49PM -0700, K. Macy wrote: > > > > > > I just ask. > > > Or why not include drm-next to base svn repo and add some > > > option to make.conf to swith drm2/dem-next ? > > > > Even if it's not being built on amd64 we're still responsible for > > keeping it building on !amd64 so long as it's in base. This makes > > changing APIs and universe runs more burdensome. The graphics > > developers have given you notice that it will now be your collective > > responsibility to keep it up to date. > > > > Not quite. One graphics developer has indicated a desire > to remove working code, because it interferes with the > graphics developers' port on a single architecture. There > is no indication by that graphics developer that drm2 will > be available in ports. You can go read the original post > here: > > https://lists.freebsd.org/pipermail/freebsd-current/2018-May/069401.html > > The last paragraph is > > What does the community think? Is there anyone still using > the drm2 driver on 12-CURRENT? If so, what is preventing > you from switching to the port? > > The answer to the last two questions are "yes" and "the port > does not work on i386". > > Yes, I recognize that you're clever enough to purposefully > break the API so that you can thumb your nose at those of > us who have older hardware. > > What is wrong with using > > .if ${MACHINE_ARCH} !=3D amd64 > ... > .endif > > to enable/disable drm2? The answer to the first question is that the consensus seem to be that moving to a port is best for the _majority_. Let me ask you, what=E2=80=99s wrong with this one-liner after base install pkg install drm2 ? > > -- > Steve > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" >