patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: vadik likholetov <vadim.likholetov@unikie.com>
To: Alyssa Ross <alyssa.ross@unikie.com>
Cc: devel@spectrum-os.org, Puck Meerburg <puck@puckipedia.com>,
	Ville Ilvonen <ville.ilvonen@unikie.com>
Subject: Re: Attempting to use virtio-gpu on Apple Silicon
Date: Thu, 08 Dec 2022 10:53:08 +0200	[thread overview]
Message-ID: <K0EKMR.PFTJI02LYSU52@unikie.com> (raw)
In-Reply-To: <20221207115440.a3wm4h6lr4gvctpf@x220>

[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]

On ke, joulu 7 2022 at 11.54.40 +00:00:00, Alyssa Ross 
<alyssa.ross@unikie.com> wrote:
> This Mesa tree was more recent than the one in our Wayland branch, so 
> I
> needed to backport some Nixpkgs changes to be able to build it.  I
> cherry-picked the following commits:
> 
>     952dbf0a4ae mesa: build more Vulkan drivers on aarch64-linux
>     906947555d2 mesa: 22.2.2 -> 22.2.3
>     7a222ffee31 mesa: fix build on darwin
>     8d7db0597f9 mesa: rm unused attributes
>     aa8d873a4eb mesa: 22.2.1 -> 22.2.2
>     33a5279d620 mesa: add vulkanLayers option and default it to 
> device-select, overlay
>     b4b99f16da9 mesa: re-enable video-codecs
>     445887f636e mesa: 22.1.7 -> 22.2.1
>     dd3fc581129 mesa: Install radv override configs into $out
>     40ee116f25a spirv-llvm-translator_14: init at 14.0.0
>     ea2ca5e6394 spirv-llvm-translator: version depends on llvm version

If you're going to update Mesa package -- I could try to enable 
acceleration in waypipe if I have Mesa build ?

-- 
vadik likholetov


[-- Attachment #2: Type: text/html, Size: 1238 bytes --]

  reply	other threads:[~2022-12-08  8:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07 11:54 Alyssa Ross
2022-12-08  8:53 ` vadik likholetov [this message]
2022-12-09 10:14   ` Alyssa Ross

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=K0EKMR.PFTJI02LYSU52@unikie.com \
    --to=vadim.likholetov@unikie.com \
    --cc=alyssa.ross@unikie.com \
    --cc=devel@spectrum-os.org \
    --cc=puck@puckipedia.com \
    --cc=ville.ilvonen@unikie.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://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

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 NNTP newsgroup(s).