[Libva] [PATCH] Allow control over logging of messages from libva
Barry Scott
barry.scott at onelan.co.uk
Fri May 22 02:58:04 PDT 2015
On Fri 22 May 2015 14:37:46 Xiang, Haihao wrote:
> On Mon, 2015-05-18 at 14:35 +0100, Barry Scott wrote:
> > On Mon 18 May 2015 09:16:12 Xiang, Haihao wrote:
> > > On Thu, 2015-05-14 at 14:43 +0100, Barry Scott wrote:
> > > Setting default level to LOG_LEVEL_ERROR will change the current
> > >
> > > behavior and it might impact other users' experience.
> >
> > Do you think that there is any user that cares about these debug
> > messages?
>
> Someone checks the driver info via the message.
>
But you already solved that problem with the vainfo tool and its output is be detailed
and exact.
>From logging that I want to stop:
libva info: VA-API version 0.36.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_36
libva info: va_openDriver() returns 0
>From vainfo:
vainfo: VA-API version: 0.36 (libva 1.4.1)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Desktop - 1.4.2.pre1
(17.vpp.vebox-r1-8-gad3f8b5)
vainfo: Supported profile and entrypoints
...
Its not clear to me that there is a problem with removing the messages by default.
I would suggest with your vainfo tool it is not required to output version info from the
libva itself by default.
Barry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/libva/attachments/20150522/2a611187/attachment-0001.html>
More information about the Libva
mailing list