9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Gorka Guardiola <paurea@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] kw audio -- /dev/audio and friends
Date: Thu, 28 Oct 2010 15:07:26 +0200	[thread overview]
Message-ID: <AANLkTinzAJwzuTJay3p+w3DZ1bqvKQPHNe2QTK5R7oR+@mail.gmail.com> (raw)
In-Reply-To: <2577c9.f3659b0a.ZYYo.mx@tumtum.plumbweb.net>

On Thu, Oct 28, 2010 at 2:38 PM, Tristan Plumb <9p-st@imu.li> wrote:
>>> multiple inputs or outputs? if so, my first pass would be do something
>>> like what #l does: #l0, #l1, &c.
>> Wouldn't it be better to use #A0, #A1, ... for the case of multiple
>> audio devices instead of multiple in/outs in one device?
> that would make sense to me, though if there's a ethernet card that had
> multiple interfaces in an analogous way, #l0, #l1 would probably be used.
>
>> I don't see why control^(1 2 3 4 5 6) or in1, out1 are so ugly
>> (specially considering that this is just a potential "problem").
> the cs42l51 (the codec used on the openrd) audioctl looks like this:
>

I am guessing the io in audio does not mean in/out.
I think audioinctl audiooutctl is a little bit more readable.
At least do audinctl audoutctl if you are shooting for shortness.
--
- curiosity sKilled the cat



  reply	other threads:[~2010-10-28 13:07 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
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 [this message]
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=AANLkTinzAJwzuTJay3p+w3DZ1bqvKQPHNe2QTK5R7oR+@mail.gmail.com \
    --to=paurea@gmail.com \
    --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).