Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Alexandru Ardelean <ardeleanalex@gmail.com>
Cc: Adrian Perez de Castro <aperez@igalia.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/cog: add libgbm as dependency when building with DRM support
Date: Fri, 22 Jul 2022 08:59:59 +0200	[thread overview]
Message-ID: <20220722085959.5fd21e9f@windsurf> (raw)
In-Reply-To: <CA+U=Dsr60t8_dfdAL7CAbtbGL2i8+WyWD-byyEFQg=vpc5dHBg@mail.gmail.com>

On Fri, 22 Jul 2022 09:38:02 +0300
Alexandru Ardelean <ardeleanalex@gmail.com> wrote:

> > > Of course, this aspect should be in a different patch: your change to
> > > add "libgbm" in the DEPENDENCIES variable is really a fix, while my
> > > proposed change in the Config.in file is really an improvement, that
> > > will allow using Cog on libgbm-capable platforms that don't use mesa3d
> > > as their OpenGL/libgbm implementation.  
> 
> Apologies for not including this part in the second email.
> So, at least cog 0.12.4 that is currently packaged in Buildroot
> doesn't seem to support (yet)

It's not about whether cog supports it, but whether it uses it.

> BR2_PACKAGE_LIBGBM_HAS_FEATURE_FORMAT_MODIFIER_PLANE_COUNT
> and
> BR2_PACKAGE_LIBGBM_HAS_FEATURE_DMA_BUF
> 
> at least what 'package/opengl/libgbm/Config.in ' mentions:
> - i can't see any use of gbm_device_get_format_modifier_plane_count in
> cog 0.12.4

Correct, but it is using:

gbm_bo_get_plane_count
gbm_bo_get_handle_for_plane
gbm_bo_get_stride_for_plane

etc. which are also related to the same "plane" support. Actually, I'm
wondering if the name
BR2_PACKAGE_LIBGBM_HAS_FEATURE_FORMAT_MODIFIER_PLANE_COUNT was really
the best.

We do have versions of libgbm that don't have any support for this
plane API.

> - i can't see any use of gbm_bo_get_fd in cog 0.12.4
> 
> And also looking now through the code, I see that EGL is used in all 3
> platforms (DRM, X11 and Wayland).
> Buildroot builds for Wayland and DRM (AFAICT).
> So, I guess libegl is explicitly required for the DRM platform.

Correct.

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

  reply	other threads:[~2022-07-22  7:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 14:49 [Buildroot] [PATCH] package/cog: add libgbm as dependency when building with DRM support Alexandru Ardelean
2022-07-21 16:16 ` Thomas Petazzoni via buildroot
2022-07-22  6:25   ` Alexandru Ardelean
2022-07-22  6:38     ` Alexandru Ardelean
2022-07-22  6:59       ` Thomas Petazzoni via buildroot [this message]
2022-07-22  7:01 ` [Buildroot] [PATCH v2] " Alexandru Ardelean
2022-07-22  7:05   ` Alexandru Ardelean
2022-07-23  8:48   ` Arnout Vandecappelle
     [not found]     ` <48-62dd4800-5-54f5770@160071985>
2022-07-24 13:50       ` Arnout Vandecappelle
2022-07-24 14:53       ` Thomas Petazzoni via buildroot
2022-07-26  8:29     ` Alexandru Ardelean
2022-08-12 15:05   ` Peter Korsgaard

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=20220722085959.5fd21e9f@windsurf \
    --to=buildroot@buildroot.org \
    --cc=aperez@igalia.com \
    --cc=ardeleanalex@gmail.com \
    --cc=thomas.petazzoni@bootlin.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