Date: Tue, 11 Apr 2017 06:27:09 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Matthew Rezny <rezny@FreeBSD.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r438198 - in head: graphics/dri graphics/libGL graphics/libGL/files graphics/libosmesa lang/clover Message-ID: <20170411062709.GA36557@FreeBSD.org> In-Reply-To: <201704101914.v3AJEmNt097726@repo.freebsd.org> References: <201704101914.v3AJEmNt097726@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 10, 2017 at 07:14:48PM +0000, Matthew Rezny wrote: > New Revision: 438198 > URL: https://svnweb.freebsd.org/changeset/ports/438198 > > Log: > Update Mesa to 17.0.3 Cool, thanks! > -OPTIONS_DEFINE= TEXTURE > +OPTIONS_DEFINE= TEXTURE VAAPI VDPAU So VDPAU is back? > @@ -1,13 +1,15 @@ > -The GALLIUM option enables gallium (llvm) backed drivers such as for example > -the r600 and radeonsi driver. > +VAAPI and VDPAU options enable building Gallium based VA-API and VDPAU > +drivers to decode video on the GPU via libva and libvdpau, respectively. > +Gallium based VAAPI and VDPAU drivers are only available for Radeon GPUs. > > -The VDPAU option enables VDPAU drivers to decode video on the GPU via the > -VDPAU library. > +Both GPU decode options require newer drm drivers than are currently present > +in a released FreeBSD kernel. These are options for DRM-next and DragonFly. I'm still confused, would it work against up-to-date -CURRENT or I still need to patch the kernel parts? ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170411062709.GA36557>