9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Devon H. O'Dell" <devon.odell@gmail.com>
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 11:00:36 -0400	[thread overview]
Message-ID: <9ab217670907140800r6cf4a460rff1902383b9805d3@mail.gmail.com> (raw)
In-Reply-To: <aeee2ada15cd35913ec268bfc1fcde4e@quanstro.net>

2009/7/14 erik quanstrom <quanstro@quanstro.net>:
> On Tue Jul 14 02:41:02 EDT 2009, sqweek@gmail.com wrote:
>>  I suspect the main inhibitor there is that (as I recall) it stomps
>> all over the existing soundblaster code. These days AC97 is probably
>> more desirable, but it would be nice to have them coexist.
>
> that's going to require thinking out how ac97 can provide a strict
> superset of sb.  as a first step, it would make sense for ac97 to
> bring it's own implementation of #A to the party.
>
> there are other sound models, it would be nice to design ac97's
> interface in such a way that it can work with other sound models.

Particularly Intel HDA (which supercedes AC97 and is what all new
machines are being shipped with now, essentially) and the various
chipset codecs on top of that. Plenty of BSDLed code on them and
plenty of documentation too.

--dho

> - erik
>
>



  reply	other threads:[~2009-07-14 15:00 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 [this message]
2009-07-14 16:28                   ` Dan Cross
2009-07-14 16:51                     ` Tim Newsham
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=9ab217670907140800r6cf4a460rff1902383b9805d3@mail.gmail.com \
    --to=devon.odell@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).