From: Takashi Iwai <tiwai@suse.de>
To: Mike Mazarick <mazarick@bellsouth.net>
Cc: Paul Davis <paul@linuxaudiosystems.com>,
Lee Revell <rlrevell@joe-job.com>,
alsa-devel <alsa-devel@lists.sourceforge.net>,
Jole <jole@conwaycorp.net>,
Waldemar Haszlakiewicz <waldemar.haszlakiewicz@siol.net>,
Jay Schwichtenberg <jays@aracnet.com>
Subject: Re: GadgetLabs Driver for Alsa Linux
Date: Thu, 21 Oct 2004 11:35:13 +0200 [thread overview]
Message-ID: <s5hmzygh0ry.wl@alsa2.suse.de> (raw)
In-Reply-To: <LEEHJNBIEAAEJEHBEGDBOEJJCFAA.mazarick@bellsouth.net>
At Wed, 20 Oct 2004 15:53:28 -0400,
Mike Mazarick wrote:
>
> As mentioned, there is very little programming skill amoungst the 2 people
> (myself and jole), and the "testbed" will have to be Fedora Core 1 based,
> using Planet CCRMA. Naturally, if possible, it would be better to use alsa
> 1.X and kernel 2.6, but without a known good test system (one with
> functional apps, working drivers for other cards, etc), I'm not sure if
> proceeding with "the latest and greatest" would be the best choice.
In general, ALSA code is based on the 2.6 style. The support for the
older kernels are achieved through compatible wrappers. So, if you
write in the right way, it works in all platforms.
> Since the work hasn't really started, and the effort of building up a
> testbed compared to the effort of writing a driver is unknown at this time,
> I'm open to suggestions here. I was just a little afraid of getting stuck
> in the cul-de-sac of creating/debugging a test system; in addition, I noted
> the "how to write an alsa driver" notes were geared around alsa .9.X. How
> much work is involved in moving from .9 to 1.X?
Not much, but some basic APIs like the buffer allocation have been
changed. Also some clean-up's for the mainline kernel. For example,
the removal of snd_magic_* stuff, the new module parameters, etc.
I don't have a specific list of changes. Maybe you can find from the
diff of Documentation/DocBook/writing-an-alsa-driver.tmpl between
0.9.x and 1.0.x versions.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
prev parent reply other threads:[~2004-10-21 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 16:40 GadgetLabs Driver for Alsa Linux Mike Mazarick
2004-10-20 17:28 ` Lee Revell
2004-10-20 19:03 ` Paul Davis
2004-10-20 19:53 ` Mike Mazarick
2004-10-21 9:35 ` Takashi Iwai [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=s5hmzygh0ry.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=jays@aracnet.com \
--cc=jole@conwaycorp.net \
--cc=mazarick@bellsouth.net \
--cc=paul@linuxaudiosystems.com \
--cc=rlrevell@joe-job.com \
--cc=waldemar.haszlakiewicz@siol.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.