public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marek Szuba <marecki@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] RFC: Introducing VIDEO_CARDS=iris to virtual/opencl
Date: Mon, 16 Dec 2019 15:25:46 +0000	[thread overview]
Message-ID: <04571007-17a7-8f7d-3d2e-731a686df590@gentoo.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1113 bytes --]


Penny for your thoughts, guys: I am thinking about splitting the
video_cards_i965 condition in virtual/opencl so that NEO is pulled in by
video_cards_iris instead, and I wonder if there is anything I haven't
thought about.

The reason why I would like to do this is that there is clear
correspondence between compatibility matrices of the Iris OpenGL driver
and the NEO OpenCL driver - both only work on Broadwell and newer. There
are differences of course, most notably that the old OpenCL driver
(Beignet) is already considered deprecated for systems supported by NEO
whereas the old OpenGL driver in Mesa (i965) is still the official one
even for newer systems.

Nb. to the best of my knowledge it is safe to set VIDEO_CARDS=iris even
globally because if both i965 and iris are available, Mesa for now still
prefers the former unless the environment variable
MESA_LOADER_DRIVER_OVERRIDE has been set to 'iris'.

There would of course have to be a news item advising the users of
virtual/opencl + dev-libs/intel-neo to adjust their USE flags.

What do you think, guys?

-- 
Marecki


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2019-12-16 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16 15:25 Marek Szuba [this message]
2019-12-17 21:21 ` [gentoo-dev] RFC: Introducing VIDEO_CARDS=iris to virtual/opencl Matt Turner
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=04571007-17a7-8f7d-3d2e-731a686df590@gentoo.org \
    --to=marecki@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