<?xml version="1.0" encoding="ANSI_X3.4-1968" standalone="no"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968" /><title>Chapter 15. How To Put Your Driver Into ALSA Tree</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /><link rel="home" href="index.html" title="Writing an ALSA Driver" /><link rel="up" href="index.html" title="Writing an ALSA Driver" /><link rel="prev" href="module-parameters.html" title="Chapter 14. Module Parameters" /><link rel="next" href="ch15s02.html" title="Driver with A Single Source File" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 15. How To Put Your Driver Into ALSA Tree</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="module-parameters.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch15s02.html">Next</a></td></tr></table><hr /></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="how-to-put-your-driver"></a>Chapter 15. How To Put Your Driver Into ALSA Tree</h1></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="section"><a href="how-to-put-your-driver.html#idm139882809910400">General</a></span></dt><dt><span class="section"><a href="ch15s02.html">Driver with A Single Source File</a></span></dt><dt><span class="section"><a href="ch15s03.html">Drivers with Several Source Files</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="idm139882809910400"></a>General</h2></div></div></div><p> So far, you've learned how to write the driver codes. And you might have a question now: how to put my own driver into the ALSA driver tree? Here (finally :) the standard procedure is described briefly. </p><p> Suppose that you create a new PCI driver for the card <span class="quote">“<span class="quote">xyz</span>”</span>. The card module name would be snd-xyz. The new driver is usually put into the alsa-driver tree, <code class="filename">alsa-driver/pci</code> directory in the case of PCI cards. Then the driver is evaluated, audited and tested by developers and users. After a certain time, the driver will go to the alsa-kernel tree (to the corresponding directory, such as <code class="filename">alsa-kernel/pci</code>) and eventually will be integrated into the Linux 2.6 tree (the directory would be <code class="filename">linux/sound/pci</code>). </p><p> In the following sections, the driver code is supposed to be put into alsa-driver tree. The two cases are covered: a driver consisting of a single source file and one consisting of several source files. </p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="module-parameters.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch15s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 14. Module Parameters </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Driver with A Single Source File</td></tr></table></div></body></html>
distrib
>
Fedora
>
18
>
x86_64
>
media
>
updates
>
by-pkgid
>
1a595394b241504ff370a8d12ebfcea7
>
files
>
5316
