Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Eliot Blennerhassett <bigblen@icqmail.com>
Cc: alsa-devel@lists.sourceforge.net, eliot@blennerhassett.gen.nz
Subject: Re: To: ALSA Soundcard Matrix maintainer
Date: Mon, 05 May 2003 17:30:35 +0900	[thread overview]
Message-ID: <3EB6212B.7040609@boosthardware.com> (raw)
In-Reply-To: 20030501191340.13435.h003.c012.wm@mail.icqmail.com.criticalpath.net

Eliot Blennerhassett wrote:
> Hello,
> 
> according to the ALSA Soundcard Matrix page:
> "Corrections should be sent to the alsa-devel mailing
> list."
> 
> so heres one:
> AudioScience cards are missing from the list:
> All cards from
> http://www.audioscience.com/internet/products/products.htm
> except ASI2214 are candidates for an ALSA driver.
> 
> Summary:
> 
> Based on TI TMS320C67xx DSP
> ASI6012
> ASI6122
> ASI6114
> ASI6118
> ASI6244
> ASI5111
> 
> Based on Motorola DSP56301 DSP
> ASI4215
> ASI4346
> ASI4344
> ASI4342
> 
> These would currently be highlighted green or grey in
> the matrix.
> 

Added.


-- 
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

Being on stage with the band in front of crowds shouting, "Get off! No! 
We want normal music!", I think that was more like acting than anything 
I've ever done.

Goldie, 8 Nov, 2002
The Scotsman



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      parent reply	other threads:[~2003-05-05  8:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02  2:13 To: ALSA Soundcard Matrix maintainer Eliot Blennerhassett
2003-05-02  8:37 ` Giuliano Pochini
2003-05-05  8:31   ` Patrick Shirkey
2003-05-05  8:30 ` Patrick Shirkey [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=3EB6212B.7040609@boosthardware.com \
    --to=pshirkey@boosthardware.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=bigblen@icqmail.com \
    --cc=eliot@blennerhassett.gen.nz \
    /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