All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Hans de Ruiter <hans@keasigmadelta.com>
Cc: qemu-devel@nongnu.org,  Gerd Hoffmann <kraxel@redhat.com>,
	Manos Pitsidianakis <manos.pitsidianakis@linaro.org>,
	Takahiro Akashi <takahiro.akashi@linaro.org>,
	Gurchetan Singh <gurchetansingh@chromium.org>
Subject: Re: QEMU Virtio GPU features status & roadmap?
Date: Wed, 08 Nov 2023 15:14:01 +0000	[thread overview]
Message-ID: <878r789t1i.fsf@draig.linaro.org> (raw)
In-Reply-To: <65466251-5c0c-90d0-c482-29ebc4e16a20@keasigmadelta.com> (Hans de Ruiter's message of "Tue, 17 Oct 2023 00:48:00 +0000 (3 weeks, 1 day, 14 hours ago)")

Hans de Ruiter <hans@keasigmadelta.com> writes:

(Cc: Adding others with interest in VirtIO GPUs to the thread)

> Hi,
>
> I'm working on Virtio GPU drivers for AmigaOS, and would like to know
> what features are currently stable enough to use. Looking at the
> master QEMU branch, both Virgl and blob resources are supported, but
> NOT at the same time. Is the ability to use both simultaneously coming
> soon?
>
> Also, what's the state of Venus/Vulkan support? Surveying various
> forks/branches, it looks very experimental and subject to change.
>
> I have the added difficulty that the AmigaOS Picasso96 driver API
> expects direct CPU access to all of VRAM, and likes to peek/poke
> directly into the bitmaps. That's clearly not possible without blob
> resources, or shared memory (not entirely sure what the shared memory
> feature is for). This is why I want to know what features are stable
> or coming soon.
>
> regards,
> Hans
>
> [2. application/pgp-keys; publickey - hans@keasigmadelta.com - 4293c311.asc]...

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


      parent reply	other threads:[~2023-11-08 15:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17  0:48 QEMU Virtio GPU features status & roadmap? Hans de Ruiter
2023-11-08  9:03 ` Antonio Caggiano
2023-11-08 11:07   ` Marc-André Lureau
2023-11-08 13:43     ` Antonio Caggiano
2023-11-09  8:13     ` Huang Rui
2023-11-09 13:17       ` Hans de Ruiter
2023-11-08 15:14 ` Alex Bennée [this message]

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=878r789t1i.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=gurchetansingh@chromium.org \
    --cc=hans@keasigmadelta.com \
    --cc=kraxel@redhat.com \
    --cc=manos.pitsidianakis@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=takahiro.akashi@linaro.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 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.