From owner-freebsd-x11@freebsd.org Thu Mar 23 22:45:05 2017 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6757BD1BE71 for ; Thu, 23 Mar 2017 22:45:05 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dnvrco-oedge-vip.email.rr.com", Issuer "dnvrco-oedge-vip.email.rr.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 43BC71C71 for ; Thu, 23 Mar 2017 22:45:04 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:31316] helo=localhost) by dnvrco-omsmta02 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 18/25-29375-93E44D85; Thu, 23 Mar 2017 22:37:45 +0000 Date: Thu, 23 Mar 2017 22:35:30 +0000 Message-ID: <18.25.29375.93E44D85@dnvrco-omsmta02> From: "Thomas Mueller" To: freebsd-x11@freebsd.org Subject: Re: Status of Intel Broadwell GPU Support?? References: <20170321182231.GG77624@rancor.immure.com> <25c5ecee-b617-a55b-c8f9-cf041b7ecf92@nomadlogic.org> <20170321201843.GH77624@rancor.immure.com> <10d5602e-8fe5-1d2c-1e07-5ca2f62ebfe0@nomadlogic.org> <20170321222823.GA79219@rancor.immure.com> <79.B5.25473.52E32D85@dnvrco-omsmta03> <20170322125003.GL3359@rancor.immure.com> <5F.72.29375.2FB73D85@dnvrco-omsmta02> <5ac76e08-6a12-76b5-0b67-7f69389eec8e@nomadlogic.org> X-RR-Connecting-IP: 107.14.64.7:25 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.23 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, 23 Mar 2017 22:45:05 -0000 > > On 03/23/17 00:38, Thomas Mueller wrote: > >> https://github.com/FreeBSDDesktop/freebsd-base-graphics > >> and used freebsd-base-graphics for both buildword and buildkernel. I'm not too > >> clear on just what that means for any future updates, though. I have been > >> hoping for the past year or more that the patches/changes included in > >> freebsd-base-graphics would get integrated into the base. I really don't know > >> if that's happened or planned to be done. Been kinda frustrating. >> Bob > > I look further and see that you need a slightly different ports tree: > > https://github.com/freebsd/freebsd-ports-graphics.git > > but I think you need to put -b xserver-next at the end of the git command (and git at the beginning). > > Then such a FreeBSD installation would have to be separate from an installation that uses regular src tree and ports tree, lest the ABI and shared libraries be out of sync. > Hrm, I think the wiki is out of date, or unclear, in regards to the separate > ports tree. As of the latest Xorg updates which brought us up to v1.18 this > is not necessarily needed. i am running drm-next kernel+world and installing > all packages off of the freebsd.org pkg repository with success. this ports > tree should still work, but is no longer a hard requirement - i'll block out > some time to update the wiki today. > -pete > Pete Wright I believe, freebsd-ports-graphics would be mostly the same as regular ports tree except for category x11? I see (NetBSD) pkgsrc is already up to v1.19.3 for modular-xorg-server, but don't think pkgsrc would successfully mix with freebsd-base-graphics. I don't want to keep two ports trees if there is no advantage in so doing. Tom