From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] Fix nusb/audio /dev entries
Date: Wed, 20 Dec 2023 09:19:37 -0800 [thread overview]
Message-ID: <ZYMiKbk6pTfDe93V@wopr> (raw)
In-Reply-To: <7408ADB29853D60644FA44A89191C3B8@wopr.sciops.net>
On Wed, Dec 20, 2023 at 05:44:35PM +0100, qwx@sciops.net wrote:
> - If more devices are plugged in, only the last one would be used,
> switching output yet again
Not my circus, but isn't this how people would expect things to work?
If you plug in an audio device, surely you expect that to become the
active device?
> - If the usb device is disconnected, audio will break for programs
> currently writing to /dev/audio and they would have to reopen it
This sounds like a bug worth fixing -- we need aan for /dev/audio. We
can call it aaa.
khm
next prev parent reply other threads:[~2023-12-20 17:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 11:23 Arne Meyer
2023-12-20 16:44 ` qwx
2023-12-20 17:19 ` Kurt H Maier [this message]
2023-12-20 17:47 ` qwx
2023-12-20 17:51 ` Kurt H Maier
2023-12-20 18:11 ` qwx
2023-12-20 18:53 ` Arne Meyer
2023-12-20 23:10 ` qwx
2023-12-21 2:47 ` Sigrid Solveig Haflínudóttir
2023-12-21 7:53 ` hiro
2023-12-21 20:12 ` Arne Meyer
2023-12-21 20:48 ` hiro
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=ZYMiKbk6pTfDe93V@wopr \
--to=khm@sciops.net \
--cc=9front@9front.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 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).