From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] audio device interface
Date: Tue, 14 Oct 2014 08:27:09 -0400 [thread overview]
Message-ID: <EDF79552-85C3-4B5D-AA26-C48D7F9C70C0@9srv.net> (raw)
In-Reply-To: <543CF396.2080400@gr13.net>
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
On Oct 14, 2014, at 5:57 , Enrico Weigelt, metux IT consult <enrico.weigelt@gr13.net> wrote:
> unfortunately, this doest contain any spec on the 9p interface.
The 9p interface is just 9p; there's nothing special for audio. Then audio(3) will answer your questions about what can be read from or written to each file.
> by the way: does it have any support for delays timestamps, etc?
audio(3) answers this (by omission). It describes what you can write to the files.
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 169 bytes --]
prev parent reply other threads:[~2014-10-14 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 13:40 Enrico Weigelt, metux IT consult
2014-10-13 14:06 ` Sergey Zhilkin
2014-10-14 9:57 ` Enrico Weigelt, metux IT consult
2014-10-14 12:27 ` Anthony Sorace [this message]
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=EDF79552-85C3-4B5D-AA26-C48D7F9C70C0@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).