From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: colbyt <colby@colbyt.com>, devel@spectrum-os.org
Subject: Re: [RFC PATCH 4/6] Revert "host/rootfs: Makefile: don't use QEMU with GL"
Date: Sun, 12 Jul 2026 20:05:34 +0200 [thread overview]
Message-ID: <87ik6kdqxd.fsf@alyssa.is> (raw)
In-Reply-To: <ac6e1299-953c-4b08-84c1-52c6bd196753@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
Demi Marie Obenour <demiobenour@gmail.com> writes:
> On 7/10/26 15:59, Alyssa Ross wrote:
>> This reverts commit 1ffefee2ae391e934a265294164596b341b2c77a.
>>
>> This was disabled because it wasn't necessary at the time, and enabled
>> development on systems without GPU acceleration. COSMIC needs it
>> though, so we have to raise our requirement.
>
> Will this break running spectrum on systems with no GPU?
>
> I generally do my development on a remote server that doesn't have
> a GPU, as it is able to perform builds very quickly.
Can they use llvmpipe?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2026-07-12 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 19:59 [RFC PATCH 0/6] host/rootfs: switch from Weston to cosmic-comp Alyssa Ross
2026-07-10 19:59 ` [RFC PATCH 1/6] pkgs: s6: fix s6-notify-fd-from-socket Alyssa Ross
2026-07-10 19:59 ` [RFC PATCH 2/6] pkgs: cosmic-comp: support custom socket path Alyssa Ross
2026-07-10 19:59 ` [RFC PATCH 3/6] Revert "host/rootfs/Makefile: don't pass -display to QEMU" Alyssa Ross
2026-07-10 19:59 ` [RFC PATCH 4/6] Revert "host/rootfs: Makefile: don't use QEMU with GL" Alyssa Ross
2026-07-10 20:49 ` Demi Marie Obenour
2026-07-12 18:05 ` Alyssa Ross [this message]
2026-07-13 17:02 ` Demi Marie Obenour
2026-07-10 19:59 ` [RFC PATCH 5/6] host/rootfs: make run: use virgl virtio-gpu Alyssa Ross
2026-07-10 19:59 ` [RFC PATCH 6/6] host/rootfs: switch from Weston to cosmic-comp 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=87ik6kdqxd.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=colby@colbyt.com \
--cc=demiobenour@gmail.com \
--cc=devel@spectrum-os.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.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
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).