isapnp(4) [netbsd man page]

ISAPNP(4)						   BSD Kernel Interfaces Manual 						 ISAPNP(4)

NAME

     isapnp -- introduction to ISA Plug-and-Play support

SYNOPSIS

     isapnp0 at isa?

     An
     isapnp bus can be configured for each supported ISA bus.

DESCRIPTION

     NetBSD provides machine-independent bus support and drivers for ISA Plug-and-Play (isapnp) autoconfiguration of PnP-compatible devices on an
     ISA bus.

SUPPORTED DEVICES

     NetBSD includes machine-independent ISAPNP drivers, sorted by function and driver name:

   SCSI interfaces
	   aha	      Adaptec AHA-154[02] SCSI interfaces.

	   aic	      Adaptec AHA-1520B SCSI interfaces.

   Disk controllers
	   wdc	      Standard IDE and ATAPI drive controller.

   Serial and parallel interfaces
	   com	      8250/16450/16550-compatible ISA PnP serial cards and internal modems.

   Network interfaces
	   an	      Aironet 4500/4800 and Cisco 340 series 802.11 interfaces.

	   ep	      3Com 3c509B EtherLink III Ethernet interface.

	   le	      PCnet-PnP Ethernet interfaces based on the successor to the AMD LANCE chip.

	   ne	      NE2000-compatible Ethernet interfaces.

	   tr	      TROPIC based token ring interfaces.

   Sound cards
	   ess	      ESS Technology derived PnP sound cards and devices.

	   guspnp     Gravis Ultrasound PnP sound cards.

	   sb	      SoundBlaster, SoundBlaster 16, and SoundBlaster Pro sound cards.

	   wss	      Windows Sound System compatible cards, e.g., most of the cards with Crystal Semiconductor chips.

	   ym	      Yamaha OPL3-SAx sound cards.

   Miscellaneous devices
	   pcic       PCI PCMCIA controllers, including the Cirrus Logic GD6729.

     ISA Plug-and-Play devices also have alternate ISA drivers with static ISA IO address configuration.  These are listed in isa(4).  The isapnp
     bus ignores devices that have already been found and configured as isa(4) devices.  The isapnp bus is only effective on machines which lack a
     PnP BIOS, or  on which the PnP BIOS has been disabled.  The manual pages for each individual isapnp driver also list the supported front-ends
     for other buses.

SEE ALSO

     aha(4), aic(4), an(4), com(4), ep(4), ess(4), guspnp(4), intro(4), isa(4), le(4), ne(4), pcic(4), sb(4), tr(4), wdc(4), wss(4), ym(4)

HISTORY

     The isapnp driver appeared in NetBSD 1.3.

BSD
								 February 17, 1997							       BSD

SB(4)							   BSD Kernel Interfaces Manual 						     SB(4)

NAME

     sb -- SoundBlaster family (and compatible) audio device driver

SYNOPSIS

     sb0    at isa? port 0x220 irq 5 drq 1 drq2 5
     sb1    at isa? port 0x240 irq 7 drq 1 flags 1
     sb*    at isapnp?
     sb*    at pnpbios? index ?
     audio* at audiobus?
     midi*  at sb?
     mpu*   at sb?
     opl*   at sb?

DESCRIPTION

     The sb driver provides support for the SoundBlaster, SoundBlaster Pro, SoundBlaster 16, Jazz 16, SoundBlaster AWE 32, SoundBlaster AWE 64,
     and hardware register-level compatible audio cards.

     The SoundBlaster series are half-duplex cards, capable of 8- and 16-bit audio sample recording and playback at rates up to 44.1kHz (depending
     on the particular model).

     The base I/O port address is usually jumper-selected to either 0x220 or 0x240 (newer cards may provide software configuration, but this
     driver does not directly support them--you must configure the card for its I/O addresses with other software).  The SoundBlaster takes 16 I/O
     ports.  For the SoundBlaster and SoundBlaster Pro, the IRQ and DRQ channels are jumper-selected.  For the SoundBlaster 16, the IRQ and DRQ
     channels are set by this driver to the values specified in the config file.  The IRQ must be selected from the set {5,7,9,10}.

     The configuration file must use 1 flags specification to enable the Jazz16 support.  This is to avoid potential conflicts with other devices
     when probing the Jazz 16 because it requires use of extra I/O ports not in the base port range.

     With a SoundBlaster 16 card the device is full duplex, but it can only sensibly handle a precision of 8 bits.  It does so by extending the
     output 8 bit samples to 16 bits and using the 8 bit DMA channel for input and the 16 bit channel for output.

     The joystick interface (if enabled by a jumper) is handled by the joy(4) driver, and the optional SCSI CD-ROM interface is handled by the
     aic(4) driver.

     SoundBlaster 16 cards have MPU401 emulation and can use the mpu attachment, older cards have a different way to generate MIDI and has a midi
     device attached directly to the sb.

SEE ALSO

     aic(4), audio(4), isa(4), isapnp(4), joy(4), midi(4), mpu(4), opl(4), pnpbios(4)

HISTORY

     The sb device driver appeared in NetBSD 1.0.

BUGS

     Non-SCSI CD-ROM interfaces are not supported.

     The MIDI interface on the SB hardware is braindead, and the driver needs to busy wait while writing MIDI data.  This will consume a lot of
     system time.

BSD
								   June 22, 2005							       BSD