ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Konstantin Lepikhov <lakostis@altlinux.org>
To: devel@lists.altlinux.org
Subject: Re: [devel] Q: libva feedback
Date: Fri, 13 Oct 2017 14:32:33 +0200
Message-ID: <20171013123233.GA30649@lks.home> (raw)
In-Reply-To: <8b319066-178a-af81-e6a2-0e42cf48fb16@basealt.ru>

Hi Anton!

On 10/13/2017, at 02:35:32 PM you wrote:

> Я всегда проверяю libva на железе перед отправкой на связке ffmpeg+vlc.
> 
> Что там за неправильный merge ?
> 
<skip>
http://git.altlinux.org/people/lakostis/packages/?p=libva.git;a=blobdiff;f=va/va.c;h=d4c188f66d4d0494ab84988a4442c0b2dece955d;hp=7f027dd8d812b53e41835fd094a9b903daad0e76;hb=a620ea1ba8a174cbf2c699b763a8ac0bf796c2c4;hpb=39a559e6e117f0d6aae62a0e541544a36a19caed

@@ -648,8 +648,6 @@ VAStatus vaInitialize (
...

Насколько я помню из своего патча для /etc/libva.conf, там не должно быть
повторного вызова getenv, поскольку значение LIBVA_DRIVER_NAME будет null
если переменнная окружения не задана и это значение перепишет предыдущее
из /etc/libva.conf

см. va/va.c:

  59 /*
  60  * read a config "env" for libva.conf or from environment setting
  61  * libva.conf has higher priority
  62  * return 0: the "env" is set, and the value is copied into env_value
  63  *        1: the env is not set
  64  */
  65 int va_parseConfig(char *env, char *env_value)

-- 
WBR et al.


  reply	other threads:[~2017-10-13 12:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13  9:36 Konstantin Lepikhov
2017-10-13 11:13 ` Sergey Bolshakov
2017-10-13 11:35 ` Anton Farygin
2017-10-13 12:32   ` Konstantin Lepikhov [this message]
2017-10-13 12:46     ` Anton Farygin
2017-10-13 13:01       ` Konstantin Lepikhov
2017-10-13 13:05         ` Anton Farygin
2017-10-13 13:20           ` Konstantin Lepikhov
2017-10-13 13:25             ` Anton Farygin
2017-10-13 14:09               ` Konstantin Lepikhov
2017-10-13 16:52                 ` Anton Farygin
2017-10-23 10:52           ` Konstantin Lepikhov
2017-10-23 11:38             ` Anton Farygin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171013123233.GA30649@lks.home \
    --to=lakostis@altlinux.org \
    --cc=devel@lists.altlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git