From: Gurchetan Singh <gurchetansingh@chromium.org>
To: Alyssa Ross <hi@alyssa.is>
Cc: qemu-devel@nongnu.org, marcandre.lureau@redhat.com,
akihiko.odaki@gmail.com, ray.huang@amd.com,
alex.bennee@linaro.org, shentey@gmail.com, ernunes@redhat.com,
manos.pitsidianakis@linaro.org, mark.cave-ayland@ilande.co.uk,
thuth@redhat.com
Subject: Re: [PATCH v15 0/9] rutabaga_gfx + gfxstream
Date: Fri, 19 Jan 2024 09:52:53 -0800 [thread overview]
Message-ID: <CAAfnVBmiaesEQkZOk4zf08JTh-WM3tqNT8RoyaL=49Lm--5HSQ@mail.gmail.com> (raw)
In-Reply-To: <87wms9d0fi.fsf@alyssa.is>
On Tue, Jan 16, 2024 at 2:42 AM Alyssa Ross <hi@alyssa.is> wrote:
>
> Hi Gurchetan,
>
> Gurchetan Singh <gurchetansingh@chromium.org> writes:
>
> > - As mentioned in v14:
> > * AEMU: d6e6b99 "Delete VpxFrameParser.cpp"
> > * gfxstream: 2131f78d Merge "gfxstream: add egl & gles deps.."
> >
> > are the proposed v.0.1.2 release points. If those commits are sufficient
> > for packaging AEMU + gfxstream, let me know and I'll have official release
> > tags made. If additional changes are required for packaging, let me know
> > as well.
>
> Were these releases ever made?
Thanks for the reminder. I did make a request to create the release
tags, but changes were requested by Fedora packaging effort:
https://bugzilla.redhat.com/show_bug.cgi?id=2242058
https://bugzilla.redhat.com/show_bug.cgi?id=2241701
So the request was canceled, but never re-requested. I'll fire off
another request, with:
gfxstream: 23d05703b94035ac045df60823fb1fc4be0fdf1c ("gfxstream:
manually add debug logic")
AEMU: dd8b929c247ce9872c775e0e5ddc4300011d0e82 ("aemu: improve licensing")
as the commits. These match the Fedora requests, and the AEMU one has
been merged into Fedora already it seems.
>
>
> The gfxstream ref mentioned here isn't compatible with
> v0.1.2-rutabaga-release, because it no longer provides logging_base.pc,
> and this email is the last mention I can find of these releases.
>
> In Nixpkgs, I've gone for packaging gfxstream and aemu with your initial
> proposed release points, which works fine, but it would be great to have
> this clearer upstream.
next prev parent reply other threads:[~2024-01-19 17:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 20:44 [PATCH v15 0/9] rutabaga_gfx + gfxstream Gurchetan Singh
2023-10-03 20:44 ` [PATCH v15 1/9] virtio: Add shared memory capability Gurchetan Singh
2023-10-03 20:44 ` [PATCH v15 2/9] virtio-gpu: CONTEXT_INIT feature Gurchetan Singh
2023-10-03 20:44 ` [PATCH v15 3/9] virtio-gpu: hostmem Gurchetan Singh
2023-10-03 20:44 ` [PATCH v15 4/9] virtio-gpu: blob prep Gurchetan Singh
2023-10-03 20:44 ` [PATCH v15 5/9] gfxstream + rutabaga prep: added need defintions, fields, and options Gurchetan Singh
2023-10-03 20:44 ` [PATCH v15 6/9] gfxstream + rutabaga: add initial support for gfxstream Gurchetan Singh
2023-10-04 8:19 ` Marc-André Lureau
2023-10-03 20:44 ` [PATCH v15 7/9] gfxstream + rutabaga: meson support Gurchetan Singh
2023-10-03 20:44 ` [PATCH v15 8/9] gfxstream + rutabaga: enable rutabaga Gurchetan Singh
2023-10-03 20:45 ` [PATCH v15 9/9] docs/system: add basic virtio-gpu documentation Gurchetan Singh
2024-01-16 10:42 ` [PATCH v15 0/9] rutabaga_gfx + gfxstream Alyssa Ross
2024-01-19 17:52 ` Gurchetan Singh [this message]
2024-01-19 21:13 ` Alyssa Ross
2024-01-19 22:53 ` Gurchetan Singh
2024-01-20 12:18 ` Alyssa Ross
2024-01-26 2:15 ` Gurchetan Singh
2024-01-26 14:22 ` Alyssa Ross
2024-01-31 3:10 ` Gurchetan Singh
2024-02-14 0:48 ` Gurchetan Singh
2024-03-02 14:37 ` rutabaga 0.1.3 Alyssa Ross
2024-03-05 0:23 ` Gurchetan Singh
2024-03-22 21:20 ` 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='CAAfnVBmiaesEQkZOk4zf08JTh-WM3tqNT8RoyaL=49Lm--5HSQ@mail.gmail.com' \
--to=gurchetansingh@chromium.org \
--cc=akihiko.odaki@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=ernunes@redhat.com \
--cc=hi@alyssa.is \
--cc=manos.pitsidianakis@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=ray.huang@amd.com \
--cc=shentey@gmail.com \
--cc=thuth@redhat.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.
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).