From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109714] Unable to Compile R200 driver: "Options 'r200' are not allowed..."
Date: Thu, 21 Feb 2019 11:27:00 +0000 [thread overview]
Message-ID: <bug-109714-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1235 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109714
Bug ID: 109714
Summary: Unable to Compile R200 driver: "Options 'r200' are not
allowed..."
Product: Mesa
Version: 18.3
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r200
Assignee: dri-devel@lists.freedesktop.org
Reporter: emoriel17@yahoo.com
QA Contact: dri-devel@lists.freedesktop.org
On Ubuntu 18.04LTS, 18.04.1LTS, and Ubuntu 18.04.2LTS, as well as Ubuntu 18.10,
and even with Oibaf's PPA for those released, the R200 driver is not included,
causing the Radeon 9000M (rv250) on my ThinkPad T42 to default to the LLVMPipe
driver.
When attempting to compile Mesa with the R200 driver, on Solus, Meson spits out
the following error: ERROR: Options "r200" are not in allowed choices: ",
auto, kmsro, radeonsi, r300, r600, nouveau, freedreno, swrast, v3d, vc4,
etnaviv, tegra, i915, svga, virgl, swr, panfrost".
Any idea why I cannot compile the R200 driver?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2645 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-02-21 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 11:27 bugzilla-daemon [this message]
2019-02-21 15:30 ` [Bug 109714] Unable to Compile R200 driver: "Options 'r200' are not allowed..." bugzilla-daemon
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-109714-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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 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.