static/netbsd/man4/eap.4 4.html


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77

<table class="head">
  <tr>
    <td class="head-ltitle">EAP(4)</td>
    <td class="head-vol">Device Drivers Manual</td>
    <td class="head-rtitle">EAP(4)</td>
  </tr>
</table>
<div class="manual-text">
<section class="Sh">
<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1>
<p class="Pp"><code class="Nm">eap</code> &#x2014; <span class="Nd">AudioPCI
    audio device driver</span></p>
</section>
<section class="Sh">
<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1>
<p class="Pp"><code class="Cd">eap* at pci? dev ? function ?</code>
  <br/>
  <code class="Cd">options EAP_USE_BOTH_DACS</code></p>
<p class="Pp">
  <br/>
  <code class="Cd">audio* at audiobus?</code>
  <br/>
  <code class="Cd">joy* at eap?</code>
  <br/>
  <code class="Cd">midi* at eap?</code></p>
</section>
<section class="Sh">
<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
<p class="Pp">The <code class="Nm">eap</code> driver provides support for the
    Ensoniq AudioPCI and Creative Labs SoundBlaster PCI series of audio cards.
    All models based on the ES1370, ES1371, and ES1373 chips are supported.</p>
<p class="Pp">By specifying:</p>
<p class="Pp"></p>
<div class="Bd Bd-indent"><code class="Cd">options
  EAP_USE_BOTH_DACS</code></div>
<p class="Pp">a second audio device is attached. This can be used for audio
    output simultaneously with the primary DAC. You can use it simply by
    directing audio output to the additional <span class="Pa">/dev/audioX</span>
    device associated with it.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE
  ALSO</a></h1>
<p class="Pp"><a class="Xr">ac97(4)</a>, <a class="Xr">audio(4)</a>,
    <a class="Xr">joy(4)</a>, <a class="Xr">midi(4)</a>,
    <a class="Xr">pci(4)</a></p>
</section>
<section class="Sh">
<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1>
<p class="Pp">The <code class="Nm">eap</code> device driver appeared in
    <span class="Ux">NetBSD 1.4</span>.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="CAVEATS"><a class="permalink" href="#CAVEATS">CAVEATS</a></h1>
<p class="Pp">The joystick port hardware works by emulating a legacy
    <a class="Xr">isa(4)</a> joystick port, bypassing the
    <a class="Xr">pci(4)</a> bus method for address allocation. This is unlikely
    to work on PCI busses other than the primary one. There is also a
    possibility for conflicts with real ISA devices because the PCI bus is
    probed before ISA. Use with caution.</p>
<p class="Pp">The <code class="Dv">EAP_USE_BOTH_DACS</code> option is rather
    redundant after the introduction of the in-kernel audio mixer, and may be
    removed in a future release. It is possible that it could be used to
    accelerate mixing streams by taking advantage of the hardware's features,
    but currently the additional (small) overhead of the kernel mixer is
    impossible to bypass, since <span class="Ux">NetBSD</span> no longer allows
    userspace software to write directly to audio hardware. The
    <code class="Nm">eap</code> hardware only features one clock, so generally
    the second audio device must be configured in the same way as the first.</p>
</section>
</div>
<table class="foot">
  <tr>
    <td class="foot-date">May 16, 2024</td>
    <td class="foot-os">NetBSD 10.1</td>
  </tr>
</table>