9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tim Newsham <newsham@lava.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan9 as an everyday OS
Date: Tue, 14 Jul 2009 06:51:02 -1000	[thread overview]
Message-ID: <Pine.BSI.4.64.0907140647260.5249@malasada.lava.net> (raw)
In-Reply-To: <aa7e41150907140928h40992fc5vdcb91484dfdc5643@mail.gmail.com>

> However, I still think this is worthwhile just to provide (a) a
> standard interface for audio devices (e.g., /dev/audioctl always
> accepts the same messages to set volume, input levels, etc), and (b)
> to have a single kernel support more than one type of audio device
> (imagine a network where you actually have an SB16 plus a bunch of
> AC97 devices and some of these HCI things that Devon mentioned-one 9pc
> should be able to support them all).

I was looking at audio interfaces a little lately and
I noticed that inferno's audio device uses different
conventions and seems to be more complete.  It might
be worthwhile to shoot for an interface like that.

>        - Dan C.

Tim Newsham
http://www.thenewsh.com/~newsham/



  reply	other threads:[~2009-07-14 16:51 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-10 16:05 Lorenzo Bolla
2009-07-10 16:30 ` André Günther
2009-07-10 16:52   ` John Floren
2009-07-10 17:07     ` Noah Evans
2009-07-10 17:27       ` Joseph Stewart
2009-07-10 17:46         ` john
2009-07-10 17:49           ` Don Bailey
2009-07-10 21:06           ` J.R. Mauro
2009-07-10 21:35             ` Devon H. O'Dell
2009-07-10 21:46               ` J.R. Mauro
2009-07-10 21:59               ` Jason Catena
2009-07-10 20:44         ` Noah Evans
2009-07-10 20:56           ` Don Bailey
2009-07-10 17:30       ` hiro
2009-07-10 17:27     ` Ethan Grammatikidis
2009-07-10 16:44 ` maht
2009-07-10 17:23 ` Andrés Domínguez
2009-07-10 17:26   ` Don Bailey
2009-07-11  6:26   ` Uriel
2009-07-11 10:03     ` Lorenzo Bolla
2009-07-10 17:25 ` Ethan Grammatikidis
2009-07-10 17:45   ` Ethan Grammatikidis
2009-07-10 17:50     ` john
2009-07-10 21:52   ` cinap_lenrek
2009-07-10 22:01     ` john
2009-07-10 22:09       ` cinap_lenrek
2009-07-10 22:10         ` john
2009-07-10 22:37           ` cinap_lenrek
2009-07-10 22:48           ` Jack Johnson
2009-07-10 22:58           ` Andreas Eriksen
2009-07-12  8:20             ` Francisco J Ballesteros
2009-07-11 10:13         ` sqweek
2009-07-11 18:08           ` Uriel
2009-07-13  8:29             ` sqweek
2009-07-11 20:41           ` cinap_lenrek
2009-07-13 17:09         ` Markus Sonderegger
2009-07-13 11:22           ` erik quanstrom
2009-07-13 11:34             ` Bela Valek
2009-07-14  6:39               ` sqweek
2009-07-14 13:01                 ` erik quanstrom
2009-07-14 15:00                   ` Devon H. O'Dell
2009-07-14 16:28                   ` Dan Cross
2009-07-14 16:51                     ` Tim Newsham [this message]
2009-07-14 17:29                       ` Devon H. O'Dell
2009-07-14  7:26             ` markus
2009-07-10 17:28 ` Jack Johnson

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=Pine.BSI.4.64.0907140647260.5249@malasada.lava.net \
    --to=newsham@lava.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).