Date: Sat, 08 Dec 2018 21:11:56 +0300 From: Greg V <greg@unrelenting.technology> To: Kevin Oberman <rkoberman@gmail.com> Cc: Jan Beich <jbeich@freebsd.org>, yuripv@yuripv.net, "freebsd-x11@freebsd.org" <x11@freebsd.org> Subject: Re: [CFT] Mesa 18.3.0 update (mesa-libs, mesa-dri, libosmesa, clover) Message-ID: <1544292716.1907.0@smtp.migadu.com> In-Reply-To: <CAN6yY1ukNSMR%2B%2B=XqHAOHx6akvXu3_u4mi2iuu0DOX_5gsoHNg@mail.gmail.com> References: <wool-v81e-wny@FreeBSD.org> <790ba1cb-7251-e8b3-f7a3-6de3cdee9958@yuripv.net> <8t11-v5xg-wny@FreeBSD.org> <CAN6yY1ukNSMR%2B%2B=XqHAOHx6akvXu3_u4mi2iuu0DOX_5gsoHNg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 8, 2018 at 8:34 PM, Kevin Oberman <rkoberman@gmail.com>=20 wrote: > mesa18.3 is running fine on my Sandy Bridge system. 1080p video plays > smoothly with little CPU load. glgears runs 60 FPS with vsync and=20 > just > under 5000 without. >=20 > I didn't think that the HD3000 did HW compositing. Firefox reports it > "Blocked by platform". Yes, Firefox still doesn't enable HW compositing by default on=20 Linux/BSD/etc. You have to force-enable it in about:config (or via environment=20 variables). > Again I see the implication that VAAPI is AMD specific. AFAIK, it is=20 > the > Intel specific implementation of Gallium. In any case, it is required=20 > (with > the libva-intel-driver) for video acceleration on the HD3000 GPU. To clear some confusion: - VA-API is, well, an API. For video encode/decode acceleration; - Mesa has a VAAPI implementation for AMD Radeons; - libva-intel-driver is a VAAPI implementation for Intel iGPUs =97 it's=20 *not part of Mesa*, it's an independent Intel project; - Gallium is an internal graphics-related part of Mesa that doesn't=20 have much to do with VAAPI. =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1544292716.1907.0>