From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/2] package/mesa3d: update vc4 help text
Date: Tue, 4 Feb 2020 22:03:00 +0100 [thread overview]
Message-ID: <20200204210300.GC6335@scaer> (raw)
In-Reply-To: <20200204144412.6666-3-ps.report@gmx.net>
Peter, All,
On 2020-02-04 15:44 +0100, Peter Seiderer spake thusly:
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> package/mesa3d/Config.in | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/package/mesa3d/Config.in b/package/mesa3d/Config.in
> index 1351d1cd97..9389a6132e 100644
> --- a/package/mesa3d/Config.in
> +++ b/package/mesa3d/Config.in
> @@ -244,8 +244,10 @@ config BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_VC4
> select BR2_PACKAGE_LIBDRM_VC4
> select BR2_PACKAGE_MESA3D_OPENGL_EGL
> help
> - Driver for Broadcom VC4 (rpi2/3) GPUs.
> - It requires a vanilla 4.5+ kernel with drm vc4 (open) support.
> + Driver for Broadcom VC4 (rpi2/3/4) GPUs (needs kmsro).
> + It requires a recent enough mainline/raspberrypi kernel with
> + drm vc4 (CONFIG_DRM_VC4) support enabled, for rpi4 additional
> + v3d support is required.
This is all very confusing...
First, you add rpi4 as supported by the vc4 driver, but the v3d driver
is also supposed to cover the rpi4. Are both needed? Is the v3d driver
a supperset, a subset, a complement to vc4? If so, why doesn't the v3d
driver select the vc4 driver (although it selects the vc4 drm backend)?
Or is it possible to use just the vc4 driver on rpi4?
Then, you drop the 4.5+ version with this hazy "recent enough"
categorisation. For the same reason as I explained in the previous
patch, this is not nice.
So, please explain in the commit log what is going on here...
In the meantime, I marked the patch as rejected in patchwork.
Regards,
Yann E. MORIN.
> config BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_VIRGL
> bool "Gallium virgl driver"
> --
> 2.25.0
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-02-04 21:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 14:44 [Buildroot] [PATCH v1 0/2] Raspberry Pi 4 - mesa3d support Peter Seiderer
2020-02-04 14:44 ` [Buildroot] [PATCH v1 1/2] package/mesa3d: add v3d driver support Peter Seiderer
2020-02-04 20:55 ` Yann E. MORIN
[not found] ` <20200204224540.23f620c0@gmx.net>
2020-02-04 22:00 ` Peter Seiderer
2020-02-04 22:14 ` Yann E. MORIN
2020-02-04 22:40 ` Peter Seiderer
2020-02-05 9:30 ` Yann E. MORIN
2020-02-04 14:44 ` [Buildroot] [PATCH v1 2/2] package/mesa3d: update vc4 help text Peter Seiderer
2020-02-04 21:03 ` Yann E. MORIN [this message]
2020-02-04 21:55 ` Peter Seiderer
2020-02-05 9:37 ` Yann E. MORIN
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=20200204210300.GC6335@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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