From owner-freebsd-current@freebsd.org Tue May 22 22:12:43 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 ADA60EB167B for ; Tue, 22 May 2018 22:12:43 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 083046B73C; Tue, 22 May 2018 22:12:42 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w4MMCdd1031938; Tue, 22 May 2018 15:12:39 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w4MMCdA9031937; Tue, 22 May 2018 15:12:39 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: To: "K. Macy" Date: Tue, 22 May 2018 15:12:39 -0700 (PDT) CC: "A. Wilcox" , FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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: Tue, 22 May 2018 22:12:43 -0000 > > > > > > it makes me giggle that people still think non-amd64 is "legacy". > > > > i386 is alive and well - new chips are being fabbed based on the 586 > > design with pci-e slots; not to mention things like the Talos and > > AmigaOne for PowerPC. Yes, some how we need to shake off the idea that all the world is going to be 64 bit, and stop talking about EOL for 32 bit x86, IMHO that would be a serious mistake. For one any VM that does not need >4G of address space is a waste to run in 64 bit mode. > DRM2 doesn't support anything later than mid-Haswell. The chips in > question all pre-date 2007. Users of low-volume hardware on chips from Um, haswell announced in 2011, started shipping in mid 2013, and last product started to ship in 2015, so if "mid-haswell" is the supported chip arrena that would be pre date 2012? Also as the Moore's law curve flattens expect the life of these older, but not so old, machines to live quiet some time. I believe we are talking sandy bridge and earlier? If that is corret Sandy bridge is still a very viable system. > that period are welcome to continue to sustain themselves on the drm2 > port just as the other 95+% of the user base will use what is now > referred to as drm-next. Even by powerpc maintainers' admission DRM2 > also only barely works there. I've promised Justin that I'll make > drm-next work on Talos once POWER9 support is solid enough. I think the original RFC has been answer, yes there are people still using DRM2, and they wish to continue to use it into the 12.x time frame. Lets find a technically agreeable solution to that, and move forward. I am concerned about just disabling the compile on amd64, that typically leads to bit rot of the i386 code. I am concerned about just shoving it out to ports, as that makes it rot even faster. I am still very concerned that our in base i9xx code is like 4 years old and everyone is told to go to kmod-next from ports as well. No, I do not have a solution, but I have not tried hard to find one. I am sure if we try hard to find one it can be done. Regards, -- Rod Grimes rgrimes@freebsd.org