summaryrefslogtreecommitdiffstats
path: root/Documentation/sound/AD1816
diff options
context:
space:
mode:
authorRalf Baechle <ralf@linux-mips.org>2000-10-05 01:18:40 +0000
committerRalf Baechle <ralf@linux-mips.org>2000-10-05 01:18:40 +0000
commit012bb3e61e5eced6c610f9e036372bf0c8def2d1 (patch)
tree87efc733f9b164e8c85c0336f92c8fb7eff6d183 /Documentation/sound/AD1816
parent625a1589d3d6464b5d90b8a0918789e3afffd220 (diff)
Merge with Linux 2.4.0-test9. Please check DECstation, I had a number
of rejects to fixup while integrating Linus patches. I also found that this kernel will only boot SMP on Origin; the UP kernel freeze soon after bootup with SCSI timeout messages. I commit this anyway since I found that the last CVS versions had the same problem.
Diffstat (limited to 'Documentation/sound/AD1816')
-rw-r--r--Documentation/sound/AD181661
1 files changed, 9 insertions, 52 deletions
diff --git a/Documentation/sound/AD1816 b/Documentation/sound/AD1816
index b43d13be8..c5085a9a7 100644
--- a/Documentation/sound/AD1816
+++ b/Documentation/sound/AD1816
@@ -1,52 +1,15 @@
Documentation for the AD1816(A) sound driver
============================================
-NOTE: This driver is still EXPERIMENTAL, so don't use it on production
-systems!
-
-
Installation:
-------------
-To get your AD1816(A) based sound card work, you'll have to enable
-module support ("Enable loadable module support") and support for
-experimental code ("Prompt for development and/or incomplete
-code/drivers") during kernel configuration. Enable "Sound card
-support", "OSS modules support" and "Support for AD1816(A) based cards
-(EXPERIMENTAL)" in the sound configuration menu, too. Be sure, that
-you build "Support for AD1816(A) based cards (EXPERIMENTAL)" as a MODULE,
-otherwise you may run into problems later.
-Now build, install and reboot the new kernel as usual.
-
-Since the AD1816(A) is a P'n'P sound chip you'll usually have to
-configure it using the isapnptools. See isapnptools documentation for
-details on configuring P'n'P cards.
-
-After you have successfully configured the card using isapnp, you may
-load the AD1816 driver using modprobe. A typical modprobe call should
-look like this:
-
- modprobe ad1816 io=0x530 irq=5 dma=1 dma2=3 ad1816_clockfreq=33000
-
-if your isapnp.conf file looks like this (relevant lines only):
-
- (INT 0 (IRQ 5 (MODE +E)))
- (DMA 0 (CHANNEL 1))
- (DMA 1 (CHANNEL 3))
- (IO 0 (BASE 0x0220))
- (IO 1 (BASE 0x0388))
- (IO 2 (BASE 0x0530))
-
-NOTE: Be sure, that you use the address IO 2 (in our example 0x530) when
-loading the module!
-
-If your setup was correct, you should see the following messages in
-/var/log/messages (numbers may be different):
-
-Nov 6 17:07:26 tek01 kernel: ad1816_detect(530)
-Nov 6 17:07:26 tek01 kernel: ad1816_detect() - Detected OK
-Nov 6 17:07:26 tek01 kernel: AD1816 Version: 3
-
+To get your AD1816(A) based sound card work, you'll have to enable support for
+experimental code ("Prompt for development and/or incomplete code/drivers")
+and isapnp ("Plug and Play support", "ISA Plug and Play support"). Enable
+"Sound card support", "OSS modules support" and "Support for AD1816(A) based
+cards (EXPERIMENTAL)" in the sound configuration menu, too. Now build, install
+and reboot the new kernel as usual.
Features:
---------
@@ -86,13 +49,7 @@ Troubleshooting:
----------------
First of all you should check, if the driver has been loaded
-properly. If you get the following message in your /var/log/messages:
-
-Nov 6 17:06:31 tek01 kernel: ad1816_detect(530)
-Nov 6 17:06:31 tek01 kernel: Chip is not an AD1816 or chip is not active
-
-you either used the wrong address for loading the driver, your chip is
-not an AD1816 or you forgot to initialize the card with isapnp.
+properly.
If loading of the driver succeeds, but playback/capture fails, check
if you used the correct values for irq, dma and dma2 when loading the module.
@@ -122,6 +79,6 @@ or:
Bugreports, bugfixes and related questions should be sent via E-Mail to:
tek@rbg.informatik.tu-darmstadt.de
-
Thorsten Knabe <tek@rbg.informatik.tu-darmstadt.de>
- Last modified: 1999/05/02
+Christoph Hellwig <hch@caldera.de>
+ Last modified: 2000/09/20