On Sun, Dec 15, 2019 at 07:45:07PM +0300, Vadim Zhukov wrote:
> вс, 15 дек. 2019 г. в 19:29, Brad DeMorrow :
> >
> > Based on feedback from Bryan and Vadim, the following has been tested:
> > libva: Bryan and Vadim
> > intel-vaapi-driver: Vadim (Bryan compiled a different VA-API driver for his
>
* Vadim Zhukov [2019-12-15 19:45:07 +0300]:
> вс, 15 дек. 2019 г. в 19:29, Brad DeMorrow :
> >
> > Based on feedback from Bryan and Vadim, the following has been tested:
> > libva: Bryan and Vadim
> > intel-vaapi-driver: Vadim (Bryan compiled a different VA-API driver for his
> > card)
> >
вс, 15 дек. 2019 г. в 19:29, Brad DeMorrow :
>
> Based on feedback from Bryan and Vadim, the following has been tested:
> libva: Bryan and Vadim
> intel-vaapi-driver: Vadim (Bryan compiled a different VA-API driver for his
> card)
> libva-utils: Bryan and Vadim
>
> Is it too soon to ask for OKs?
вс, 15 дек. 2019 г. в 10:02, Bryan Steele :
>
> On Sun, Dec 15, 2019 at 12:14:33AM -0500, Bryan Steele wrote:
> > I did a dirty, awful thing. For r600/radeonsi gallium drivers it seems
> > neccessary to compile Mesa with --enable-va for this to work. That said,
> > it seems that installing the
Based on feedback from Bryan and Vadim, the following has been tested:
libva: Bryan and Vadim
intel-vaapi-driver: Vadim (Bryan compiled a different VA-API driver for his
card)
libva-utils: Bryan and Vadim
Is it too soon to ask for OKs?
I'd like to move on to ports that utilize libva, but not
вс, 15 дек. 2019 г. в 18:15, Brad DeMorrow :
>
> Vadim,
> It's very possible that the H264 encode simply isn't supported by your
> chipset.
> This table from ffmpeg's site shows which generation added support for
> different things:
> https://trac.ffmpeg.org/wiki/Hardware/QuickSync
>
> It looks
Vadim,
It's very possible that the H264 encode simply isn't supported by your
chipset.
This table from ffmpeg's site shows which generation added support for
different things:
https://trac.ffmpeg.org/wiki/Hardware/QuickSync
It looks like H264 Encoding support was added in Gen 6 (Sandy Bridge).
сб, 14 дек. 2019 г. в 17:27, Brad DeMorrow :
>
> Thank you both again for the explanation. That makes sense now.
> I've updated the libva Makefile to simply use 0.0 as the SHARED_LIBS versions
> and I've removed the post-install hook that adds additional symlinks for no
> good reason.
>
> I
On Sun, Dec 15, 2019 at 12:14:30AM -0500, Bryan Steele wrote:
> I did a dirty, awful thing. For r600/radeonsi gallium drivers it seems
> neccessary to compile Mesa with --enable-va for this to work. That said,
> it seems that installing the shared libraries from this build is
> enough to make the
On Sun, Dec 15, 2019 at 12:14:33AM -0500, Bryan Steele wrote:
> I did a dirty, awful thing. For r600/radeonsi gallium drivers it seems
> neccessary to compile Mesa with --enable-va for this to work. That said,
> it seems that installing the shared libraries from this build is
> enough to make the
I did a dirty, awful thing. For r600/radeonsi gallium drivers it seems
neccessary to compile Mesa with --enable-va for this to work. That said,
it seems that installing the shared libraries from this build is
enough to make the vainfo utility happy. I haven't seen if this
actualy works with ffmpeg
Thank you both again for the explanation. That makes sense now.
I've updated the libva Makefile to simply use 0.0 as the SHARED_LIBS
versions
and I've removed the post-install hook that adds additional symlinks for no
good reason.
I added patches to remove the explicit shared library versions
сб, 14 дек. 2019 г. в 10:27, Brad DeMorrow :
>
> On Sat, Dec 14, 2019 at 1:16 AM Vadim Zhukov wrote:
>>
>> сб, 14 дек. 2019 г. в 08:25, Vadim Zhukov :
>> >
>> > сб, 14 дек. 2019 г. в 06:10, Brad DeMorrow :
>> > >
>> > > Thank you both, this is very helpful for me.
>> > > Attached are updated
On Sat, Dec 14, 2019 at 01:27:39AM -0600, Brad DeMorrow wrote:
> On Sat, Dec 14, 2019 at 1:16 AM Vadim Zhukov wrote:
>
> > сб, 14 дек. 2019 г. в 08:25, Vadim Zhukov :
> > >
> > > сб, 14 дек. 2019 г. в 06:10, Brad DeMorrow :
> > > >
> > > > Thank you both, this is very helpful for me.
> > > >
On Sat, Dec 14, 2019 at 1:16 AM Vadim Zhukov wrote:
> сб, 14 дек. 2019 г. в 08:25, Vadim Zhukov :
> >
> > сб, 14 дек. 2019 г. в 06:10, Brad DeMorrow :
> > >
> > > Thank you both, this is very helpful for me.
> > > Attached are updated tarballs.
> > > Since the meson module does the right thing,
сб, 14 дек. 2019 г. в 08:25, Vadim Zhukov :
>
> сб, 14 дек. 2019 г. в 06:10, Brad DeMorrow :
> >
> > Thank you both, this is very helpful for me.
> > Attached are updated tarballs.
> > Since the meson module does the right thing, I stuck with using it for all
> > three ports.
>
> Then why do you
On Fri, Dec 13, 2019 at 11:25 PM Vadim Zhukov wrote:
> сб, 14 дек. 2019 г. в 06:10, Brad DeMorrow :
> >
> > Thank you both, this is very helpful for me.
> > Attached are updated tarballs.
> > Since the meson module does the right thing, I stuck with using it for
> all three ports.
>
> Then why
сб, 14 дек. 2019 г. в 06:10, Brad DeMorrow :
>
> Thank you both, this is very helpful for me.
> Attached are updated tarballs.
> Since the meson module does the right thing, I stuck with using it for all
> three ports.
Then why do you create that symlink mess and complicate SHARED_LIBS?
I've
For those wishing to test, I have found information about which devices
would benefit from these:
Gen 5 - Gen 9.5 inteldrm devices are what the intel-vaapi-driver(aka i965)
supports.
There is a good deal of information available on ffmpeg's site here:
Thank you both, this is very helpful for me.
Attached are updated tarballs.
Since the meson module does the right thing, I stuck with using it for all
three ports.
What else would be needed to get this into the tree?
For the record, below is output from my pcidump as well as vainfo
brad-laptop$
On Sat, Dec 14, 2019 at 04:55:51AM +0300, Vadim Zhukov wrote:
> сб, 14 дек. 2019 г. в 04:07, Brad DeMorrow :
> >
> > First of all, thank you for taking the time to review and test this Vadim.
> > Comments inline below.
> > I have questions about using autotools for the intel-vaapi-driver port, so
сб, 14 дек. 2019 г. в 04:07, Brad DeMorrow :
>
> First of all, thank you for taking the time to review and test this Vadim.
> Comments inline below.
> I have questions about using autotools for the intel-vaapi-driver port, so I
> won't
> attach new tarballs yet.
>
> On Fri, Dec 13, 2019 at 3:58
First of all, thank you for taking the time to review and test this Vadim.
Comments inline below.
I have questions about using autotools for the intel-vaapi-driver port, so
I won't
attach new tarballs yet.
On Fri, Dec 13, 2019 at 3:58 PM Vadim Zhukov wrote:
> пт, 13 дек. 2019 г. в 22:17, Brad
пт, 13 дек. 2019 г. в 22:17, Brad DeMorrow :
>
> I wasn't clear, thorough, and concise in my previous email. My apologies.
>
> These three ports are required to enable VA-API support in OpenBSD.
Cool. At some point in the past I worked on those, but stopped due to
the same problem as seen with
I wasn't clear, thorough, and concise in my previous email. My apologies.
These three ports are required to enable VA-API support in OpenBSD.
What has changed?: Nothing, these are new ports.
Architectures tested on: amd64
Impact on consumers: No consumers yet.
Requirements for testing: An
25 matches
Mail list logo
