qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: chouhan.shreyansh2702@gmail.com,
	Gerd Hoffmann <kraxel@redhat.com>,
	Laurent Vivier <Laurent@vivier.eu>,
	Anton Yakovlev <anton.yakovlev@opensynergy.com>,
	qemu-devel@nongnu.org
Subject: Re: virtio-sound Google Summer of Code project?
Date: Tue, 31 Jan 2023 17:43:16 +0000	[thread overview]
Message-ID: <874js661lu.fsf@linaro.org> (raw)
In-Reply-To: <CAJSP0QWDMv2yFkORzKt+p45ykiY=AmZCbrS464nZOqEtOz-NqA@mail.gmail.com>


Stefan Hajnoczi <stefanha@gmail.com> writes:

> On Sun, 29 Jan 2023 at 17:10, Stefan Hajnoczi <stefanha@gmail.com> wrote:
>>
>> Hi Shreyansh, Gerd, and Laurent,
>> The last virtio-sound RFC was sent in February last year. It was a
>> spare time project. Understandably it's hard to complete the whole
>> thing on weekends, evenings, etc. So I wanted to suggest relaunching
>> the virtio-sound effort as a Google Summer of Code project.
>>
>> Google Summer of Code is a 12-week full-time remote work internship.
>> The intern would be co-mentored by some (or all) of us. The project
>> goal would be to merge virtio-sound with support for both playback and
>> capture. Advanced features for multi-channel audio, etc can be stretch
>> goals.
>>
>> I haven't looked in detail at the patches from February 2022, so I
>> don't know the exact state and whether there is enough work remaining
>> for a 12-week internship. What do you think?
>
> Adding Anton.
>
> I have updated the old wiki page for this project idea and added it to
> the 2023 ideas list:
> https://wiki.qemu.org/Internships/ProjectIdeas/VirtioSound
>
> Please let me know if you wish to co-mentor this project!

I'd be happy to help - although if someone was rust inclined I'd also be
happy to mentor a rust-vmm vhost-user implementation of VirtIO sound.

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2023-01-31 17:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-29 22:10 virtio-sound Google Summer of Code project? Stefan Hajnoczi
2023-01-31 15:35 ` Stefan Hajnoczi
2023-01-31 17:43   ` Alex Bennée [this message]
2023-01-31 18:19     ` Stefan Hajnoczi
2023-01-31 18:42       ` Alex Bennée
2023-01-31 18:45         ` Stefan Hajnoczi
2023-01-31 19:48       ` Marc-André Lureau
2023-01-31 20:29         ` Stefan Hajnoczi
2023-01-31 21:18           ` Marc-André Lureau
2023-01-31 21:41             ` Stefan Hajnoczi
2023-02-06  8:32   ` Anton Yakovlev
2023-02-06 14:22     ` Stefan Hajnoczi
2023-02-21 16:50       ` Stefan Hajnoczi

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=874js661lu.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=Laurent@vivier.eu \
    --cc=anton.yakovlev@opensynergy.com \
    --cc=chouhan.shreyansh2702@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).