Index | Thread | Search

From:
Rafael Sadowski <rafael@sizeofvoid.org>
Subject:
Re: NEW: multimedia/intel-media-driver
To:
Antoine Jacoutot <ajacoutot@bsdfrog.org>
Cc:
Rafael Sadowski <rafael@sizeofvoid.org>, Jonathan Gray <jsg@jsg.id.au>, ports <ports@openbsd.org>
Date:
Mon, 22 Jul 2024 08:57:50 +0200

Download raw body.

Thread
On Mon Jul 22, 2024 at 08:50:57AM GMT, Antoine Jacoutot wrote:
> On Mon, Jul 22, 2024 at 08:20:17AM +0200, Rafael Sadowski wrote:
> > On Mon Jul 22, 2024 at 02:34:28PM GMT, Jonathan Gray wrote:
> > > On Sat, Jul 13, 2024 at 12:51:39PM +0200, Rafael Sadowski wrote:
> > > > OK to import intel-media-driver-24.1.5? Keep in mind, to build this you
> > > > need libv installed from xenocara.
> > > > 
> > > > Comment:
> > > > Intel(R) Media Driver for VAAPI
> > > > 
> > > > Description:
> > > > VA-API (Video Acceleration API) user mode driver for Intel GEN Graphics family
> > > > 
> > > > VA-API is an open-source library and API specification, which provides access to
> > > > graphics hardware acceleration capabilities for video processing. It consists of
> > > > a main library and driver-specific acceleration backends for each supported
> > > > hardware vendor.
> > > > 
> > > > The current video driver backend provides a bridge to the GEN GPUs through the
> > > > packaging of buffers and commands to be sent to the i915 driver for exercising
> > > > both hardware and shader functionality for video decode, encode, and processing.
> > > 
> > > Why are you putting .so files into X11BASE with @sample?
> > > 
> > > lib/xorg/
> > > lib/xorg/modules/
> > > @so lib/xorg/modules/iHD_drv_video.so
> > > @sample ${X11BASE}/lib/modules/drivers/iHD_drv_video.so
> > > 
> > > @sample is for sample configuration files according to pkg_create(1)
> > 
> > So we ‘agreed’ (consensus in porters) to do that.
> > 
> > > 
> > > Shouldn't the .so built in ports go into LOCALBASE and
> > > libva search both X11BASE and LOCALBASE paths?
> > > 
> > 
> > This would mean that we would have to adapt libva in xenocara. Of course
> > we can do that too, but I didn't want to in the first step.
> 
> There's a 3rd solution, use PREFIX and/or @cwd, no?
> Like what we do to install stuff under /var/www

> 

Yes but both solutions end up with the same result.