From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11906] the new version of mesa3d cannot support etnaviv when compiled with --enable-autotools
Date: Sun, 26 May 2019 19:32:41 +0000 [thread overview]
Message-ID: <bug-11906-163-6ilqi5esVD@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11906-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11906
--- Comment #2 from romain.naour at gmail.com ---
Hi,
kmsro driver is currently only available for vc4 GPU since Buildroot (2019.05)
currently use autotools build system. See [1].
As you noticed, building kmsro driver for etnaviv require to use the meson
build system. There is an existing patch series in the patchwork doing so [2].
There is even a patch adding the support for kmsro driver for etnaviv [3].
It would be great if you can test this series and send a feedback (Tested-by).
See [4] for further details.
So this is not really a bug, this is a missing feature due to the late
switching to meson build system in mesa3d package.
Best regards,
Romain
[1]
https://git.buildroot.net/buildroot/commit/?id=c19e2f44cccf65f34c416ecda9a9ebd96608891f
[2] http://patchwork.ozlabs.org/project/buildroot/list/?series=106301
[3] http://patchwork.ozlabs.org/patch/1095779
[4] http://nightly.buildroot.org/manual.html#_reviewing_and_testing_patches
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-05-26 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 8:31 [Buildroot] [Bug 11906] New: the new version of mesa3d cannot support etnaviv when compiled with --enable-autotools bugzilla at busybox.net
2019-05-24 8:33 ` [Buildroot] [Bug 11906] " bugzilla at busybox.net
2019-05-26 19:32 ` bugzilla at busybox.net [this message]
2019-05-27 12:10 ` bugzilla at busybox.net
2020-02-10 14:19 ` bugzilla at busybox.net
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=bug-11906-163-6ilqi5esVD@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.