From owner-freebsd-x11@freebsd.org Thu Feb 28 22:16:58 2019 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 8B065151BD12; Thu, 28 Feb 2019 22:16:58 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1ADA88C806; Thu, 28 Feb 2019 22:16:58 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-io1-xd2d.google.com with SMTP id e186so18031763ioa.0; Thu, 28 Feb 2019 14:16:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=qMwTbwWBdshWjzxXelIHmE/LgWx0izT8ssctmBscs9o=; b=bXi8WVTHz8BggT9l1hwsN5++HTnopsmha04UDU0nkihzZ5oRvpSn69mHDTC0HvaE9g leMPoC+GuIl8KJ7xmLXAk+5jNOnwlWhfd/3ItLOyyQYwyDfTonRWoOGqMkcGhR81v8jd lLiF6Q8iOTvPyXaTqPXQWaHWDh7P8tzv/9bIr1lfk83oyvyLT9bwceD8B0NdWTo/bFea UmkIp1f2zBR3nqfCQcwJDUIw5nHnh5RvTAtoPJ8CpbWvLuVcDS4SDbmJtSyRKEVA//2N IThlFsSxZAv3GW3VHStAaztJ8GSCmGMisaS1/1K47lxMpNEwfn2/JYsZxeTpAs4S4Oon r9fg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=qMwTbwWBdshWjzxXelIHmE/LgWx0izT8ssctmBscs9o=; b=GUuMlZ8cnmS1X6Dn13eRL/UUam0n3YRQk0mjSl0bfboO4x4cFl9X+5TykK3YRP+WxX xZvH8eOklCV+bta9R+cWrdRy4z74HXCd8iQLB3vlXyAfXrGslUX3NVOT7bq3L1vgQDvJ 8G4lDn3wl6MsFiXQQHR+l+fyIkpHIlP7lZmEbqpPBDymKFQF1M32DBirT+K5CPOYXzIk EQSHd3KTOoB8XKGsMDSUM87XMRYKpFTcy9TqGu1IeBs0/K/WZObRK5A8v9slYee24RK/ 8qY5eqaSy+ZrzOYCkYJYcPs9yhu2uuQ5556fLqXerKIoy9+YG0tobozvQ4DM5obbLBrD 9e2Q== X-Gm-Message-State: APjAAAUev3l/spuz7ANLTX9LRuqNexsXXGQ6SwQXzk/zKDcitpnPDQ0t D055nZ5U7tnngk48JcMHlN0FH+5p7Ps= X-Google-Smtp-Source: APXvYqw8InZRuwJzZf9lsv6B298rxIkE20/gUFnKRyGMzrV7uwru7ypwbucjhTB6JC35DDx2qRnlpw== X-Received: by 2002:a6b:b5c7:: with SMTP id e190mr1027963iof.26.1551392216673; Thu, 28 Feb 2019 14:16:56 -0800 (PST) Received: from titan.knownspace (173-25-245-129.client.mchsi.com. [173.25.245.129]) by smtp.gmail.com with ESMTPSA id 203sm3475601itv.6.2019.02.28.14.16.55 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 28 Feb 2019 14:16:56 -0800 (PST) Date: Thu, 28 Feb 2019 16:15:24 -0600 From: Justin Hibbits To: John Baldwin Cc: sgk@troutmask.apl.washington.edu, Cy Schubert , Yoshihiro Ota , "freebsd-arch@freebsd.org" , FreeBSD X11 mailing list , greg@unrelenting.technology Subject: Re: DRM removal soon Message-ID: <20190228161524.1449770b@titan.knownspace> In-Reply-To: <4f374050-6ae2-1d39-f148-a4e588838f8d@FreeBSD.org> References: <20190228194929.GA18747@troutmask.apl.washington.edu> <201902282034.x1SKYWMi006337@slippy.cwsent.com> <20190228210635.GA31257@troutmask.apl.washington.edu> <4f374050-6ae2-1d39-f148-a4e588838f8d@FreeBSD.org> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; powerpc64-portbld-freebsd13.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 1ADA88C806 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.983,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2019 22:16:58 -0000 On Thu, 28 Feb 2019 13:54:39 -0800 John Baldwin wrote: > On 2/28/19 1:06 PM, Steve Kargl wrote: > > I suppose it is the bane of those of who cannot afford > > new hardware every 2 or 3 years. > > This is a bit of an exaggeration. I just replaced my previous > laptop (Thinkpad x220 from 2011 that I bought used in probably > 2013 or so) with a Lenovo X1 from this year (which requires > drm-kmod-current). That's a span of 5 years. Note that > the in-tree drm2 drivers won't work on laptops made since > around 2015 or so. > > > I haven't looked at what the drm-fbsd11.2-kmod or 12.0 mean. I > > assume that these are the ports for 11-stable and 12-stable, and I > > assume that these work on those specific stable branches. If that > > is the case, then there is no support needed by graphics teams > > unless a src committer merges somethings from -current that breaks > > stability. If the MFC is a security fix, then the graphics teams > > may need to asked about helping troubleshoot the 11.2 and 12.0 > > kmods; otherwise, then MFC should not happen if it breaks > > stability. Or, perhaps, I have a s different definition of > > 'stable. > > I think one of the issues that isn't clear is that there are other > ports involved than just the drm-kmod ports. The various x11 driver > ports (xf86-video-*) use the DRM APIs. Newer versions of those > packages only work with newer versions of DRM, and newer versions of > other things like KDE depend on newer versions of X libraries, etc. > It actually ends up being a far larger ball of mud at the bottom of > the hill than just the drm-kmod ports in terms of the dependencies > affected by keeping older versions of DRM around. > > In your case, I am hopeful that using an amd64 kernel with an i386 > chroot is going to give you an overall better experience by giving > you more stable kernel support as well as the ability to test libm > for both i386 and amd64 on the same machine. > (Picking the latest message in the thread to respond to, nothing more): I would like to point out that for the time being drm-legacy-kmod and the associated xf86-video-ati-legacy driver, is required for graphics on some powerpc systems (notably, my AmigaOne X5000). Matt Macy did some work to get drm-current-kmod working on the POWER9, but since his changes touch many parts of the kernel, not just powerpc-specific sections, it needs a pretty good review. This will be needed for anything to work correctly on the POWER9 TALOS systems. I don't recall if his work is only in his POWER9BSD repository or if he's submitted any reviews on phabricator for it yet. If not, I will do so when I'm able to test on my own hardware. tl;dr: More than i386 is impacted by drm-legacy-kmod, and I'm sure everybody wants to get off the legacy kmod to ease the load on the graphics team, but it will take work by the interested parties to make this happen. - Justin