From: "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.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 11:57:42 +0200 [thread overview]
Message-ID: <543CF396.2080400@gr13.net> (raw)
In-Reply-To: <CAOFTvPL95AnzBx9BWMq59nk1Si5COR21dv2vwVi43Maje-zhEw@mail.gmail.com>
On 13.10.2014 16:06, Sergey Zhilkin wrote:
Hi,
> audio(3) - some docs. Look
> at http://plan9.bell-labs.com/wiki/plan9/supported_pc_hardware/index.html for
> supported hardware.
unfortunately, this doest contain any spec on the 9p interface.
> And sources of device (in /pc)
hmm, seems I have to reverse-engieer it ...
by the way: does it have any support for delays timestamps, etc?
cu
--
Enrico Weigelt,
metux IT consulting
+49-151-27565287
next prev parent reply other threads:[~2014-10-14 9:57 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 [this message]
2014-10-14 12:27 ` Anthony Sorace
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=543CF396.2080400@gr13.net \
--to=enrico.weigelt@gr13.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).