From owner-freebsd-current@freebsd.org Sun Sep 3 19:19:24 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07D35E1A62E; Sun, 3 Sep 2017 19:19:24 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (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 C0D7375519; Sun, 3 Sep 2017 19:19:23 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-it0-x22f.google.com with SMTP id c13so10489012itb.0; Sun, 03 Sep 2017 12:19:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=msNQYTKY4ujbE+jwWPbaNgw4jChew9FuUHAko8MnNBk=; b=RHgPdBGUszZm+xT3LzqSLDlV7aBHOTOa6XM85+pFj/r8cf9Diwsm48GkaLDeNU2OLq t/ZNU+xVbHLjysUcOXnfyiSS0AHJuCJDFCU4pvUbGcKtU052pTaVp9YpxD50cxY02FbI 22XrcjQkqQ1H742f1gY0tuUB6PHc6J5SG0aH/GB+l1asXjL6ihyc0RYva2LvJsV7Xx0e 6Ia8St2S7vz4sIEGay03Ml0Hx0ejeE9IwMV4xBHbwhqGOUEy2V0U5d9lr/LA4rccgps/ Nrp0yQ5ue6F9tC8nCrv2rOe5bu66vYTCWDybixp1e3S8WyGq+s3Q+lE9gwJe/BHqZtmK bAkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=msNQYTKY4ujbE+jwWPbaNgw4jChew9FuUHAko8MnNBk=; b=CCaYlt73ubS9uYg+KbnmROKNYf4cmxTQswORIz9OnX4VjPZMTvyzTt3ERUzZqImnu4 ExQ7JhVrS6hSdMe0R+K9J65cC5UwhrSd788LQwaeLaX6j64v65vfcvJCRWUwQiIupSwP 4fa+f3bibyRF984gmZMP01fJA0gySP1mD3wHYdvhx63sMdlj4cW3OdsOS5I7g2C2jLvv XUufN2+0VRISbuTtMdwHYgPqvnN+K7CPV99WsQ+UGNehijzVSDh1ANyplWz1+aEsvPVq ibXu1Snm0VDcBegM5GxtWUk8hET3MvWf5Dhx07su8N3I1QVcGpJoq+n763YdsdRqZ1p/ yUwg== X-Gm-Message-State: AHPjjUizHVBsIuVC+TlkQPvgAaiiZQwYT471ep+S431KxjLGU5Z9R2FD Id4mQUH5CwpbAlxZ X-Google-Smtp-Source: ADKCNb7uJ5LSBGrjzgdEZ/v6cFZnnpFAqyfhZdbWwDR/UdmtQFZYUdzfpKuePFjWk7aoik0+pS+ErQ== X-Received: by 10.36.144.195 with SMTP id x186mr5169309itd.5.1504466362750; Sun, 03 Sep 2017 12:19:22 -0700 (PDT) Received: from bish ([75.98.19.132]) by smtp.gmail.com with ESMTPSA id b66sm2587447itb.0.2017.09.03.12.19.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 Sep 2017 12:19:21 -0700 (PDT) Sender: Mark Johnston Date: Sun, 3 Sep 2017 12:19:09 -0700 From: Mark Johnston To: Johannes M Dieterich Cc: freebsd-current@freebsd.org, freebsd-x11@freebsd.org Subject: Re: [RFC] future of drm1 in base Message-ID: <20170903191908.GA1259@bish> References: <20170902220257.6667280e@manray.ogolem.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170902220257.6667280e@manray.ogolem.org> User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 03 Sep 2017 19:19:24 -0000 On Sat, Sep 02, 2017 at 10:02:57PM -0400, Johannes M Dieterich wrote: > Dear current/x11, > > please CC me on responses. > > I am writing you on behalf of the FreeBSDDesktop team concerning the > future of drm1 in base. > > drm1 in base supports the following GPUs: > * 3dfx Banshee/Voodoo3+ (tdfx) > * ATI Rage 128 (r128) > * ATI Rage Pro (mach64) > * Matrox G200/G400 (mga) > * Savage3D/MX/IX, Savage4, SuperSavage, Twister, ProSavage[DDR] (savage) > * SIS 300/630/540 and XGI V3XE/V5/V8 (sis) > * VIA Unichrome / Pro (via) > > Since their original introduction up to 2010 these drivers have mostly > been maintained as part of larger cleanups. The newest hardware drm1 > supports dates from 2004, if I am not mistaken, and most of the > hardware is AGP-based. > > With the introduction of graphics/drm-next-kmod which brings its own > drm.ko following the Linux notation, we are facing collisions between > these old drivers' drm.ko and the newer one. I don't think this is a real problem. The reason one currently needs to manually load the drm-next drm.ko (rather than just kldloading a driver and having it pick up the right drm.ko automatically) is that our drm.ko defines the same module ("drmn") as drm2.ko in the base system. So upon attempting to load a drm-next driver, the kernel uses the linker hints to load drm2.ko, which is incorrect. However, this can be addressed by simply bumping the drmn version in the port and modifying the drivers accordingly. I've submitted a 4-line PR which does exactly that. After that change, we can modify the pkg-message to omit drm.ko from the kld_list value. As a result, the name of our DRM module doesn't matter since users don't need to specify it, so the collision with drm1 isn't a problem. > We would like to hear if anybody still runs CURRENT on machines housing > the above GPUs and relies on drm1. > > If there are still a significant number of people running CURRENT on > this hardware in production, we would be willing to make a > graphics/drm-legacy-kmod port. With the PR I mentioned above, I think it's a non-issue to keep drm1 in the base system. Since there appear to be at least some users of those drivers, I really think it would be preferable to avoid removing them unless it's absolutely necessary.