Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Mahyar Koshkouei <mahyar.koshkouei@gmail.com>,
	Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/mpv: vaapi-drm needs egl-drm
Date: Thu, 19 Aug 2021 23:11:12 +0200	[thread overview]
Message-ID: <20210819231112.0c561c52@windsurf> (raw)
In-Reply-To: <CAPi7W8386-5F-fCsNzNWev47_14DB5B7Tqey4QawWDWELMJHCw@mail.gmail.com>

On Thu, 19 Aug 2021 22:40:16 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> > Do we can only use Mesa3D as an EGL provider ?  
> From my understanding, vaapi-drm needs egl-drm which has been added
> with commit 031df474c24f92757ac95ade572b90995ebdc6a2 and is only
> available with mesa3d because of gbm dependency:
> https://github.com/mpv-player/mpv/blob/0b56e1c00a57fdb767674462c299a5c973a9e373/wscript#L571

OK, so it's related to the fact that for now, only Mesa3D is recognized
as a proper gbm provider.

So I think your proposed patch is OK: this is a limitation that we
know. I know internally at Bootlin we do have a patch series (probably
it was submitted once) to improve the Buildroot handling of gbm. I'll
poke internally to get it posted.

Thanks,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

      reply	other threads:[~2021-08-19 21:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 16:03 [Buildroot] [PATCH 1/1] package/mpv: vaapi-drm needs egl-drm Fabrice Fontaine
2021-08-19 20:32 ` Thomas Petazzoni
2021-08-19 20:40   ` Fabrice Fontaine
2021-08-19 21:11     ` Thomas Petazzoni [this message]

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=20210819231112.0c561c52@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=mahyar.koshkouei@gmail.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox