Date: Tue, 22 May 2018 13:58:54 +0200 From: Niclas Zeising <zeising+freebsd@daemonic.se> To: dpolyg <dpolyg@gmail.com>, Andreas Nilsson <andrnils@gmail.com>, Johannes Lundberg <johalun0@gmail.com> Cc: FreeBSD X11 mailing list <freebsd-x11@freebsd.org>, "K. Macy" <kmacy@freebsd.org>, Rozhuk Ivan <rozhuk.im@gmail.com>, Oliver Pinter <oliver.pinter@hardenedbsd.org>, Current FreeBSD <freebsd-current@freebsd.org>, Steve Kargl <sgk@troutmask.apl.washington.edu>, Warner Losh <imp@bsdimp.com> Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <cd25ede4-4cd1-125a-39c4-ff1c2fb82044@daemonic.se> In-Reply-To: <368b7106-d9c9-c860-cc00-54a45a07d34c@gmail.com> References: <CAPS9%2BSv6SDWkbrEZruM4g2%2BOfw4ksvbtiMF=Q_towrMtJrgt1w@mail.gmail.com> <20180518193009.GA88432@troutmask.apl.washington.edu> <CANCZdfoMrFCyPteChSWgfYRY-uOyazzR0ZbYvp_OVmXRTe-Hqw@mail.gmail.com> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <CAPQ4ffvd1da%2BiMXtPfz%2BxETqPZwgmNoBa5yZMSF26qPMkSD2qQ@mail.gmail.com> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <CAHM0Q_ND3_4EB7mXoPK94wQSXsrgpvLO8D2kRDMnA=pZ4wLzUA@mail.gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> <CAECmPwsfSSYtcHypWej4vTiDJy_wHM0pm8YchZniAe17ojXGgA@mail.gmail.com> <CAPS9%2BSt5dZaAwC%2Bw1EyXW2hr4D4dgpZUzVjQ2=aKdMS9ucZaRg@mail.gmail.com> <368b7106-d9c9-c860-cc00-54a45a07d34c@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/22/18 13:47, 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=20 > factor PCs from Shuttle: > http://global.shuttle.com/products/productsList?categoryId=3D69 > 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)=20 > models. Do I missing something? > Here is concrete example: > I have a Shuttle DS47:=20 > http://global.shuttle.com/main/productsDetail?productId=3D1718 > 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= =20 > video call to it from a smartphone (WebRTC) (imagine "Amazon Show"=20 > powered by stock FeeBSD) but I never install any drm-next on it. Stock=20 > amd64 kernel used. No ports compiled. Only "pkg install ..." + custom=20 > code as the most front end. > After reading this thread I tried to compile drm-next on my DS47 box: >=20 > root@ShuttleD47:/usr/ports/graphics/drm-next-kmod # uname -a > FreeBSD ShuttleD47 11.1-RELEASE-p10 FreeBSD 11.1-RELEASE-p10 #0: Tue Ma= y=20 > =C2=A08 05:21:56 UTC 2018=20 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC=C2=A0 a= md64 > root@ShuttleD47:/usr/ports/graphics/drm-next-kmod # make > =3D=3D=3D>=C2=A0 drm-next-kmod-4.11.g20180505_1 not supported on 10.x o= r older, no=20 > kernel > support. > *** Error code 1 >=20 > Stop. > make: stopped in /usr/ports/graphics/drm-next-kmod >=20 > 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-Computers/zgbs/ele= ctronics/13896591011=20 >=20 That is most likely a typo, or at least not as good as it should be.=20 drm-stable-kmod and drm-next-kmod are supported on CURRENT and will be=20 supported on FreeBSD 11.2 (it's supported in stable right now). Older=20 releases will, however, not be supported. But they still have drm2, I=20 will not remove any drivers from releases or from STABLE. Regards --=20 Niclas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cd25ede4-4cd1-125a-39c4-ff1c2fb82044>