From owner-freebsd-current@freebsd.org Thu May 31 17:52:28 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 7EB4DF7A448 for ; Thu, 31 May 2018 17:52:28 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::229]) (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 EB6387557B; Thu, 31 May 2018 17:52:27 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x229.google.com with SMTP id i14-v6so33822551wre.2; Thu, 31 May 2018 10:52:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NcXvEFMubZzXuHlE2SlhPL+G0YzX3vkOMldAYb+vd6w=; b=ISbKFrwDfKbcYAXGP7w44/8xtcFzGarfbi2itQRKGe1cNX33Z4kD7Z7IdHfem9dgg0 9hCkAC43AweuADRISfTTlWurp+xyw06imU2kCjoewhedJGb5uPkzI1VuIri2cLZ2h8Wb r9Y4XQ523FMQRhh+eR+cJWzBtcSH7vKgpmy23dkh5HVrc0FSb+UN+ZtInBBF9iOgNBYx +vjqAxC1BiuAR1YHKXwCQ7wbE0R3l8ZieAAoYpdQyphW/cElOWSii+6cTQdJ3MrD0RXr XYRHyMWJdtDBGOPqyQByV5wF8MTXywc0uFWwvOhVfK/jlAjwqaMzJ/45V3fCIwk2QOqj xaUw== 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=NcXvEFMubZzXuHlE2SlhPL+G0YzX3vkOMldAYb+vd6w=; b=fE7T+WzJEuXiZtd5bVf0ZntbwONuPCdWX82aiLT1XJFH07/ybgSmFXUdTsv0bcrLGT 75ptacPdcOOzoSuGy5uLjASyuJqAoSphvxUFxd/YejpcO6lqac4ewFpG8No+ygMhB2yx xbidbbYpRiEvqVY9eqC9iNgoZC9D1r682W08AmjPKKD/0mGl7hkcSKr6Uv3R9D8z5DUi Pc9Q+pI5y4xToqvoKIepTZz7El+5eehIiUZtcD5B65cw04jgssUuqayWdp47G5FWQDEz RtVksiKTAGZUaOT9115wa+aC1mSE4xD102tNl+dE42b0JAuiTLgbn7eFHyqrjY9gcjrV w75g== X-Gm-Message-State: ALKqPwc37OpWOnDlszZf4UOE2AUC1yR6+WJK8DDT0Zqv3yUNVc7xa2aB 609xeo0PSq5S/mSdPDxIeoSiTXP2QnnngKcVrx4= X-Google-Smtp-Source: ADUXVKKFqFWb8oZxlkyeAt5q7Jaqu3ZxBtQACerqoJRM5b5sm7jb6gXvvgsVTLzNKCKpog1VoUnNlSyz2xE2wKgxISw= X-Received: by 2002:adf:a0b9:: with SMTP id m54-v6mr5951084wrm.76.1527789146836; Thu, 31 May 2018 10:52:26 -0700 (PDT) MIME-Version: 1.0 References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> In-Reply-To: From: Johannes Lundberg Date: Thu, 31 May 2018 18:51:50 +0100 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: jmaloney@ixsystems.com Cc: deischen@freebsd.org, Konstantin Belousov , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 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: Thu, 31 May 2018 17:52:28 -0000 On Thu, May 31, 2018 at 4:34 PM Joe Maloney wrote: > I personally wish that more drivers, and firmware were separated from > base. > > I'm not a committer but as I understand there's not pre-commit integration tests.. If one had that, plus that it would test build kmod ports against the pre-commit state of head as well, then maybe this would work. > For example wireless firmware: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169433 > > That was a ticket which I chimed in on about a firmware I needed to make > my wireless adapter work. I went through numerous efforts on IRC, and > elsewhere to try to bring attention that ticket in order to attempt to get > that firmware backported for several 10.x releases in a row without > success. The firmware worked perfectly fine in PC-BSD where it was cherry > picked for numerous 10.x releases. > > Technically since I was using PC-BSD, and was a committer for that project > I had no real dire need to reach out to FreeBSD about the issue. I was > simply trying to help anyone else who might be encountering the same issue > trying to use stock FreeBSD because it was a simple backport. If my effort > had turned out to be more fruitful I would have spent more time pursuing > tickets, diffs, or whatever to get more things back-ported when I found > them. I am not sure where the breakdown was which did not allow that to > happen. Anyways I don't want to bikeshed, or anything but I just wanted to > point out how I think having more drivers, and firmware in ports could be > helpful to enhance compatibility for end users. > > Having a separate port for legacy drm could definitely make things easier > to providing installation options for end users, and automating the post > install action chosen in TrueOS, GhostBSD, and future derivative projects > tailored for the desktop use case. For example for TrueOS we boot the > installer in failsafe mode with either VESA, or SCFB depending on whether > or not BIOS, or EFI is booted. Then we could simply make a checkbox for > legacy intel, or skylake + to install the correct package then the module > path for either driver can more or less remain the same. Eventually with > something like devmatch maybe that can even be fully automatic. > > Joe Maloney > > On Thu, May 31, 2018 at 10:23 AM, Daniel Eischen > wrote: > >> On Thu, 31 May 2018, Konstantin Belousov wrote: >> >> On Thu, May 31, 2018 at 08:34:44AM +0100, Johannes Lundberg wrote: >>> >>> We're not replacing anything. We are moving the older drm1 and drm2 from >>>> kernel to ports to make it easier for the majority of the users to load >>>> the >>>> correct driver without conflicts. >>>> >>> >>> You do understand that you increase your maintainence load by this move. >>> dev/drm and dev/drm2 use KPIs which cannot be kept stable even in stable >>> branches, so you will need to chase these updates. >>> >> >> I agree. One argument previously made was that it's easier >> to maintain in ports. One data point from me - I rarely >> update my ports, I update my OS much more frequently. In >> fact, some times my ports get so out of date I just >> (take off and) nuke /usr/local (from orbit, it's the only >> way to be sure). >> >> Also, are we trying to solve a problem by moving drm[2] to >> ports that won't be a problem when base is pkg'ized? If >> drm[2] is a package unto itself, then you don't have this >> problem of ports conflicting with it, at least not so >> much. You can either not install the base drm[2] package >> or deinstall it to make way for a conflicting port. Once >> drm[2] is pkg rm'd, it's not going to be reinstalled >> again when you update the base OS. >> >> And don't we have the same problem with sendmail and a >> few other base services? >> >> -- >> DE >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org >> " >> > >