From: Mike Crowe <mac@mcrowe.com>
To: openembedded-core@lists.openembedded.org
Subject: Correct way to set DRIDRIVERS and GALLIUMDRIVERS from mesa bbappend
Date: Wed, 1 Dec 2021 16:43:49 +0000 [thread overview]
Message-ID: <YaemRcD22hUhkQrq@mcrowe.com> (raw)
I'm building for a specific chip and therefore don't wish to waste time and
electricity building and disk space on the target installing unwanted mesa
drivers. However, mesa.inc contains:
GALLIUMDRIVERS = "swrast"
GALLIUMDRIVERS:x86-x32 = ""
GALLIUMDRIVERS:append:x86:class-target = ",i915,iris,crocus"
GALLIUMDRIVERS:append:x86-64:class-target = ",i915,iris,crocus"
and mesa_21.3.0.bb contains:
DRIDRIVERS ??= ""
DRIDRIVERS:append:x86:class-target = ",r100,r200,nouveau,i965"
DRIDRIVERS:append:x86-64:class-target = ",r100,r200,nouveau,i965"
I'm unable to find a way to override these values. Using (for example):
DRIDRIVERS:forcevariable = ""
GALLIUMDRIVERS:forcevariable = "swrast"
doesn't work because the append still happens after the forcevariable
override takes effect. :(
Is there a way that I can override GALLIUMDRIVERS and DRIDRIVERS with my
own values for x86 and x86-64 without modifying oe-core itself?
If not, should the oe-core recipe being using something like:
GALLIUMDRIVERS_DEFAULT = "swrast"
GALLIUMDRIVERS_DEFAULT:x86-x32 = ""
GALLIUMDRIVERS_DEFAULT:append:x86:class-target = ",i915,iris,crocus"
GALLIUMDRIVERS_DEFAULT:append:x86-64:class-target = ",i915,iris,crocus"
GALLIUMDRIVERS ?= "${GALLIUMDRIVERS_DEFAULT}"
and similar for DRIDRIVERS to support this?
Thanks.
Mike.
next reply other threads:[~2021-12-01 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 16:43 Mike Crowe [this message]
2021-12-01 17:21 ` [OE-core] Correct way to set DRIDRIVERS and GALLIUMDRIVERS from mesa bbappend Alexander Kanavin
2021-12-01 18:05 ` Mike Crowe
2021-12-01 20:33 ` Alexander Kanavin
2021-12-02 15:58 ` Mike Crowe
2021-12-01 19:18 ` Justin Bronder
2021-12-01 20:20 ` Mike Crowe
2021-12-02 17:00 ` [OE-core] " Richard Purdie
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=YaemRcD22hUhkQrq@mcrowe.com \
--to=mac@mcrowe.com \
--cc=openembedded-core@lists.openembedded.org \
/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