From: Takashi Iwai <tiwai@suse.de>
To: mjander@embedded.cl
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: New driver
Date: Wed, 05 Mar 2003 09:48:50 +0100 [thread overview]
Message-ID: <s5hn0kafbbh.wl@alsa2.suse.de> (raw)
In-Reply-To: <200303041935.AA192217402@embedded.cl>
Hi,
At Tue, 4 Mar 2003 19:35:35 -0400,
mjander wrote:
>
> Hi,
>
> I started writing a new driver for the Aureal Vortex soundcards.
wow, how did you get hardware information?
> Now the howto is pretty good, and the basic stuff is nearly
> complete, but
> how do i integrate my driver into the configure scripts,
> Makefiles, and
> all sorts of thingiees that makee up the tree ?
>
> I placed the driver (several files) into the directory
> "pci/vortex". I managed to get the configure script to recognice
> the "vortex" card fiddling in the acinclude.m4 file, but when
> i do "make" it doesnt compile the files in "/pci/vortex". This
> directory has a apropiate makefile (i took the one of the
> emu10k1 an d modiifyed it).
>
> What is the "official" procedure to integrate my driver ?
ah, that's not on the howto yet :)
first, the test drivers should be put into alsa-driver tree. they
will be brought up to alsa-kernel tree eventually and submitted to
linux 2.5 kernel later.
in your case, alsa-driver/pci/vx222 or alsa-driver/pci/pdplus would be
a good example.
add the vortex directory to extra-subdir-y in alsa-driver/pci/Makefile:
extra-subdir-y := pdplus vx222 vortex
create a new Makefile in alsa-driver/pci/vortex (see vx222 or pdplus
Makefile).
add the definition to alsa-driver/utils/Modules.dep like below:
%dir linux/sound/pci/vortex
|snd-vortex snd-pcm ...
where the second and later arguments are dependent lowlevel modules.
and also define the necessary dependency in
alsa-driver/acore/Makefile or whererever the dependent lowlevel
modules exist.
finally, run ./cvscompile to regenerate the configure script, etc.
ciao,
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-03-05 8:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 23:35 New driver mjander
2003-03-04 23:27 ` Paul Davis
2003-03-05 8:48 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-24 0:09 Ian Molton
2004-08-26 19:54 ` Ian Molton
2004-08-26 20:52 ` Josh Boyer
2004-02-19 0:27 new driver Doelfel, Hardy
2004-02-18 23:39 Tomita, Haruo
2004-02-18 23:57 ` Ken Schneider
2004-02-19 5:32 ` Jeff Garzik
2004-02-18 8:51 Tomita, Haruo
2004-02-18 12:29 ` Arjan van de Ven
2004-02-18 23:29 ` Ken Schneider
2004-02-15 0:06 Ken Schneider
2004-02-15 9:29 ` Christoph Hellwig
2004-02-15 10:57 ` Arjan van de Ven
2004-02-15 20:35 ` Jeff Garzik
2000-12-28 21:19 New driver Pixel
2000-12-28 21:53 ` Keith Owens
2000-12-29 2:49 ` Pixel
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=s5hn0kafbbh.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=mjander@embedded.cl \
/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.