unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Lilah Tascheter <lilah@lunabee.space>,
	64528@debbugs.gnu.org, iyzsong@envs.net
Subject: [bug#64528] [PATCH v2] gnu: mesa: Fix Vulkan on older Intel GPUs.
Date: Sun, 16 Jul 2023 18:06:56 +0000	[thread overview]
Message-ID: <87wmyzzq6e.fsf_-_@protonmail.com> (raw)
In-Reply-To: <60cf22ecd3b501d0c75dab931f1d018f4dd23843.1688793383.git.lilah@lunabee.space>


Hello,

Liliana Prikler wrote:
>Am Samstag, dem 08.07.2023 um 13:29 -0500 schrieb Lilah Tascheter:
>> Mesa split the Vulkan intel driver into two: intel and intel_hasvk.
>> Enables intel_hasvk so vulkan functions on older intel GPUs again,
>> and swrast for lavapipe as a fallback.
>>
>> * gnu/packages/gl.scm (mesa-vulkan-hasvk): New variable.
>>   (mesa): Graft with mesa-vulkan-hasvk.
>> ---
>Pushed.

Ah, sorry I didn't see and respond earlier as we have a mesa-updates
branch that I'm just waiting for the go ahead to merge to master. It
updates mesa and is already built on Cuirass.

How can we ensure that upon merging we don't cause the full rebuild?
Should I revert this, apply the updates, and then do this graft? Or will
applying the update on top of this graft commit be okay too?

My original thought was that this shouldn't be grafted but can just be
applied directly to mesa-updates with the next round of patches there,
as this one is already built. This could be done pretty quickly, though
I expect a new mesa version soon that I would group this with, along
with some other mass rebuild changes waiting. I think on the order of a
couple or few weeks.

What do we all think? (Sorry there is no mesa team as of yet, not sure
how to set that up without it applying to a too large scope of packages
by default.)

Thanks,
John





  parent reply	other threads:[~2023-07-16 18:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08  5:16 [bug#64528] [PATCH] gnu: mesa: Fix Vulkan on older Intel GPUs Lilah Tascheter via Guix-patches via
2023-07-08 15:46 ` Liliana Marie Prikler
2023-07-08 18:29 ` [bug#64528] [PATCH v2] " Lilah Tascheter via Guix-patches via
2023-07-16  7:26   ` bug#64528: " Liliana Marie Prikler
2023-07-16 18:06 ` John Kehayias via Guix-patches via [this message]
2023-07-16 18:28   ` [bug#64528] " Liliana Marie Prikler
2023-07-25 21:25     ` John Kehayias via Guix-patches via

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wmyzzq6e.fsf_-_@protonmail.com \
    --to=guix-patches@gnu.org \
    --cc=64528@debbugs.gnu.org \
    --cc=iyzsong@envs.net \
    --cc=john.kehayias@protonmail.com \
    --cc=lilah@lunabee.space \
    --cc=liliana.prikler@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).