All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eliot Blennerhassett" <bigblen@xtra.co.nz>
To: alsa-devel@lists.sourceforge.net
Subject: Writing a driver for this card: your thoughts?
Date: Thu, 6 Jun 2002 11:03:19 +1200	[thread overview]
Message-ID: <3CFF4177.16823.43BD597@localhost> (raw)

Those of you who read linux-audio-dev will recognise the following. 
Thanks for your replies over there. 

It should have gone primarily to alsa-devel, but somehow didn't. 
========================== 

Hello, 

I work for AudioScience (www.audioscience.com) 

We make excellent (how could I say otherwise) audio cards. 

The emphasis within the company has been on microsoft windows drivers. 
... but we have a Linux driver, currently proprietary, closed source, that 
exposes this 
(http://www.audioscience.com/internet/download/spchpi.pdf) API. 

(It may be possible to release the host side code, but never the DSP code 
on the cards.) 

I think it would be much better if we had an ALSA driver. 

I'd like some idea how hard it would be to write an ALSA driver either as a 
compatibility layer on top of our existing driver, or from the ground up.  I 
realise that this is rather a broad question, so please consider this an 
invitation to enter discussion, rather than a request for you to go off and 
do a lot of work for me. 

Oh - what do you think of the cards' feature set?  


Some distinctive things about our cards (not all have all features) - they 
have on board DSP.  Code is downloaded by the driver. - they have a lot of 
on board buffer memory (hundreds of K at least) - on board DSP handles 
decompression/compression - mixing - samplerate conversion or multiple 
outputs at different rates - analog and digital audio I/O, balanced drivers 


=============================================
====
Eliot Blennerhassett                       *:-{)>
AudioScience, Inc. (New Zealand Office)
6 Centaurus Rd             
Christchurch 8002          Mobile: +64 21 1183531
New Zealand                Ph/fax: +64  3 3327818
eblennerhassett@audioscience.com
<http://www.audioscience.com>
=============================================
====


_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

             reply	other threads:[~2002-06-05 23:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05 23:03 Eliot Blennerhassett [this message]
2002-06-06 19:04 ` Writing a driver for this card: your thoughts? Dan Hollis
2002-06-07  1:00   ` Eliot Blennerhassett
2002-06-07  1:39     ` Dan Hollis
2002-06-10 14:20 ` Takashi Iwai

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=3CFF4177.16823.43BD597@localhost \
    --to=bigblen@xtra.co.nz \
    --cc=alsa-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.