From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13831] mesa3d - kmsro driver requires dri3
Date: Sat, 12 Jun 2021 22:38:17 +0000 [thread overview]
Message-ID: <bug-13831-163-Ru5dt3tB8D@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13831-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13831
--- Comment #3 from Peter Seiderer <ps.report@gmx.net> ---
Patches suggested:
- [v1,1/2] package/mesa3d: add config option for DRI3 support:
https://patchwork.ozlabs.org/project/buildroot/patch/20210612223011.26118-1-ps.report at gmx.net/
- [v1,2/2] package/mesa3d: gallium/kmsro drivers require dri3 for X11
https://patchwork.ozlabs.org/project/buildroot/patch/20210612223011.26118-2-ps.report at gmx.net/
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-06-12 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 9:07 [Buildroot] [Bug 13831] New: mesa3d - kmsro driver requires dri3 bugzilla at busybox.net
2021-06-11 11:50 ` [Buildroot] [Bug 13831] " bugzilla at busybox.net
2021-06-11 18:51 ` bugzilla at busybox.net
2021-06-12 22:38 ` bugzilla at busybox.net [this message]
2022-07-25 13:50 ` bugzilla
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-13831-163-Ru5dt3tB8D@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox