From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
"Enrico Weigelt, metux IT consult" <lkml@metux.net>,
David Hildenbrand <david@redhat.com>, Greg KH <greg@kroah.com>,
Christoph Lameter <cl@gentwo.de>, Theodore Ts'o <tytso@mit.edu>,
Jiri Kosina <jikos@kernel.org>,
ksummit@lists.linux.dev,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>, netdev <netdev@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: Maintainers / Kernel Summit 2021 planning kick-off
Date: Fri, 18 Jun 2021 18:45:45 +0200 [thread overview]
Message-ID: <20210618184545.33ea3d47@coco.lan> (raw)
In-Reply-To: <20210618155829.GD4920@sirena.org.uk>
Em Fri, 18 Jun 2021 16:58:29 +0100
Mark Brown <broonie@kernel.org> escreveu:
> On Fri, Jun 18, 2021 at 10:32:14AM -0400, Steven Rostedt wrote:
> > On Fri, 18 Jun 2021 16:28:02 +0200
> > Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> > > What about letting people use the personal mic they're already
> > > carrying, i.e. a phone?
>
> > Interesting idea.
>
> > I wonder how well that would work in practice. Are all phones good
> > enough to prevent echo?
>
> Unless you get the latency for the WebRTC<->in room speaker down lower
> than I'd expect it to be I'd expect echo cancellation to have fun,
> though beam forming might reject a lot of in room noise including that -
> higher end modern phones are astonishingly good at this stuff. I'd not
> trust it to work reliably for all attendees though, it's the sort of
> thing where you'll get lots of per device variation.
The local audience should be listening to the in-room audio, in order
to avoid echo. Also, all local mics should be muted, if someone is
speaking from a remote location.
Yet, echo is unavoidable if a remote participant is speaking while
listening to the audio without headphones. If this ever happens, I
guess the moderator should cut the remote audio and ask the remote
participant to lower their speakers or use a headphone.
Thanks,
Mauro
next prev parent reply other threads:[~2021-06-18 16:45 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 15:28 Maintainers / Kernel Summit 2021 planning kick-off Theodore Ts'o
2021-04-28 10:29 ` Jiri Kosina
2021-04-30 21:48 ` Theodore Ts'o
2021-05-27 13:23 ` Christoph Lameter
2021-05-27 13:29 ` Greg KH
2021-05-28 14:58 ` James Bottomley
2021-05-28 15:11 ` Matthew Wilcox
2021-05-28 15:27 ` James Bottomley
2021-05-28 15:31 ` Laurent Pinchart
2021-05-28 15:44 ` James Bottomley
2021-05-28 15:55 ` Laurent Pinchart
2021-05-28 16:04 ` James Bottomley
2021-05-28 16:31 ` Laurent Pinchart
2021-05-28 15:42 ` Toke Høiland-Jørgensen
2021-06-09 10:37 ` David Hildenbrand
2021-06-09 19:23 ` James Bottomley
2021-06-11 10:58 ` Enrico Weigelt, metux IT consult
2021-06-10 18:07 ` Enrico Weigelt, metux IT consult
2021-06-10 18:23 ` Konstantin Ryabitsev
2021-06-10 18:39 ` Laurent Pinchart
2021-06-10 19:26 ` Steven Rostedt
2021-06-10 19:55 ` Shuah Khan
2021-06-10 20:02 ` Steven Rostedt
2021-06-10 20:20 ` Matthew Wilcox
2021-06-10 20:31 ` Steven Rostedt
2021-06-10 22:43 ` Toke Høiland-Jørgensen
2021-06-11 2:59 ` Willy Tarreau
2021-06-11 9:13 ` Mauro Carvalho Chehab
2021-06-11 9:51 ` Willy Tarreau
2021-06-18 13:46 ` Laurent Pinchart
2021-06-18 14:11 ` James Bottomley
2021-06-18 14:17 ` Steven Rostedt
2021-06-18 14:28 ` Geert Uytterhoeven
2021-06-18 14:32 ` Steven Rostedt
2021-06-18 14:45 ` Laurent Pinchart
2021-06-18 14:58 ` Geert Uytterhoeven
2021-06-18 15:14 ` Matthew Wilcox
2021-06-18 15:23 ` Steven Rostedt
2021-06-18 15:29 ` Geert Uytterhoeven
2021-06-18 15:34 ` Steven Rostedt
2021-06-18 15:36 ` Steven Rostedt
2021-06-18 16:33 ` Mauro Carvalho Chehab
2021-06-18 15:58 ` Mark Brown
2021-06-18 16:45 ` Mauro Carvalho Chehab [this message]
2021-06-18 14:46 ` James Bottomley
2021-06-22 22:33 ` Shuah Khan
2021-06-22 22:59 ` Laurent Pinchart
2021-06-22 23:33 ` Shuah Khan
2021-06-22 23:57 ` Shuah Khan
2021-06-23 0:06 ` Laurent Pinchart
2021-06-23 0:15 ` Steven Rostedt
2021-06-10 18:55 ` Linus Torvalds
2021-06-18 13:34 ` Enrico Weigelt, metux IT consult
2021-06-18 14:08 ` Steven Rostedt
2021-06-11 11:10 ` David Howells
2021-06-15 18:23 ` Enrico Weigelt, metux IT consult
2021-06-15 18:30 ` Matthew Wilcox
2021-06-15 18:34 ` Konstantin Ryabitsev
2021-06-15 18:40 ` Laurent Pinchart
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=20210618184545.33ea3d47@coco.lan \
--to=mchehab@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=broonie@kernel.org \
--cc=cl@gentwo.de \
--cc=david@redhat.com \
--cc=geert@linux-m68k.org \
--cc=greg@kroah.com \
--cc=jikos@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkml@metux.net \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=tytso@mit.edu \
/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).