From: Matt Turner <mattst88@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] RFC: Introducing VIDEO_CARDS=iris to virtual/opencl
Date: Tue, 17 Dec 2019 16:21:01 -0500 [thread overview]
Message-ID: <CAEdQ38GAP-faMu-X6VLkm2OddzaukX7S1Mjr0FJZfJCh0gS5Ng@mail.gmail.com> (raw)
In-Reply-To: <04571007-17a7-8f7d-3d2e-731a686df590@gentoo.org>
On Mon, Dec 16, 2019 at 10:26 AM Marek Szuba <marecki@gentoo.org> wrote:
> What do you think, guys?
I don't love it.
I don't like the mess that has become VIDEO_CARDS=... either. radeon
vs radeonsi vs amdgpu. Different names for different bits of the
stack, even for the same hardware. I would like to come up with
something that avoids the confusion users often have.
Does anyone have suggestions?
Should we make a cpuid2cpuflags equivalent for VIDEO_CARDS?
Should VIDEO_CARDS specify only the vendor with MESA_VIDEO_CARDS=...
etc for individual packages? (Seems gross)
Should VIDEO_CARDS be more fine grained with multiple names for the
same thing sometimes? (e.g., offer VIDEO_CARDS=amdgpu for
media-libs/mesa that enables the radeonsi driver; similarly offer
VIDEO_CARDS=radeonsi for x11-libs/libdrm that enables libdrm_radeon).
I think perhaps that in conjunction with a cpuid2cpuflags-equivalent
is the most sensible.
next prev parent reply other threads:[~2019-12-17 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 15:25 [gentoo-dev] RFC: Introducing VIDEO_CARDS=iris to virtual/opencl Marek Szuba
2019-12-17 21:21 ` Matt Turner [this message]
2019-12-18 8:33 ` Jaco Kroon
2019-12-20 13:14 ` Marek Szuba
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=CAEdQ38GAP-faMu-X6VLkm2OddzaukX7S1Mjr0FJZfJCh0gS5Ng@mail.gmail.com \
--to=mattst88@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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