2 If you have a sound card in your computer, i.e. if it can say more
3 than an occasional beep, say Y. Be sure to have all the information
4 about your sound card and its configuration down (I/O port,
5 interrupt and DMA channel), because you will be asked for it.
7 You want to read the Sound-HOWTO, available from
8 <http://www.linuxdoc.org/docs.html#howto>. General information about
9 the modular sound system is contained in the files
10 <file:Documentation/sound/Introduction>. The file
11 <file:Documentation/sound/README.OSS> contains some slightly
12 outdated but still useful information as well.
14 If you have a PnP sound card and you want to configure it at boot
15 time using the ISA PnP tools (read
16 <http://www.roestock.demon.co.uk/isapnptools/>), then you need to
17 compile the sound card support as a module ( = code which can be
18 inserted in and removed from the running kernel whenever you want)
19 and load that module after the PnP configuration is finished. To do
20 this, say M here and read <file:Documentation/modules.txt> as well
21 as <file:Documentation/sound/README.modules>; the module will be
24 I'm told that even without a sound card, you can make your computer
25 say more than an occasional beep, by programming the PC speaker.
26 Kernel patches and supporting utilities to do that are in the pcsp
27 package, available at <ftp://ftp.infradead.org/pub/pcsp/>.
30 Gameport support is for the standard 15-pin PC gameport. If you
31 have a joystick, gamepad, gameport card, a soundcard with a gameport
32 or anything else that uses the gameport, say Y or M here and also to
33 at least one of the hardware specific drivers.
34 Please read the file <file:Documentation/input/joystick.txt> which
35 contains more information and the location of the joystick package
36 that you'll need if you use the gameport with a joystick.
38 This driver is also available as a module ( = code which can be
39 inserted in and removed from the running kernel whenever you want).
40 The module will be called gameport.o. If you want to compile it as
41 a module, say M here and read <file:Documentation/modules.txt>.
44 OSS is the Open Sound System suite of sound card drivers. They make
45 sound programming easier since they provide a common API. Say Y or
46 M here (the module will be called sound.o) if you haven't found a
47 driver for your sound card above, then pick your driver from the
51 Linux can often have problems allocating DMA buffers for ISA sound
52 cards on machines with more than 16MB of RAM. This is because ISA
53 DMA buffers must exist below the 16MB boundary and it is quite
54 possible that a large enough free block in this region cannot be
55 found after the machine has been running for a while. If you say Y
56 here the DMA buffers (64Kb) will be allocated at boot time and kept
57 until the shutdown. This option is only useful if you said Y to
58 "OSS sound modules", above. If you said M to "OSS sound modules"
59 then you can get the persistent DMA buffer functionality by passing
60 the command-line argument "dmabuf=1" to the sound.o module.
62 Say Y unless you have 16MB or more RAM or a PCI sound card.
65 This module initializes the older non Plug and Play sound galaxy
66 cards from Aztech. It supports the Waverider Pro 32 - 3D and the
69 If you compile the driver into the kernel, you have to add
70 "sgalaxy=<io>,<irq>,<dma>,<dma2>,<sgbase>" to the kernel command
74 Say M here if you have a sound card based on the Analog Devices
77 If you compile the driver into the kernel, you have to add
78 "ad1816=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
81 Say Y or M if you have a Yamaha OPL3-SA1 sound chip, which is
82 usually built into motherboards. Read
83 <file:Documentation/sound/OPL3-SA> for details.
85 If you compile the driver into the kernel, you have to add
86 "opl3sa=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
90 Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio
91 16 or Logitech SoundMan 16 sound card. Answer N if you have some
92 other card made by Media Vision or Logitech since those are not
93 PAS16 compatible. Please read <file:Documentation/sound/PAS16>.
94 It is not necessary to add Sound Blaster support separately; it
95 is included in PAS support.
97 If you compile the driver into the kernel, you have to add
98 "pas2=<io>,<irq>,<dma>,<dma2>,<sbio>,<sbirq>,<sbdma>,<sbdma2>
99 to the kernel command line.
102 Say Y here to enable the Pro Audio Spectrum 16's auxiliary joystick
106 Answer Y if you have an original Sound Blaster card made by Creative
107 Labs or a 100% hardware compatible clone (like the Thunderboard or
108 SM Games). For an unknown card you may answer Y if the card claims
109 to be Sound Blaster-compatible.
111 Please read the file <file:Documentation/sound/Soundblaster>.
113 You should also say Y here for cards based on the Avance Logic
114 ALS-007 and ALS-1X0 chips (read <file:Documentation/sound/ALS>) and
115 for cards based on ESS chips (read
116 <file:Documentation/sound/ESS1868> and
117 <file:Documentation/sound/ESS>). If you have an SB AWE 32 or SB AWE
118 64, say Y here and also to "AWE32 synth" below and read
119 <file:Documentation/sound/INSTALL.awe>. If you have an IBM Mwave
120 card, say Y here and read <file:Documentation/sound/mwave>.
122 If you compile the driver into the kernel and don't want to use
123 isapnp, you have to add "sb=<io>,<irq>,<dma>,<dma2>" to the kernel
126 You can say M here to compile this driver as a module; the module is
130 Say Y here for any type of Gravis Ultrasound card, including the GUS
131 or GUS MAX. See also <file:Documentation/sound/ultrasound> for more
132 information on configuring this card with modules.
134 If you compile the driver into the kernel, you have to add
135 "gus=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
138 Be careful with this question. The MPU401 interface is supported by
139 all sound cards. However, some natively supported cards have their
140 own driver for MPU401. Enabling this MPU401 option with these cards
141 will cause a conflict. Also, enabling MPU401 on a system that
142 doesn't really have a MPU401 could cause some trouble. If your card
143 was in the list of supported cards, look at the card specific
144 instructions in the <file:Documentation/sound/README.OSS> file. It
145 is safe to answer Y if you have a true MPU401 MIDI interface card.
147 If you compile the driver into the kernel, you have to add
148 "mpu401=<io>,<irq>" to the kernel command line.
150 CONFIG_SOUND_UART6850
151 This option enables support for MIDI interfaces based on the 6850
152 UART chip. This interface is rarely found on sound cards. It's safe
153 to answer N to this question.
155 If you compile the driver into the kernel, you have to add
156 "uart6850=<io>,<irq>" to the kernel command line.
159 Answer Y or M if you have an Orchid SW32, Cardinal DSP16, Beethoven
160 ADSP-16 or some other card based on the PSS chipset (AD1848 codec +
161 ADSP-2115 DSP chip + Echo ESC614 ASIC CHIP). For more information on
162 how to compile it into the kernel or as a module see the file
163 <file:Documentation/sound/PSS>.
165 If you compile the driver into the kernel, you have to add
166 "pss=<io>,<mssio>,<mssirq>,<mssdma>,<mpuio>,<mpuirq>" to the kernel
170 Answer Y for Beethoven ADSP-16. You may try to say Y also for other
171 cards if they have master volume, bass, treble, and you can't
172 control it under Linux. If you answer N for Beethoven ADSP-16, you
173 can't control master volume, bass, treble and synth volume.
175 If you said M to "PSS support" above, you may enable or disable this
176 PSS mixer with the module parameter pss_mixer. For more information
177 see the file <file:Documentation/sound/PSS>.
180 If you have the DSPxxx.LD file or SYNTH.LD file for you card, say Y
181 to include this file. Without this file the synth device (OPL) may
185 Enter the full pathname of your DSPxxx.LD file or SYNTH.LD file,
189 Again think carefully before answering Y to this question. It's
190 safe to answer Y if you have the original Windows Sound System card
191 made by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may
192 say Y in case your card is NOT among these:
194 ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
195 Ensoniq SoundScape (and compatibles made by Reveal and Spea),
196 Gravis Ultrasound, Gravis Ultrasound ACE, Gravis Ultrasound Max,
197 Gravis Ultrasound with 16 bit option, Logitech Sound Man 16,
198 Logitech SoundMan Games, Logitech SoundMan Wave, MAD16 Pro (OPTi
199 82C929), Media Vision Jazz16, MediaTriX AudioTriX Pro, Microsoft
200 Windows Sound System (MSS/WSS), Mozart (OAK OTI-601), Orchid
201 SW32, Personal Sound System (PSS), Pro Audio Spectrum 16, Pro
202 Audio Studio 16, Pro Sonic 16, Roland MPU-401 MIDI interface,
203 Sound Blaster 1.0, Sound Blaster 16, Sound Blaster 16ASP, Sound
204 Blaster 2.0, Sound Blaster AWE32, Sound Blaster Pro, TI TM4000M
205 notebook, ThunderBoard, Turtle Beach Tropez, Yamaha FM
206 synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface.
208 For cards having native support in VoxWare, consult the card
209 specific instructions in <file:Documentation/sound/README.OSS>.
210 Some drivers have their own MSS support and saying Y to this option
211 will cause a conflict.
213 If you compile the driver into the kernel, you have to add
214 "ad1848=<io>,<irq>,<dma>,<dma2>[,<type>]" to the kernel command
218 Say Y or M if you have an SGI Visual Workstation and you want to be
219 able to use its on-board audio. Read
220 <file:Documentation/sound/vwsnd> for more info on this driver's
224 Answer Y if you have a sound card based on the Ensoniq SoundScape
225 chipset. Such cards are being manufactured at least by Ensoniq, Spea
226 and Reveal (Reveal makes also other cards).
228 If you compile the driver into the kernel, you have to add
229 "sscape=<io>,<irq>,<dma>,<mpuio>,<mpuirq>" to the kernel command
233 Answer Y if you have the AudioTriX Pro sound card manufactured
236 CONFIG_TRIX_HAVE_BOOT
237 The MediaTrix AudioTrix Pro has an on-board microcontroller which
238 needs to be initialized by downloading the code from the file
239 TRXPRO.HEX in the DOS driver directory. If you don't have the
240 TRXPRO.HEX file handy you may skip this step. However, the SB and
241 MPU-401 modes of AudioTrix Pro will not work without this file!
243 CONFIG_TRIX_BOOT_FILE
244 Enter the full pathname of your TRXPRO.HEX file, starting from /.
247 Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi
248 82C928 or 82C929 or 82C931) audio interface chip. These chips are
249 quite common so it's possible that many no-name cards have one of
250 them. In addition the MAD16 chip is used in some cards made by known
251 manufacturers such as Turtle Beach (Tropez), Reveal (some models)
252 and Diamond (latest ones). Note however that the Tropez sound cards
253 have their own driver; if you have one of those, say N here and Y or
254 M to "Full support for Turtle Beach WaveFront", below.
256 If you compile the driver into the kernel, you have to add
257 "mad16=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the
260 See also <file:Documentation/sound/Opti> and
261 <file:Documentation/sound/MAD16> for more information on setting
262 these cards up as modules.
264 CONFIG_SOUND_WAVEFRONT
265 Answer Y or M if you have a Tropez Plus, Tropez or Maui sound card
266 and read the files <file:Documentation/sound/Wavefront> and
267 <file:Documentation/sound/Tropez+>.
270 Answer Y (or M) if you have an older card based on the C928 or
271 Mozart chipset and you want to have MIDI support. If you enable this
272 option you also need to enable support for Sound Blaster.
275 Say Y here if you have a card based on the Crystal CS4232 chip set,
276 which uses its own Plug and Play protocol.
278 If you compile the driver into the kernel, you have to add
279 "cs4232=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
282 See <file:Documentation/sound/CS4232> for more information on
283 configuring this card.
286 Say Y or M if you have a card based on one of these Yamaha sound
287 chipsets or the "SAx", which is actually a SA3. Read
288 <file:Documentation/sound/OPL3-SA2> for more information on
289 configuring these cards.
291 If you compile the driver into the kernel and do not also
292 configure in the optional ISA PnP support, you will have to add
293 "opl3sa2=<io>,<irq>,<dma>,<dma2>,<mssio>,<mpuio>" to the kernel
297 Say Y here if you have a Turtle Beach Wave Front, Maui, or Tropez
300 If you compile the driver into the kernel, you have to add
301 "maui=<io>,<irq>" to the kernel command line.
303 CONFIG_MAUI_HAVE_BOOT
304 Turtle Beach Maui and Tropez sound cards have a microcontroller
305 which needs to be initialized prior to use. OSWF.MOT is a file
306 distributed with the card's DOS/Windows drivers. Answer Y if you
309 CONFIG_MAUI_BOOT_FILE
310 Enter the full pathname of your OSWF.MOT file, starting from /.
312 CONFIG_SOUND_MSNDCLAS
313 Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or
314 Monterey (not for the Pinnacle or Fiji).
316 See <file:Documentation/sound/MultiSound> for important information
317 about this driver. Note that it has been discontinued, but the
318 Voyetra Turtle Beach knowledge base entry for it is still available
319 at <http://www.voyetra-turtle-beach.com/site/kb_ftp/790.asp>.
322 I/O port address for the MultiSound Classic and related cards.
325 Interrupt Request line for the MultiSound Classic and related cards.
328 Memory-mapped I/O base address for the MultiSound Classic and
331 CONFIG_MSNDCLAS_INIT_FILE
332 The MultiSound cards have two firmware files which are required for
333 operation, and are not currently included. These files can be
334 obtained from Turtle Beach. See
335 <file:Documentation/sound/MultiSound> for information on how to
338 CONFIG_MSNDCLAS_PERM_FILE
339 The MultiSound cards have two firmware files which are required for
340 operation, and are not currently included. These files can be
341 obtained from Turtle Beach. See
342 <file:Documentation/sound/MultiSound> for information on how to
346 Say M here if you have a Turtle Beach MultiSound Pinnacle or Fiji.
347 See <file:Documentation/sound/MultiSound> for important information
348 about this driver. Note that it has been discontinued, but the
349 Voyetra Turtle Beach knowledge base entry for it is still available
350 at <http://www.voyetra-turtle-beach.com/site/kb_ftp/600.asp>.
352 CONFIG_MSNDPIN_IDE_IO0
353 CD-ROM drive 0 memory-mapped I/O base address for the MultiSound
354 Pinnacle and Fiji sound cards.
356 CONFIG_MSNDPIN_IDE_IO1
357 CD-ROM drive 1 memory-mapped I/O base address for the MultiSound
358 Pinnacle and Fiji sound cards.
360 CONFIG_MSNDPIN_IDE_IRQ
361 Interrupt request number for the IDE CD-ROM interface on the
362 MultiSound Pinnacle and Fiji sound cards.
365 Memory-mapped I/O base address for the primary synthesizer on
366 MultiSound Pinnacle and Fiji sound cards.
368 CONFIG_MSNDPIN_MPU_IO
369 Memory-mapped I/O base address for the Kurzweil daughterboard
370 synthesizer on MultiSound Pinnacle and Fiji sound cards.
372 CONFIG_MSNDPIN_MPU_IRQ
373 Iinterrupt request number for the Kurzweil daughterboard
374 synthesizer on MultiSound Pinnacle and Fiji sound cards.
377 Interrupt request line for the primary synthesizer on MultiSound
378 Pinnacle and Fiji sound cards.
380 CONFIG_MSNDPIN_JOYSTICK_IO
381 Memory-mapped I/O base address for the joystick port on MultiSound
382 Pinnacle and Fiji sound cards.
385 Memory-mapped I/O base address for the primary synthesizer on
386 MultiSound Pinnacle and Fiji sound cards.
388 CONFIG_MSNDPIN_INIT_FILE
389 The MultiSound cards have two firmware files which are required
390 for operation, and are not currently included. These files can be
391 obtained from Turtle Beach. See
392 <file:Documentation/sound/MultiSound> for information on how to
395 CONFIG_MSNDPIN_PERM_FILE
396 The MultiSound cards have two firmware files which are required for
397 operation, and are not currently included. These files can be
398 obtained from Turtle Beach. See
399 <file:Documentation/sound/MultiSound> for information on how to
402 CONFIG_MSNDPIN_DIGITAL
403 If you have the S/PDIF daughter board for the Pinnacle or Fiji,
404 answer Y here; otherwise, say N. If you have this, you will be able
405 to play and record from the S/PDIF port (digital signal). See
406 <file:Documentation/sound/MultiSound> for information on how to make
407 use of this capability.
409 CONFIG_MSNDPIN_NONPNP
410 The Pinnacle and Fiji card resources can be configured either with
411 PnP, or through a configuration port. Say Y here if your card is NOT
412 in PnP mode. For the Pinnacle, configuration in non-PnP mode allows
413 use of the IDE and joystick peripherals on the card as well; these
414 do not show up when the card is in PnP mode. Specifying zero for any
415 resource of a device will disable the device. If you are running the
416 card in PnP mode, you must say N here and use isapnptools to
417 configure the card's resources.
420 This is the port which the Pinnacle and Fiji uses to configure the
421 card's resources when not in PnP mode. If your card is in PnP mode,
422 then be sure to say N to the previous option, "MSND Pinnacle Non-PnP
426 Configures the size of each audio buffer, in kilobytes, for
427 recording and playing in the MultiSound drivers (both the Classic
428 and Pinnacle). Larger values reduce the chance of data overruns at
429 the expense of overall latency. If unsure, use the default.
432 Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4).
433 Answering Y is usually a safe and recommended choice, however some
434 cards may have software (TSR) FM emulation. Enabling FM support with
435 these cards may cause trouble (I don't currently know of any such
436 cards, however). Please read the file
437 <file:Documentation/sound/OPL3> if your card has an OPL3 chip.
439 If you compile the driver into the kernel, you have to add
440 "opl3=<io>" to the kernel command line.
444 CONFIG_SOUND_ACI_MIXER
445 ACI (Audio Command Interface) is a protocol used to communicate with
446 the microcontroller on some sound cards produced by miro and
447 Cardinal Technologies. The main function of the ACI is to control
448 the mixer and to get a product identification.
450 This VoxWare ACI driver currently supports the ACI functions on the
451 miroSOUND PCM1-pro, PCM12 and PCM20 radio. On the PCM20 radio, ACI
452 also controls the radio tuner. This is supported in the video4linux
453 miropcm20 driver (say M or Y here and go back to "Multimedia
454 devices" -> "Radio Adapters").
456 This driver is also available as a module and will be called aci.o.
458 CONFIG_SOUND_AWE32_SYNTH
459 Say Y here if you have a Sound Blaster SB32, AWE32-PnP, SB AWE64 or
460 similar sound card. See <file:Documentation/sound/README.awe>,
461 <file:Documentation/sound/AWE32> and the Soundblaster-AWE
462 mini-HOWTO, available from <http://www.linuxdoc.org/docs.html#howto>
466 Answer Y if you have a Gallant's Audio Excel DSP 16 card. This
467 driver supports Audio Excel DSP 16 but not the III nor PnP versions
470 The Gallant's Audio Excel DSP 16 card can emulate either an SBPro or
471 a Microsoft Sound System card, so you should have said Y to either
472 "100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support"
473 or "Microsoft Sound System support", above, and you need to answer
474 the "MSS emulation" and "SBPro emulation" questions below
475 accordingly. You should say Y to one and only one of these two
478 Read the <file:Documentation/sound/README.OSS> file and the head of
479 <file:drivers/sound/aedsp16.c> as well as
480 <file:Documentation/sound/AudioExcelDSP16> to get more information
481 about this driver and its configuration.
484 Answer Y if you want your audio card to emulate Sound Blaster Pro.
485 You should then say Y to "100% Sound Blaster compatibles
486 (SB16/32/64, ESS, Jazz16) support" and N to "Audio Excel DSP 16 (MSS
489 If you compile the driver into the kernel, you have to add
490 "aedsp16=<io>,<irq>,<dma>,<mssio>,<mpuio>,<mouirq>" to the kernel
494 Answer Y if you want your audio card to emulate Microsoft Sound
495 System. You should then say Y to "Microsoft Sound System support"
496 and say N to "Audio Excel DSP 16 (SBPro emulation)".
499 The SC6600 is the new version of DSP mounted on the Audio Excel DSP
500 16 cards. Find in the manual the FCC ID of your audio card and
501 answer Y if you have an SC6600 DSP.
504 Say Y here in order to use the joystick interface of the Audio Excel
507 CONFIG_SC6600_CDROMBASE
508 Base I/O port address for the CD-ROM interface of the Audio Excel
511 CONFIG_AEDSP16_MPU401
512 Answer Y if you want your audio card to emulate the MPU-401 midi
513 interface. You should then also say Y to "MPU-401 support".
515 Note that the I/O base for MPU-401 support of aedsp16 is the same
516 you have selected for "MPU-401 support". If you are using this
517 driver as a module you have to specify the MPU I/O base address with
518 the parameter 'mpu_base=0xNNN'.
521 Say Y or M if you have a PCI sound card using the CMI8338
522 or the CMI8378 chipset. Data on these chips are available at
523 <http://www.cmedia.com.tw/>.
525 A userspace utility to control some internal registers of these
526 chips is available at
527 <http://member.nifty.ne.jp/Breeze/softwares/unix/cmictl-e.html>.
529 CONFIG_SOUND_CMPCI_CM8738
530 Say Y or M if you have a PCI sound card using the CMI8338
531 or the CMI8378 chipset. Data on this chip is available at
532 <http://www.cmedia.com.tw/doc8738.htm>.
534 A userspace utility to control some internal registers of these
535 chips is available at
536 <http://member.nifty.ne.jp/Breeze/softwares/unix/cmictl-e.html>.
538 CONFIG_SOUND_CMPCI_JOYSTICK
539 Say here in order to enable the joystick port on a sound crd using
540 the CMI8338 or the CMI8738 chipset. Data on these chips are
541 available at <http://www.cmedia.com.tw/>.
543 CONFIG_SOUND_CMPCI_SPEAKERS
544 Specify the number of speaker channels you want the card to drive,
547 CONFIG_SOUND_CMPCI_SPDIFLOOP
548 Enable loopback from SPDIF in to SPDIF out. For discussion, see
549 "The 8738 Audio SPDIF In/Out Technical Data" on the technical
550 support page at <http://www.cmedia.com.tw/>.
552 A userspace utility to control even more internal registers of these
553 chips is available at
554 <http://member.nifty.ne.jp/Breeze/softwares/unix/cmictl-e.html>.
555 This package will among other things help you enable SPDIF
559 Say Y or M if you have a PCI sound card using the EMU10K1 chipset,
560 such as the Creative SBLive!, SB PCI512 or Emu-APS.
562 For more information on this driver and the degree of support for the
563 different card models please check <http://opensource.creative.com/>.
565 It is now possible to load dsp microcode patches into the EMU10K1
566 chip. These patches are used to implement real time sound
567 processing effects which include for example: signal routing,
568 bass/treble control, AC3 passthrough, ...
569 Userspace tools to create new patches and load/unload them can be
570 found at <http://opensource.creative.com/dist.html>.
573 Say Y if you want to be able to use the OSS /dev/sequencer
574 interface. This code is still experimental.
577 This module drives the Crystal SoundFusion devices (CS4280/46xx
578 series) when wired as native sound drivers with AC97 codecs. If
579 this driver does not work try the CS4232 driver.
582 Say Y or M if you have a PCI sound card utilizing the Ensoniq
583 ES1370 chipset, such as Ensoniq's AudioPCI (non-97). To find
584 out if your sound card uses an ES1370 without removing your
585 computer's cover, use lspci -n and look for the PCI ID
586 1274:5000. Since Ensoniq was bought by Creative Labs,
587 Sound Blaster 64/PCI models are either ES1370 or ES1371 based.
588 This driver differs slightly from OSS/Free, so PLEASE READ
589 <file:Documentation/sound/es1370>.
592 Say Y or M if you have a PCI sound card utilizing the Ensoniq
593 ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if
594 your sound card uses an ES1371 without removing your computer's
595 cover, use lspci -n and look for the PCI ID 1274:1371. Since
596 Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI
597 models are either ES1370 or ES1371 based. This driver differs
598 slightly from OSS/Free, so PLEASE READ
599 <file:Documentation/sound/es1371>.
601 CONFIG_SOUND_ESSSOLO1
602 Say Y or M if you have a PCI sound card utilizing the ESS Technology
603 Solo1 chip. To find out if your sound card uses a
604 Solo1 chip without removing your computer's cover, use
605 lspci -n and look for the PCI ID 125D:1969. This driver
606 differs slightly from OSS/Free, so PLEASE READ
607 <file:Documentation/sound/solo1>.
609 CONFIG_SOUND_SONICVIBES
610 Say Y or M if you have a PCI sound card utilizing the S3
611 SonicVibes chipset. To find out if your sound card uses a
612 SonicVibes chip without removing your computer's cover, use
613 lspci -n and look for the PCI ID 5333:CA00. This driver
614 differs slightly from OSS/Free, so PLEASE READ
615 <file:Documentation/sound/sonicvibes>.
618 Say Y or M if you have a PCI sound card utilizing the Trident
619 4DWave-DX/NX chipset or your mother board chipset has SiS 7018
620 or ALi 5451 built-in. The SiS 7018 PCI Audio Core is embedded
621 in SiS960 Super South Bridge and SiS540/630 Single Chipset.
622 The ALi 5451 PCI Audio Core is embedded in ALi M1535, M1535D,
623 M1535+ or M1535D+ South Bridge.
625 Use lspci -n to find out if your sound card or chipset uses
626 Trident 4DWave or SiS 7018. PCI ID 1023:2000 or 1023:2001 stands
627 for Trident 4Dwave. PCI ID 1039:7018 stands for SiS7018. PCI ID
628 10B9:5451 stands for ALi5451.
630 This driver supports S/PDIF in/out (record/playback) for ALi 5451
631 embedded in ALi M1535+ and M1535D+. Note that they aren't all
632 enabled by default; you can enable them by saying Y to "/proc file
633 system support" and "Sysctl support", and after the /proc file
634 system has been mounted, executing the command
636 command what is enabled
638 echo 0>/proc/ALi5451 pcm out is also set to S/PDIF out. (Default).
640 echo 1>/proc/ALi5451 use S/PDIF out to output pcm data.
642 echo 2>/proc/ALi5451 use S/PDIF out to output non-pcm data.
645 echo 3>/proc/ALi5451 record from Ac97 in(MIC, Line in...).
648 echo 4>/proc/ALi5451 no matter Ac97 settings, record from S/PDIF
652 This driver differs slightly from OSS/Free, so PLEASE READ the
653 comments at the top of <file:drivers/sound/trident.c>.
655 CONFIG_SOUND_WAVEARTIST
656 Say Y here to include support for the Rockwell WaveArtist sound
657 system. This driver is mainly for the NetWinder.
659 CONFIG_SOUND_VIA82CXXX
660 Say Y here to include support for the audio codec found on VIA
661 82Cxxx-based chips. Typically these are built into a motherboard.
663 DO NOT select Sound Blaster or Adlib with this driver, unless
664 you have a Sound Blaster or Adlib card in addition to your VIA
667 CONFIG_MIDI_VIA82CXXX
668 Answer Y to use the MIDI interface of the Via686. You may need to
669 enable this in the BIOS before it will work. This is for connection
670 to external MIDI hardware, and is not required for software playback
674 Say M here to include audio support for the NeoMagic 256AV/256ZX
675 chipsets. These are the audio chipsets found in the Sony
676 Z505S/SX/DX, some Sony F-series, and the Dell Latitude CPi and CPt
677 laptops. It includes support for an AC97-compatible mixer and an
678 apparently proprietary sound engine.
680 See <file:Documentation/sound/NM256> for further information.
683 Say Y or M if you have a sound system driven by ESS's Maestro line
684 of PCI sound chips. These include the Maestro 1, Maestro 2, and
685 Maestro 2E. See <file:Documentation/sound/Maestro> for more
688 CONFIG_SOUND_MAESTRO3
689 Say Y or M if you have a sound system driven by ESS's Maestro 3
693 Includes ASB 64 4D. Information on programming AdLib cards is
694 available at <http://www.itsnet.com/home/ldragon/Specs/adlib.html>.
697 Picture and feature list at
698 <http://www.pcbroker.com/crystal4281.html>.
701 Support for Gravis Ulstrasound (GUS) cards (other than the GUS),
702 sampling at 16-bit width.
705 Support for Gravis Ulstrasound MAX.
708 Support for integral audio in Intel's I/O Controller Hub (ICH)
709 chipset, as used on the 810/820/840 motherboards.
711 CONFIG_SOUND_TRACEINIT
712 Verbose soundcard initialization -- affects the format of autoprobe
713 and initialization messages at boot time.
716 Support for audio mixer facilities on the BT848 TV frame-grabber
720 16-bit support for the VIDC onboard sound hardware found on Acorn
724 Support for MIDI loopback on port 1 or 2.
727 Support for Yamaha cards including the YMF711, YMF715, YMF718,
728 YMF719, YMF724, Waveforce 192XG, and Waveforce 192 Digital.
730 CONFIG_SOUND_YMFPCI_LEGACY
731 Support for YMF7xx PCI cards emulating an MP401.
734 Say Y or M if you have a Hammerfall, Hammerfall light or Hammerfall
738 Audio DMA support for bt878 based grabber boards. As you might have
739 already noticed, bt878 is listed with two functions in /proc/pci.
740 Function 0 does the video stuff (bt848 compatible), function 1 does
741 the same for audio data. This is a driver for the audio part of
742 the chip. If you say 'Y' here you get a oss-compatible dsp device
743 where you can record from. If you want just watch TV you probably
744 don't need this driver as most TV cards handle sound with a short
745 cable from the TV card to your sound card's line-in.
747 This driver is available as a module called btaudio.o ( = code
748 which can be inserted in and removed from the running kernel
749 whenever you want). If you want to compile it as a module, say M
750 here and read <file:Documentation/modules.txt>.