All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: Audio miniconference schedule
Date: Wed, 24 Oct 2018 09:16:06 +0200	[thread overview]
Message-ID: <s5hsh0vq0g9.wl-tiwai@suse.de> (raw)
In-Reply-To: <20181002195849.GA23818@sirena.org.uk>

On Tue, 02 Oct 2018 21:58:49 +0200,
Mark Brown wrote:
> 
> As previously announced there's an audio miniconference happening on the
> 21st in Edinburgh:
> 
>    https://blog.sirena.org.uk/2018/09/19/2018-linux-audio-miniconfernce
> 
> (yes there is a typo in the URL).  A number of people have proposed
> topics so I just went through them and pulled them into a proposed
> agenda:
> 
>   - Virtualization (Liam)
>   - SoundWire (Liam)
>   - Byte controls (Vinod)
>   - GObject introspection for language bindings (Sakamoto-san)
>   - Integrating the ALSA control core (Sakamoto-san)
>   - AGL (Stephane/Ronan)
>   - Y2038 (broonie)
>   - AVB (Liam)
>   - DSPs (Liam)
>    - Sound Open Firmware
> 
> What do people think?  Any other topics?  There's still time to sign up
> if you're interested in attending, you can sign up right up to the day
> of the event.
> 
> It also seems good to mention that there's another audio event going on
> around ELC:
> 
>    https://blogs.gnome.org/uraeus/2018/09/24/getting-the-team-together-to-revolutionize-linux-audio/
> 
> which is a hackathon for a new userspace stack called PipeWire - if we
> have someone attending who knows about that I think it'd be good to talk
> about it too.

Thanks Mark for the great organization, I enjoyed the meeting in this
year very much (as always), and thanks Cirrus for a really nice venue!

If anyone can share the notes, it'd be great.


Takashi

  parent reply	other threads:[~2018-10-24  7:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02 19:58 Audio miniconference schedule Mark Brown
2018-10-05 10:20 ` Charles Keepax
2018-10-05 11:44   ` Mark Brown
2018-10-14  5:50     ` Patrick Lai
2018-10-15 10:24       ` Mark Brown
2018-10-16 20:48 ` Mark Brown
2018-10-16 21:16   ` Takashi Iwai
2018-10-17 19:12     ` Mark Brown
2018-10-18  5:53       ` Keyon Jie
2018-10-18 17:44         ` Mark Brown
2018-10-19  3:06           ` Keyon Jie
2018-10-19 14:35           ` Charles Keepax
2018-10-19 16:14             ` Jaroslav Kysela
2018-10-21  8:12               ` Jaroslav Kysela
2018-10-21  9:01                 ` Charles Keepax
2018-10-21  9:46                 ` Takashi Iwai
2018-10-18 10:12     ` Takashi Sakamoto
2018-10-24  7:16 ` Takashi Iwai [this message]
2018-10-24  7:30   ` Jaroslav Kysela
2018-10-24  7:33     ` Takashi Iwai
2018-10-24  8:11       ` Vinod
2018-10-24  8:51         ` Jaroslav Kysela
2018-10-24 10:08           ` Vinod
2018-10-24 10:24         ` Mark Brown
2018-10-24 10:16     ` Charles Keepax
2018-10-18 17:55 Mark Brown

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=s5hsh0vq0g9.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.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.