From owner-freebsd-x11@freebsd.org Tue May 22 12:04:02 2018 Return-Path: Delivered-To: freebsd-x11@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 21436EF385F for ; Tue, 22 May 2018 12:04:02 +0000 (UTC) (envelope-from dpolyg@gmail.com) Received: from mail-pg0-x244.google.com (mail-pg0-x244.google.com [IPv6:2607:f8b0:400e:c05::244]) (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 91C46715F1 for ; Tue, 22 May 2018 12:04:01 +0000 (UTC) (envelope-from dpolyg@gmail.com) Received: by mail-pg0-x244.google.com with SMTP id a3-v6so2851043pgt.13 for ; Tue, 22 May 2018 05:04:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=z/ds9H2+qdGPXg5O6cx7kWGtDlGm5w3qUznqegpSK6E=; b=fFgDfb/l76Mxzcwf2PlSHHxW5jo9qi+r7pQhRJpcHKrgs4E3Hc7tTRXUDobmttg5CP ml9/kI2w4UpfOCfoc0b7472ss6GB62yw9jDv+rChJRysRziPWLFQDSdvgCMKR6oPE/RL 7m0gMK6OwcQKBt1YuE3dv0P3BQiZEU9rdsdq6ONRuZCLvFIyJyG1gVLBrrYkMIB25zF0 NQppaoGAgldPSqhACIF/4TZ4Dy4mCCfqXavCgFk/vcIZyKH+hYa6l4HHYLcU5clH4H10 /TPWCbFYonzwRJd+6Ri0VDqrkn7kuDYjzzjEL0CAKN/r9Ibk+5roJB08/89DR1GMJn2q 0fjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=z/ds9H2+qdGPXg5O6cx7kWGtDlGm5w3qUznqegpSK6E=; b=SIA4ZSn1eRifM+G/Md3lqZd+V2V/0YM8+OxWQOx8iRpBGe2ozW9tqs/bCohSaXOLEa rZzvFlu9Q7Y/Ctj/SQNH7hZc8q2f6cm0fA45lwoM6hQ6aoc36Zde9V/q/pKOPvHAN638 Ds7RtbZ/54zL2yUIxDI+EIoDIB5VKLJ3qS6TRqVrbSWyP3nqXxp4zOTeiUEFwMRANnna RvSrhS+oux7l9D2HNl+qr24S+Uh+DiAFmMeNticJykBYrlhx2Cs4X3pYqEImmk3y/jNc GUNJI5vJTi+bZacJm0GY9A/GiPKBGg7WClyiKG/yc/p+0uV4lakVRpK02ShwHqH6Uq4o CtWA== X-Gm-Message-State: ALKqPwcjuRwYXGAhwL6X6yPvWxUqV2pStjgQcrGLPqAM/sNUgd4UuGSP swo2TsBCaiVlXRTpP3j4vATA+g== X-Google-Smtp-Source: AB8JxZq/4zPwexJJNgbPsHlc6ZCQ22E3PT4oie3ZZ4Nf3G2bF0cAHy9gUSr4nVjs7AsY9B0XbSMFtQ== X-Received: by 2002:a62:c103:: with SMTP id i3-v6mr23891357pfg.148.1526990640547; Tue, 22 May 2018 05:04:00 -0700 (PDT) Received: from [192.168.1.100] (ngn6-ppp656.tokyo.sannet.ne.jp. [157.192.82.148]) by smtp.googlemail.com with ESMTPSA id h28-v6sm19977370pgn.65.2018.05.22.05.03.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 May 2018 05:04:00 -0700 (PDT) Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Johannes Lundberg Cc: FreeBSD X11 mailing list References: <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> <368b7106-d9c9-c860-cc00-54a45a07d34c@gmail.com> From: dpolyg Message-ID: <5e092e7b-9d5a-528c-c838-55debcb2678f@gmail.com> Date: Tue, 22 May 2018 21:03:58 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2018 12:04:02 -0000 Hi Johannes, sorry, I forgot to mention in my previous e-mail that I tried drm-stable too with the same result: root@ShuttleD47:/usr/ports/graphics/drm-stable-kmod # make ===> drm-stable-kmod-g20180505_5 not supported on 10.x or older, no kernel support. *** Error code 1 Stop. make: stopped in /usr/ports/graphics/drm-stable-kmod I have latest port tree (run '# portsnap fetch update' in advance). Regards, Denis. On 22/05/2018 8:55 PM, Johannes Lundberg wrote: > On Tue, May 22, 2018 at 12:47 PM, dpolyg wrote: > >> I have one comment regarding usage of the drm2 on a "legacy" hardware. >> Excuse me in advance if I misunderstand something. >> For the last 2-3 years I'm playing with devices such as small form factor >> PCs from Shuttle: >> http://global.shuttle.com/products/productsList?categoryId=69 >> or from Gigabyte: >> https://www.gigabyte.com/us/Mini-PcBarebone >> or Intel "NUC"s. >> To my experience drm-next doesn't work on lower price (Celeron/Atom) >> models. Do I missing something? >> Here is concrete example: >> I have a Shuttle DS47: http://global.shuttle.com/main >> /productsDetail?productId=1718 >> running FreeBSD 11.1-RELEASE and drm2.ko loaded + Xorg + compton. >> Having that I made a box with a voice control and ability to make a SIP >> video call to it from a smartphone (WebRTC) (imagine "Amazon Show" powered >> by stock FeeBSD) but I never install any drm-next on it. Stock amd64 kernel >> used. No ports compiled. Only "pkg install ..." + custom code as the most >> front end. >> After reading this thread I tried to compile drm-next on my DS47 box: >> >> root@ShuttleD47:/usr/ports/graphics/drm-next-kmod # uname -a >> FreeBSD ShuttleD47 11.1-RELEASE-p10 FreeBSD 11.1-RELEASE-p10 #0: Tue May >> 8 05:21:56 UTC 2018 root@amd64-builder.daemonology >> .net:/usr/obj/usr/src/sys/GENERIC amd64 >> root@ShuttleD47:/usr/ports/graphics/drm-next-kmod # make >> ===> drm-next-kmod-4.11.g20180505_1 not supported on 10.x or older, no >> kernel >> support. >> *** Error code 1 >> >> Stop. >> make: stopped in /usr/ports/graphics/drm-next-kmod >> >> Why drm-next thinks it lives on a 10.x kernel or older? >> Is such usage case already considered as legacy? >> Is this hardware supported by drm-next? >> https://www.amazon.com/Best-Sellers-Electronics-Mini-Compute >> rs/zgbs/electronics/13896591011 >> >> > > Hi Denis > > For FreeBSD 11, please use drm-stable-kmod (this is based on drm drivers in > Linux 4.9 and has been backported to FreeBSD 11) > > For FreeBSD 12, drm-next-kmod is currently Linux 4.11 but will updated to > Linux 4.15 soon. (of course, drm-stable-kmod is also usable on 12-CURRENT. > you might wanna use that if drm-next-kmod is buggy) > > If you need the firmware, gpu-firmware-kmod port is used for both > drm-xxx-kmod ports. > > > > >> Regards, >> Denis. >> >> >> >> On 22/05/2018 4:51 PM, Andreas Nilsson wrote: >> >>> On Tue, May 22, 2018 at 8:50 AM, Johannes Lundberg >>> wrote: >>> >>> On Mon, May 21, 2018 at 23:50 Steve Kargl >>> edu> >>>> wrote: >>>> >>>> On Mon, May 21, 2018 at 03:20:49PM -0700, K. Macy wrote: >>>>> >>>>>> >>>>>>> I just ask. >>>>>>> Or why not include drm-next to base svn repo and add some >>>>>>> option to make.conf to swith drm2/dem-next ? >>>>>>> >>>>>> >>>>>> Even if it's not being built on amd64 we're still responsible for >>>>>> keeping it building on !amd64 so long as it's in base. This makes >>>>>> changing APIs and universe runs more burdensome. The graphics >>>>>> developers have given you notice that it will now be your collective >>>>>> responsibility to keep it up to date. >>>>>> >>>>>> >>>>> Not quite. One graphics developer has indicated a desire >>>>> to remove working code, because it interferes with the >>>>> graphics developers' port on a single architecture. There >>>>> is no indication by that graphics developer that drm2 will >>>>> be available in ports. You can go read the original post >>>>> here: >>>>> >>>>> https://lists.freebsd.org/pipermail/freebsd-current/2018- >>>>> May/069401.html >>>>> >>>>> The last paragraph is >>>>> >>>>> What does the community think? Is there anyone still using >>>>> the drm2 driver on 12-CURRENT? If so, what is preventing >>>>> you from switching to the port? >>>>> >>>>> The answer to the last two questions are "yes" and "the port >>>>> does not work on i386". >>>>> >>>>> Yes, I recognize that you're clever enough to purposefully >>>>> break the API so that you can thumb your nose at those of >>>>> us who have older hardware. >>>>> >>>>> What is wrong with using >>>>> >>>>> .if ${MACHINE_ARCH} != amd64 >>>>> ... >>>>> .endif >>>>> >>>>> to enable/disable drm2? >>>>> >>>> >>>> >>>> >>>> The answer to the first question is that the consensus seem to be that >>>> moving to a port is best for the _majority_. >>>> >>>> Let me ask you, what’s wrong with this one-liner after base install >>>> pkg install drm2 >>>> ? >>>> >>>> >>>> >>>>> -- >>>>> Steve >>>>> >>>> >>> >>> Hello, >>> >>> If you were running GNU/Linux, you would be using the equivalent of >>> drm-stable-kmod or drm-next-kmod. Why do you want to run older code on >>> FreeBSD? >>> >>> Hardware and software moves on. One does not expect to run the latest >>> hardware with old software, old hardware and new software might work, if >>> someone is willing to maintain old code. >>> >>> Since the proposal was to keep drm2 in 11, you're looking at support until >>> 2021, will you still run that old hardware then? >>> >>> With such long-time support offered by 11- branch, why hamper development >>> of 12 by lugging around old, hard to maintain code that is relevant for >>> only legacy hardware? >>> >>> Best regards >>> Andreas >>> _______________________________________________ >>> freebsd-x11@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-x11 >>> To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" >>> >>> >