From owner-freebsd-arch@freebsd.org Fri Feb 15 10:07:38 2019 Return-Path: Delivered-To: freebsd-arch@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 40ECB14D401E for ; Fri, 15 Feb 2019 10:07:38 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (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 2C7E989155 for ; Fri, 15 Feb 2019 10:07:37 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr1-x434.google.com with SMTP id o17so9711440wrw.3 for ; Fri, 15 Feb 2019 02:07:37 -0800 (PST) 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=QUlvORHZydHZPUFpRZbts0JjngD0zeBT6CFJc+AY924=; b=D0clj+oEeIyduVcjRv08rM52bnCxlNUJeBwson8wBsRF0OTp6aLX2rfcBCZBNBt33F gjj5l+/cKyDUz2lZ1w53Dt+r/vWcmESZLAg7A3U+GfYTc8A8z8naa9ndUtytO7hPwKOH +Pfyx1S8ou92hFE4OGmZe7C2UkTal0YXKgbVsS8dcRmbd4mbD6CTo5QU8wOKylk+DzTx W0Vwimzscdxqz4nkFrbH1WvGC8Sk3N/fhWHrxI6KW5uVBkT+xh23Q/9xy0CexnK1J5De Th+hCBfG6UQe5psAQkH9oELK1+5m6/gdjM5xqCs+n6N5LiwHJnfrxwHteS6RRBZ6FjS4 TxYw== 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=QUlvORHZydHZPUFpRZbts0JjngD0zeBT6CFJc+AY924=; b=E1wtsiEu4J1JdwQHhvu6rCqVtzFCHZh//hOZ7PffC1UZvJ6xScAbwKNseKmy8mENwc ZpuL/qMwqf4/kcCqUsv3a2x3dxaC+3gmqdj27V3ELukNAh23ts23nyopuaqxe8Tz/x+2 xAJiYDagRKKqPhlnQmkNCm6o/FD0qptBQXsFhKFe99fhBc8IXcadKR7ECLK927hBqsD2 3GdiyTD5q4j/pEDm+AkTa/VmmpBBtrvoHNRImWb6kGN8L0EPcoDYe0jaV6B4VNadyt7o lZP+QXUB2JWBCAVJv3hsEV7rdWNs4spf8NZC2OCRyZ6ivBPo8iO7wDhKi+gZhfsqnKrW luBA== X-Gm-Message-State: AHQUAuaq0mSAtptqAMsZnqZ945aZXrara8617tpdP7CD9Sr9qxpXZ+8G YszAmE8A4Hhu1IEWN0Z4thkIbgyNus5z3nq2OawYhg== X-Google-Smtp-Source: AHgI3IZcHSB1IKM791ALDlxOyJ0/AGf9p387TDxrV+40kzK1iKNH1QlIIxzT9zmqADu9s73oJTv4+XFSQyJHw22GCJ8= X-Received: by 2002:adf:a147:: with SMTP id r7mr5982034wrr.5.1550225254809; Fri, 15 Feb 2019 02:07:34 -0800 (PST) MIME-Version: 1.0 References: <20190214180101.GB67712@troutmask.apl.washington.edu> <20190214182419.GA67872@troutmask.apl.washington.edu> <20190214190244.GA68143@troutmask.apl.washington.edu> <20190214191739.GA68371@troutmask.apl.washington.edu> <20190214225810.kmfxzeuvr7t7gget@smtp.freebsd.org> <20190214233000.GA2752@troutmask.apl.washington.edu> <3b0ba403-ff96-8c94-6d98-40165473d1f3@gmail.com> In-Reply-To: From: Johannes Lundberg Date: Fri, 15 Feb 2019 10:07:23 +0000 Message-ID: Subject: Re: "DRM removal soon" is premature To: Oliver Pinter Cc: "freebsd-arch@freebsd.org" X-Rspamd-Queue-Id: 2C7E989155 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=D0clj+oE; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of johalun0@gmail.com designates 2a00:1450:4864:20::434 as permitted sender) smtp.mailfrom=johalun0@gmail.com X-Spamd-Result: default: False [-6.80 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.98)[-0.978,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[4.3.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.81)[ip: (-9.71), ipnet: 2a00:1450::/32(-2.30), asn: 15169(-1.99), country: US(-0.07)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2019 10:07:38 -0000 On Fri, Feb 15, 2019 at 09:44 Oliver Pinter wrote: > > > On Friday, February 15, 2019, Johannes Lundberg > wrote: > >> >> On 2/14/19 11:30 PM, Steve Kargl wrote: >> > On Thu, Feb 14, 2019 at 02:58:10PM -0800, Ben Widawsky wrote: >> >> Not to pile on unnecessarily here, but I think the fundamental issue >> is that >> >> there is nobody who wants to maintain the in-tree DRM, and removal is >> likely a >> >> better option to half-assed maintenance. I'd imagine there'd be a >> different >> >> discussion if several developers were clamoring to keep this driver >> well >> >> maintained in the tree. >> >> >> > Unhooking a driver from the build, so that it cannot expose >> > a change that breaks said driver is certainly a way to >> > ensure the driver is not maintained. >> > >> > Wasted a weekend trying to find and attempting to fix the >> > damage caused by a change in src/sys to the drm-legacy-kmod >> > port. You know, the port that was promised as part of the >> > drm2 removal. I would have spent this weekend testing >> > changes to cexp, cexpf, the soon-to-be-submitted cexpl, >> > ccosh, ccoshf, and the soon-to-be-submitted ccoshl. That's >> > all on hold now as I'm not sure when I'll be able to carve >> > out time for testing. >> >> This happens all time for me with virtualbox-kmod as well in current. >> Changes to src breaks certain (kmod) ports and there's always a delay >> until they are fixed. This is life in -CURRENT. I accept this and don't >> go bitching to virtualbox-kmod maintainers about it. Your usage is an >> edge case so naturally there will be a longer delay before breakage is >> noticed, until we can get automated CI up and running (even so, there >> will be a delay). >> >> With graphics, there's a software fallback (vesa/scfb), virtualbox has >> no such option. > > > bhyve, pure qumu? > Yes bhyve is awesome and I use it mostly. Don=E2=80=99t get me wrong, I=E2= =80=99m not complaining about breakage, mearly stating the fact that that=E2=80=99s lif= e in -current. VBox kmods are usually fixed quickly, I think the biggest delay is the time it takes to build all the packages. Maybe a fast lane for critical kmod ports that can be upgraded/rebuilt isolated from the rest would be something? > >> >> For stable usage, there are -RELEASE options. >> >> >> >> _______________________________________________ >> freebsd-arch@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arch >> To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" >> >