From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] kw audio -- /dev/audio and friends
Date: Wed, 27 Oct 2010 14:58:27 -0400 [thread overview]
Message-ID: <6CCD7B4C-B298-4F85-91CD-DCD750E946D9@9srv.net> (raw)
In-Reply-To: <2577c9.12b19530.giyO.mx@tumtum.plumbweb.net>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
I've misplaced my USB audio kit, but I'm reasonably sure I read from /dev/audio (and a cursory reading of the source suggests that ought to work). Is there any reason to do otherwise? I don't know what audioin is intended to buy. Given that it's never been in audio(3), I'm not sure it's important to support it.
It's unfortunate that volume and audioctl don't support the same language. Don't add another. It's pretty easy to handle both; see /sys/src/cmd/usb/audio/audiofs.c. The one for audioctl is reasonably regular and comprehensive; it'd be nice to standardize our audio interfaces around that.
I'm more interested in audiostat. I don't see that in the usb implementation, and I'm not clear on whether it could be provided there. Anyone know? Should audio programs treat that as optional?
"deprecation" in unix is a mess, where things can stay "deprecated" for ages. it'd be nice to be able to say "/dev/volume (or /dev/eia0status) was a mistake; here's a backwards-compatible improvement, and the old stuff goes away in 6 months."
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2010-10-27 18:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 14:06 Tristan Plumb
2010-10-26 14:31 ` Russ Cox
2010-10-26 14:49 ` erik quanstrom
2010-10-27 12:30 ` Tristan Plumb
2010-10-27 12:50 ` Lucio De Re
2010-10-27 13:29 ` erik quanstrom
2010-10-27 14:15 ` Tristan Plumb
2010-10-27 18:58 ` Anthony Sorace [this message]
2010-10-27 20:07 ` Skip Tavakkolian
2010-10-27 21:05 ` David Leimbach
2010-10-28 0:11 ` Tristan Plumb
2010-10-28 3:01 ` Anthony Sorace
2010-10-28 7:53 ` yy
2010-10-28 12:38 ` Tristan Plumb
2010-10-28 13:07 ` Gorka Guardiola
2010-10-28 13:26 ` Tristan Plumb
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=6CCD7B4C-B298-4F85-91CD-DCD750E946D9@9srv.net \
--to=a@9srv.net \
--cc=9fans@9fans.net \
/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).