From owner-freebsd-x11@freebsd.org Wed Mar 22 18:23:40 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 9D9FDD1806E for ; Wed, 22 Mar 2017 18:23:40 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: from mail-qt0-x243.google.com (mail-qt0-x243.google.com [IPv6:2607:f8b0:400d:c0d::243]) (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 52BD31AC0 for ; Wed, 22 Mar 2017 18:23:40 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: by mail-qt0-x243.google.com with SMTP id r5so26452290qtb.2 for ; Wed, 22 Mar 2017 11:23:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=SMyjlunh+vVTBX68RAlPT0FcSQ5FiAr6dOTKlhvRxsE=; b=dCZ/55ZW5fEwlUP0p7juHvj8dZxhmBCHtwFBgnhjyvpqSZPtyu0XLBpZRmwlGH3ROm 2Y1j2y6z0ccWn2aAwiaZb7rujE1RVSxhJILcdJKBF/MxQhGcgZeMGu7qkRzSaO7XlG0x +uBdDSF9G6uw+aI8B1/joPCy8EV9HOjQoc22rvoNLt3hn8CuUe+cl/Xiemp73Am8jWsx c8iMWVB3oQHJzILtlM6UjP45mIWVVyJJYyp9tLvpsHcOfIgliRB9z8I1JMF4RFxIdY5F BaPl0W84wYnNleQgTba5r3dxmjH0U67Y0JoddC/gf2+UqfE10Qo4YJdR9D0m77C07Fjx pHbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=SMyjlunh+vVTBX68RAlPT0FcSQ5FiAr6dOTKlhvRxsE=; b=crIPhH59uoyUK4RVa/VWGfgVZD0Id/3gCEUvgYQzERJm4CxLGrBrEVfLCqMXRoPZLv W9Hc+wGVq8arLlDUhfpypfTRRGAkIP+Zlz+jhnqn+I5wjp0Jgtx6EifkqykJqRFhLjJG +pHABqZyK3Kn6A/aIWLjwC9bP+f3OeJrv3aZaqt7APlGdN5yB+7me2x1y1iwsA241XSD vySLWVRVGc9N7uIu3PqvkHT1lsmFu/6emep7fVB8AjGL/U2W6YP7r47bVshj/v+5zuHl 8tod+YbyqZMi2pfwQixLyNvt+8xrtX97fYee/O7U+bWh5AMZNvfT8bhAN0g85LcDw6Zq 64pA== X-Gm-Message-State: AFeK/H3SNNxIl5kBzpfi5H0EkSczbw3jQU8naiNzP5drtwWGefk9HdS1n513us1lP28bMg== X-Received: by 10.237.52.130 with SMTP id x2mr22240299qtd.177.1490207019180; Wed, 22 Mar 2017 11:23:39 -0700 (PDT) Received: from [155.41.76.208] (dhcp-wifi-8021x-155-41-76-208.bu.edu. [155.41.76.208]) by smtp.gmail.com with ESMTPSA id t47sm1494676qte.45.2017.03.22.11.23.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Mar 2017 11:23:38 -0700 (PDT) Sender: Theron Tarigo Subject: Re: Status of Intel Broadwell GPU Support?? To: Pete Wright , freebsd-x11@freebsd.org 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> <5d9d18c0-e73a-3f08-3ec5-7ad0e4d96ca1@gmail.com> From: Theron Message-ID: <4aa47054-d710-5f0f-5bf5-1927dce424fb@gmail.com> Date: Wed, 22 Mar 2017 14:23:37 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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: Wed, 22 Mar 2017 18:23:40 -0000 On 03/22/17 13:58, Pete Wright wrote: > > > On 03/22/17 10:20, Theron wrote: >> On 03/22/17 08:50, Bob Willcox wrote: >>> On Wed, Mar 22, 2017 at 09:02:27AM +0000, Thomas Mueller wrote: >>>>> Hooray!! My system is up and running the >>>>> FreeBSDDesktop/freebsd-base-graphics version! >>>>> The download, build, & install was mostly uneventful. Thanks again >>>>> for your help! >>>>> Bob >>>>> Bob Willcox >>>> Did you use freebsd-base-graphics for buildworld and buildkernel, >>>> or did you use the normal /usr/src for buildworld and >>>> freebsd-base-graphics for the kernel? >>>> >>>> >>>> Tom >>>> >>> I followed the instructions here: >>> >>> 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 think the problem with upstreaming is that >> FreeBSDDesktop/freebsd-base-graphics uses elements of the Linux >> source tree organization, namely the drivers/gpu and >> Documentation/gpu directories, which do not fit in the normal FreeBSD >> source tree. As far as I can tell the FreeBSDDesktop team did this >> to minimize differences between Linux and FreeBSD gpu sources. Maybe >> these directories should be put elsewhere and just the makefiles >> modified to resolve the differences? Or have the source consist of >> the files with unmodified Linux paths along side a patch file >> correcting the differences, similarly to ports? Given that most >> technical issues are out of the way and that there is a high user >> demand for this support, it seems to be time for the developers to >> revisit this issue. > > I don't want to speak for mmacy@ or others, but my understanding was > to first implement a linux KPI layer for FreeBSD that is up to date > with the current linux kernel code. this should allow for easier > integration of the DRM bits from linux onto FreeBSD, and help get > other drivers and that are linux specific working. > > I believe currently work is happening right now to get the lkpi code > from drm-next integrated into upstream CURRENT, and some folks are > working on creating a drm port/pkg for intel i915 graphics as well as > for amd GPU's. This plan should help avoid some of the nastiness you > mention, while also keeping GPL'd that is required to get all the bits > working correctly out of the base system. > > at least that is my understanding - i'm sure someone will chime in if > i'm off base/confused though :) > > -pete > You must be right about linuxkpi being the real issue. I did an experiment locally where I deleted sys/dev/drm which is a symlink to drivers/gpu/drm, moved drivers/gpu/drm to sys/dev/drm, and deleted drivers/gpu entirely. The kernel still builds with no issue, so the only remaining reason for drivers/gpu is diff compatibility with Linux source. How would these drivers work as ports? Would this work like x11/nvidia-driver? Of course there must be others but Nvidia and Virtualbox are the ports I have encountered which provide kernel modules. Theron