From owner-freebsd-x11@freebsd.org Mon May 21 20:16:13 2018 Return-Path: Delivered-To: freebsd-x11@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 CE400EFD51E; Mon, 21 May 2018 20:16:13 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-ot0-x243.google.com (mail-ot0-x243.google.com [IPv6:2607:f8b0:4003:c0f::243]) (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 602536E5BC; Mon, 21 May 2018 20:16:13 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-ot0-x243.google.com with SMTP id m11-v6so18308576otf.3; Mon, 21 May 2018 13:16:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=rhybfzuGjA9IXalKlmn62EtLiE9B87lqvq3xGzEjrOI=; b=Pww4mHFQ0f5fPI7ISxJwSskhyeUbAFy/bvT29Rs8JqPE1Z6sCcrRs8e5XbpDa07M55 lI2iTISb4KUlFDy6YRQpjqmK7OXiLZdd+5krF3vzJQgFP+vUwUWEtuJnc/zU7rrttpUF WTKO0TGvqTNZYyAGHEajHuwEugZ96ZLnhHPTBKw3CDo3cEfOpGpWvi+h8twalDySDPT0 p2YE+2gW8GRhsDn6SD2OA3ZRJ7BscRszlHmTs8cfRKSNNzDQiy6gJwggr66Tv788Z3Qc 4YdARlpH3207j2H0s6PZ7oDnQfpvPkSJdj4uPY7k7gBsK0sp9CZmNwHM6h9VtgM/pZWz C1ew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=rhybfzuGjA9IXalKlmn62EtLiE9B87lqvq3xGzEjrOI=; b=EDPWty9h8jTQ9D+6Hb8sKFVCedcRJHTspQiHuTRp5ktX5N79/ui7KlgSCrr2su9/YL kVvNsVIYDLlpWfTomBtS50oo69dnKopD9/VCeqsnWoao/iWerER2NPeTic7Jk9grSlRN NZMcworTaVSHpNkBZgldW/8CIphidCEM3OKijj8rH5CoXlI6YR6lQGVkSTybCzwxzGR/ mIYJR2cEh2aTpHwOe5SKZYesCa79BlXqcmUzVJP9BD9XL/KoUtzJ9eC9o6jXMVG+wN9S KZArDYmOIfiPgYP/QUmOueQIi6WA5tmCoaemB2lUfAL9CzX2mlOVc5WRttocFWQduAEl ONpw== X-Gm-Message-State: ALKqPwcAgZbGNTHepGXcFC2H+BSNiWam5veOhhEVN4SCPf+U1ggSLhFk 1i0XSnu1gzQI1bBs/j95znDsFZaFz4d5dFMfi/Y= X-Google-Smtp-Source: AB8JxZrky9lAmpO9SUnxHeu13kx3MQBNGT4AxyI1M1NsDYcEqkU+liz+ErfJYqN1ovLsqAOGitse7TXTJuXEJkPT5xg= X-Received: by 2002:a9d:3e07:: with SMTP id a7-v6mr13704799otd.150.1526933772656; Mon, 21 May 2018 13:16:12 -0700 (PDT) MIME-Version: 1.0 Sender: kmacybsd@gmail.com Received: by 2002:a9d:3f0:0:0:0:0:0 with HTTP; Mon, 21 May 2018 13:16:12 -0700 (PDT) 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> From: "K. Macy" Date: Mon, 21 May 2018 13:16:12 -0700 X-Google-Sender-Auth: jGQH2dskTTygnTaOFv0T5HnU3Lc Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: sgk@troutmask.apl.washington.edu Cc: Rozhuk Ivan , Oliver Pinter , Niclas Zeising , Warner Losh , FreeBSD X11 mailing list , Current FreeBSD Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2018 20:16:14 -0000 On Mon, May 21, 2018 at 10:07 AM, Steve Kargl wrote: > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: >> On Sun, 20 May 2018 21:10:28 +0200 >> Oliver Pinter wrote: >> >> > > One of the reasons for the deprecation and removal of the drm2 bits >> > > is that they prevent us from automatically loading the >> > > drm-next/stable-kmod kernel modules, since the two collide. >> > > Regards >> > >> > >> > Then it wold be better to resolve this problem, rather then removing a >> > working solution. What's about module versioning what in other cases >> > works? >> > >> >> May be just move old drm2 to ports? > > 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. > Having it as a port puts the burden squarely on those using it and not on the majority who are running hardware from this decade. -M