From owner-freebsd-x11@freebsd.org Mon Apr 13 07:11:46 2020 Return-Path: Delivered-To: freebsd-x11@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 18AC02B5855 for ; Mon, 13 Apr 2020 07:11:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4910D12FLLz4CXy for ; Mon, 13 Apr 2020 07:11:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.nyi.freebsd.org (Postfix) id 4B2742B5854; Mon, 13 Apr 2020 07:11:45 +0000 (UTC) Delivered-To: x11@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 49A6E2B5853 for ; Mon, 13 Apr 2020 07:11:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4910D00hM2z4CXt for ; Mon, 13 Apr 2020 07:11:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x735.google.com with SMTP id x66so8536236qkd.9 for ; Mon, 13 Apr 2020 00:11:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=54zMgpcT56/drkGDYltfh1jIt1XGogNUNBmUN2yWPzk=; b=exvM8tWyZjtqhf6jBA1JQ/gBxIyfSJ+Ux2UT4NzHDeOJDldOnu9d+fux5qDCiGp6JO O4e1NkC0ISGFJFLRfMvsU85udBUJdD25H4fz+FtUsuGMtXM3W7Dax2ykdwhlOA5Jew0D +SEkeHA2VwM9LgOEDkheEcukbX4qSMLYX6MS1+TqwQvS+IiWIIYph2hx/2za1IhJOKrE iUmOM+s8xXT7ElqNh3q6liRA8B2HGBi1h5z/qy8/Bk/KhfVCGvygpLbZoY7n+1+s0HLd wx6In+ErZHt1oP11Nq5V/mVFcCHHw72/dp1FzHdEhsHv4JepQijzAPqnqlxBxwEGtYmP 7O6g== 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=54zMgpcT56/drkGDYltfh1jIt1XGogNUNBmUN2yWPzk=; b=Y9hE6fEILd3u1gcEjbybfsEZdmLxDZ5qjG0ClaXg9XWA1jb5TDPIuI8QOTNhSWRkXd 4NLQJ06nkj+4WFM+YzIdgwWsehKQuCiwccJ8amHX2sE70PpzPHyaWb2He5xKK0XSe3Pq fMz6m2Vg3V7gWoMeX4YR6P37oPADP5Q/CRfOsbBIor/0bZul970COb2JCVK7YIJ3xCqq ltbkvrDuD8olWGi8hgherTft3ydaFQ52/kLiHIWPJzfT3cAJL8YkkHgS39EwUTSNRlFD hfT9jGK5np9Cs8XG03Y9V3fCzgUOQ/2fojQdnvHfEj94qFN4H0bC1IuxW+0cw7x6aoK9 L0zw== X-Gm-Message-State: AGi0Puab9ptJYJvch8ZsPVyFJGueHd4o9KYfpiXP1HohEq5Jn6jE2rYR 9cP9Yy1EitJ+5mEmgfa8C+OYomDpGmH7bXwfbZ1mQA== X-Google-Smtp-Source: APiQypIohe4upmYpz9CuPd2Rt3MfZF0IKjW8c1SzAMiGnGV2b1LNYAl2Q45eGON8hNjKJeSbD0XRbBbO3M5quMGAuQU= X-Received: by 2002:a37:ac6:: with SMTP id 189mr1035635qkk.60.1586761902893; Mon, 13 Apr 2020 00:11:42 -0700 (PDT) MIME-Version: 1.0 References: <3049612.rJTJeGpjCJ@saskatoon.bionicmutton.org> <20200410001102.GB23747@lonesome.com> <4e3bf6be-aecf-7c62-df98-1cc4b01b8db9@gmail.com> <43f83193-e495-2bf2-f85d-91aa0b36c1a0@gmail.com> <0e205fe8-fbc6-5d91-99b0-1bd4870b8a5d@gmail.com> <536A0D50-4119-4C28-9202-28622152B203@freebsd.org> <20200413052406.GA90880@FreeBSD.org> In-Reply-To: <20200413052406.GA90880@FreeBSD.org> From: Warner Losh Date: Mon, 13 Apr 2020 01:11:30 -0600 Message-ID: Subject: Re: Ars Technica article To: Alexey Dokuchaev Cc: Niclas Zeising , FreeBSD X11 X-Rspamd-Queue-Id: 4910D00hM2z4CXt X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=exvM8tWy; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::735) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-4.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[x11@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[5.3.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.00)[ip: (-9.20), ipnet: 2607:f8b0::/32(-0.33), asn: 15169(-0.43), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Mon, 13 Apr 2020 07:11:46 -0000 On Sun, Apr 12, 2020, 11:24 PM Alexey Dokuchaev wrote: > [ setting CC to a more appropriate -x11@ list ] > > On Sat, Apr 11, 2020 at 12:43:00AM +0000, Niclas Zeising wrote: > > ... > > Short answer, because I'm on my phone... You shouldn't use drm-legacy- > > kmod, it is on life support. > > Well, that's funny, considering that for many people, it is the only > DRM port that actually works. > To be blunt: drm-legacy-kmod's days are numbered. It's irrelevant that it's the only one that "works." It's a distraction to keeping drm-kmod working on newer, more relevant hardware. It's unfortunate that some older hardware has stopped working with the newer code, but much of that is due to upstream pressures. xf86-video-ati-legacy is one symptom of that problem: upstream has moved on and we simply do not have the resources to band-aide together support for the old hardware forever. Let me be blunt: it's my goal to remove drm-legacy-kmod as quickly as possible. It's a big drag on the graphics team's time and has low ROI for the project. Given the challenges we have today, I see no other sane course of action. People that have broken hardware need to step up and provide fixes for that old hardware in the drm-kmod context, or buy new hardware. That's the harsh reality we have with the people we have working in this area. > The drm-legacy-kmod radeonkms.ko module requires xf86-video-ati-legacy > > to work in menu cases, > > menu == many? Where is this requirement documented? Many people had reported having to use `graphics/drm-legacy-kmod' ('cause, well, nothing > else works) and radeonkms.ko together with `x11-drivers/xf86-video-ati', > particularly, in PR 237642* about the invisible mouse pointer My reading of that PR is why xf86-video-ati-legacy was created. People upgraded and had to revert to the old version of xf86-video-ati to get it working and reported that xf86-video-ati-legacy worked. And that's the problem: we can't keep growing new legacy things. The cards reported were from 2008. That's over a decade old. Given the choice between supporting such old hardware, and newer hardware, the new hardware wins. It's an unfortunate reality, but honestly, upstream broke the support of the older cards. There's been no patches against the latest version of upstream, nor any work to make the drm-kmod drivers work with the older hardware. The older hardware isn't readily available, and the ROI for working on it is really really low compared to other thigns that could be done. > and that has been broken since the update of xorg-server, with no one > > stepping up to test my patches for it. > > Wrong: both pfg@ and me did test those patches, as well as other people > who reported it on -x11@ list, with sad results unfortunately. :-( > So Niclas tried to do something to make it work for you, but it didn't work. He's already gone the extra mile for this old hardware, and it's unfortunate that it no longer works. I know you're frustrated. I know you're looking for someone to blame. That person isn't Niclas. It's xorg upstream which has broken support for these older cards in some way with the old DRM drivers. They no longer support the vintage of driver we have in drm-legacy-kmod. We're lucky it works as well as it does, honestly. > I'm using modesetting across three different Intel GPUs without seeing > > any issues. > > Yes, lots of people apparently are happier with X11 server's built-in > "modesetting" driver rather than traditional xf86-video-*, but doesn't > modesetting drivers lack some/any 3D acceleration? I don't see this > documented on wiki.freebsd.org/Graphics (and modesetting driver is only > mentioned in the Intel section). The modesetting driver is working with my kaby lake laptop. I'm quite happy that I can get a modern laptop and have things work. Given the choice between really old hardware and current hardware, current hardware has to win when there's a resource shortage. And we have a huge resource shortage in this part of the stack: the drm-kmod maintainer's job shifted so he's had to resign from that role. We have nobody to even update to newer Linux driver versions (though we might have a promising person in the wings). There's literally nobody that has the time, the hardware, the docs and the expertise to help with this older video hardware (at least as evidence of it's remaining broken for a long, long time). Until that person shows up, you will unfortunately be out of luck. Again, I hate to be harsh, but supporting this old gear is getting in the way of supporting other things. It's becoming clear to me, at least, that it's time to cut our losses on anything over a decade old. It's time we're clear about it. We had our hand forced for nvidia cards when we upgraded to 1.20 because the older cards binary driver no longer works with 1.20 and nvidia has said they can't support them any more. We, sadly, must do the same and so drm-legacy-kmod's days are severely numbered because it's become a huge time sink with very little benefit. Warner ./danfe > > *) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237642 > _______________________________________________ > 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" >