All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eliot Blennerhassett <linux@audioscience.com>
To: alsa-devel@alsa-project.org
Subject: AudioScience standalone alsa driver
Date: Tue, 31 May 2005 21:30:39 +1200	[thread overview]
Message-ID: <200505312130.39277.linux@audioscience.com> (raw)

Greetings.

I have started working on making a standalone version of the alsa driver for 
audioscience cards.

(By which I mean the whole driver source is in the alsa tree, and doesn't rely 
on separately built HPI driver).

As a start, I have just thrown together the current asihpi.c (alsa driver 
module) with all the files for the HPI driver and made a couple of tweaks so 
that there is only one module init.

Here is the code for the adventurous:
http://www.audioscience.com/internet/download/beta/asihpi-standalone0.02.tar.bz2
Unpack it in the pci subdirectory of driver source (warning: overwrites 
Makefile there).  Everything else is created in asihpi subdirectory.

I'm quite well aware that the code needs a lot of bashing into shape to get it 
acceptable to alsa let alone the kernel... 

Goals for the near future are
* Get the PCI detection and probing working like a normal driver
* Enable bus master audio transfer for cards that support it
* Avoid spinlock around every HPI message transaction

all constructive comments welcome. ;-)

-- 
Eliot Blennerhassett
AudioScience Inc.


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005

                 reply	other threads:[~2005-05-31  9:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200505312130.39277.linux@audioscience.com \
    --to=linux@audioscience.com \
    --cc=alsa-devel@alsa-project.org \
    /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.