From owner-freebsd-current@freebsd.org Mon May 21 22:15:47 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 69812EFFA4E; Mon, 21 May 2018 22:15:47 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (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 D0D7873ADF; Mon, 21 May 2018 22:15:46 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: by mail-wm0-x22e.google.com with SMTP id w194-v6so27600776wmf.2; Mon, 21 May 2018 15:15:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=NYWQpyjGlAmqhsBVj6hx9N0N+iNWWOHZZpzqDlOqYIw=; b=t2Hyu5lamtSZIi+Qcmq4bNjlFYc/wPLlvfBV0tEaDpoB8WtXqSNJrEp/RF6LwFMC1Z tTb80ek50HL7hBXp1f1aRSm4kqgcyOuqrZoIMkOxkIzslpd7G4X2Yy9vkhpmNOXlg6KR jk7D064KXa5KuhmjUYnQCqQ5Gf1HdpvsFZmgeQBIaBEjREVgi3yL5yQdlr/qhwTiLOqn 5fZjmsfAaElXQRApxQh8Gwx9Zv1yuHkCrF28eZUAP5vDooQDtP3eCC/CM5wbYsfIAhhS Fm/9YcuVXSXGO3TSUfQ/zgQ0VTyk9e33maKfI8zyg4WGRPUZ17xhe7HraYoN4QccOGnd nnTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=NYWQpyjGlAmqhsBVj6hx9N0N+iNWWOHZZpzqDlOqYIw=; b=Yn1bKpafJpL52RURycGQ9BHRQq4wK9slwvIDImi8afo1Mb3+IAqSxD3ckSZGAC3YBa pVB1iVV0KPV/lZho3UuChhHcuNu0231VUge+s1NrOIhjFk/kZcKPpEIuqwTG8uMDmxoq IJ6CAVKHyH8JwbWeeTvJUnKID2ty5vod+j/baGjSKrGfGCFe87gGPxSiloyIX2CmnKkO P5pMwOvHhNYZWHbKsjkfiwFYDkjdX7zHa9FMdvQj5hZHs1s3xBLBOVuPesQCtsC2tLys +OSMfi7e10fdDf3Jfz3I0bB8f8WxLc/iSag34Vsy6o0Cm0ou2Sme52Zprj0rSqwrf0T1 GBdA== X-Gm-Message-State: ALKqPwcMk1/3HFKOWoOzJTe4PxvwftrW3/ETj1fxECcaxZJ6QSJNOETk RpUMpQDpbehgIx7U05nCwspd4P7o X-Google-Smtp-Source: AB8JxZoBHZxy/QbWtc8zrxD9PJcRiMnmPXy/Tx+9T7n5hNHHGtI7an1y1cQYOswHHqQafp4qRE2C7Q== X-Received: by 2002:a50:8f21:: with SMTP id 30-v6mr25361016edy.265.1526940945837; Mon, 21 May 2018 15:15:45 -0700 (PDT) Received: from localhost ([2001:470:1f15:3d8:7285:c2ff:fe37:5722]) by smtp.gmail.com with ESMTPSA id i22-v6sm7579457eds.28.2018.05.21.15.15.44 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 21 May 2018 15:15:44 -0700 (PDT) From: Rozhuk Ivan X-Google-Original-From: Rozhuk Ivan Date: Tue, 22 May 2018 01:15:43 +0300 To: Steve Kargl Cc: Oliver Pinter , Niclas Zeising , Warner Losh , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180522011543.3f621882@gmail.com> In-Reply-To: <20180521170728.GA14025@troutmask.apl.washington.edu> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <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> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Mon, 21 May 2018 22:15:47 -0000 On Mon, 21 May 2018 10:07:28 -0700 Steve Kargl wrote: > Why? "If it isn't broken, why fix it?" > > The conflict affects x86_64-*-freebsd aka amd64. The > conflict does not affect any other architecture. The > Makefile infrastructure can use MACHINE_ARCH to exclude > drm2 from build of amd64. > > I don't use netgraph or any of the if_*.ko modules. > Can we put all of that into ports? I don't use any > scsi controllers, so those can go too. Why make it > insanely fun for users to configure a FreeBSD system. > 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 ?