From: Guillaume Le Vaillant <glv@posteo.net>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 44558@debbugs.gnu.org, "Barnabás Béres" <beresbarnus03@gmail.com>,
romulasry <romulasry@protonmail.com>
Subject: bug#44558: Mesa isn't update to date
Date: Thu, 12 Nov 2020 17:26:44 +0100 [thread overview]
Message-ID: <87361eilrv.fsf@yamatai> (raw)
In-Reply-To: <87k0ushyi7.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org> skribis:
> Romulasry, are you suffering from specific Mesa 20.0.7 problems that 20.2.2
> might fix? Please let us know. An otherwise working package not being at the
> latest upstream version isn't a bug.
>
> romulasry via Bug reports for GNU Guix 写道：
>> Mesa 20.2.2 is released
>
> The core-updates branch updates Mesa to 20.1.9. Would you like to submit
> a (tested) core-updates patch updating it to 20.2.2?
Hi,
Mesa 20.2 brings direct OpenGL rendering support for Nvidia RTX 20xx
graphic cards with the nouveau driver, whereas with our current version
these cards have to use LLVMpipe.
I tested the update quickly on my local staging branch using glxgears
and vlc, and it worked fine. When reading a video the CPU usage dropped
from 30% to 2%, which is nice.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-11-12 16:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 20:29 bug#44558: Mesa isn't update to date romulasry via Bug reports for GNU Guix
2020-11-11 11:40 ` Barnabás Béres
2020-11-11 12:24 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-11 13:08 ` Barnabás Béres
2020-11-11 13:25 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-11 13:55 ` Barnabás Béres
2020-11-12 16:26 ` Guillaume Le Vaillant [this message]
2020-11-12 21:27 ` Marius Bakke
2020-11-13 13:56 ` Guillaume Le Vaillant
2020-11-13 15:49 ` Marius Bakke
2021-11-14 1:26 ` Maxim Cournoyer
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=87361eilrv.fsf@yamatai \
--to=glv@posteo.net \
--cc=44558@debbugs.gnu.org \
--cc=beresbarnus03@gmail.com \
--cc=me@tobias.gr \
--cc=romulasry@protonmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.