From: "Lee Revell" <rlrevell@joe-job.com>
To: Martin Wilson <mpw473@bham.ac.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Hello/EMU 0404 USB driver
Date: Tue, 6 Mar 2007 18:23:25 -0500 [thread overview]
Message-ID: <75b66ecd0703061523r152b9476lde29161fa57107f0@mail.gmail.com> (raw)
In-Reply-To: <45EDF4C7.30704@bham.ac.uk>
On 3/6/07, Martin Wilson <mpw473@bham.ac.uk> wrote:
> Hi all,
>
> a EMU
> 0404 USB which is a very good card. I would like to use something like
> Ubuntu studio instead of OSX for making music, however the sticking
> point is the driver for this particular piece of hardware. Looking
> around forums it looks like I'm not the only one who has come across
> this problem, so I have the following questions...
> 1. What is the biggest obstacle for this driver becoming a reality?
If the device is class compliant (aka does not require a driver to be
installed on OSX or Windows) then it's very easy. Otherwise it's very
hard without detailed hardware specs.
> 2. Do creative play nicely with releasing the specifics of how their
> hardware works?
Sometimes. They've helped with the EMU1212 series and CA0106 (SBLive!
24 bit) but won't help with the X-Fi.
> 3. What is the best way to learn how to write drivers for sound cards
> (I've ordered the 'Linux Device drivers' book for an overview)?
Read "Writing an ALSA driver" and refer to the source code of existing
drivers such as snd-usb-audio.
Lee
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2007-03-06 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 23:09 Hello/EMU 0404 USB driver Martin Wilson
2007-03-06 23:21 ` Tobin Davis
2007-03-06 23:23 ` Lee Revell [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=75b66ecd0703061523r152b9476lde29161fa57107f0@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=mpw473@bham.ac.uk \
/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