snc(4) [debian man page]

SNC(4)							 BSD/i386 Kernel Interfaces Manual						    SNC(4)

NAME

     snc -- National Semiconductor DP8393X SONIC Ethernet adapter driver

SYNOPSIS

     device isa
     device snc

DESCRIPTION

     The snc driver provides support for the National Semiconductor SONIC Ethernet adapters.

HARDWARE

     The snc driver supports the following cards:

     o	 National Semiconductor DP83934AVQB
     o	 NEC PC-9801-83
     o	 NEC PC-9801-84
     o	 NEC PC-9801-103
     o	 NEC PC-9801-104
     o	 NEC PC-9801N-15
     o	 NEC PC-9801N-25
     o	 NEC PC-9801N-J02 PCMCIA
     o	 NEC PC-9801N-J02R PCMCIA

     The snc driver also includes support for the National Semiconductor NS46C46 as 64 * 16 bits Microwave Serial EEPROM.

IMPLEMENTATION NOTES

     Accessing SONIC card data structures and registers as 32 bit values makes code endianness independent.  The SONIC is however always in big-
     endian mode so it is necessary to ensure that data structures shared between the CPU and the SONIC card are always in big-endian order.  The
     snc driver supports the PC-98 C-Bus, and PnP buses.  Support is also provided for the legacy C-Bus.

DIAGNOSTICS

     The following driver specific error messages may be reported:

     snc%d: snc_nec16_register_irq: unsupported irq (%d)  The card returned an IRQ which is not supported by the driver.

     snc%d: invalid packet length %d bytes  An attempt to transfer a data packet failed due to an invalid packet length.

SEE ALSO

     netintro(4), bus_alloc_resource_any(9)

HISTORY

     The snc driver was ported from NetBSD by Motomichi Matsuzaki <mzaki@e-mail.ne.jp> and Hiroshi Yamashita <bluemoon@msj.biglobe.ne.jp>.  It
     first appeared in FreeBSD 4.2.  This manual page first appeared in FreeBSD 5.3.

AUTHORS

     This manual page was written by Tom Rhodes <trhodes@FreeBSD.org>.

BUGS

     Currently the snc driver only works on the PC-98 architecture.  It should probably work on the i386 architecture as well.

BSD
								 September 4, 2004							       BSD

FWOHCI(4)						   BSD Kernel Interfaces Manual 						 FWOHCI(4)

NAME

     fwohci -- OHCI FireWire chipset device driver

SYNOPSIS

     To compile this driver into the kernel, place the following line in your kernel configuration file:

	   device firewire

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

	   firewire_load="YES"

     To disable physical access (see BUGS section for detail), put the following line in loader.conf(5):

	   hw.firewire.phydma_enable=0

HARDWARE

     The fwohci driver provides support for PCI/CardBus FireWire interface cards.  The driver supports the following IEEE 1394 OHCI chipsets:

     o	 Adaptec AHA-894x/AIC-5800
     o	 Apple Pangea
     o	 Apple UniNorth
     o	 Intel 82372FB
     o	 IOGEAR GUF320
     o	 Lucent / Agere FW322/323
     o	 NEC uPD72861
     o	 NEC uPD72870
     o	 NEC uPD72871/2
     o	 NEC uPD72873
     o	 NEC uPD72874
     o	 National Semiconductor CS4210
     o	 Ricoh R5C551
     o	 Ricoh R5C552
     o	 Sony CX3022
     o	 Sony i.LINK (CXD3222)
     o	 Sun PCIO-2 (RIO 1394)
     o	 Texas Instruments PCI4410A
     o	 Texas Instruments PCI4450
     o	 Texas Instruments PCI4451
     o	 Texas Instruments TSB12LV22
     o	 Texas Instruments TSB12LV23
     o	 Texas Instruments TSB12LV26
     o	 Texas Instruments TSB43AA22
     o	 Texas Instruments TSB43AB21/A/AI/A-EP
     o	 Texas Instruments TSB43AB22/A
     o	 Texas Instruments TSB43AB23
     o	 Texas Instruments TSB82AA2
     o	 VIA Fire II (VT6306)

SEE ALSO

     firewire(4), fwe(4), fwip(4), sbp(4), fwcontrol(8), kldload(8)

HISTORY

     The fwohci device driver first appeared in FreeBSD 5.0.

AUTHORS

     The fwohci device driver was written by Katsushi Kobayashi and Hidetoshi Shimokawa.

BUGS

     The driver allows physical access from any nodes on the bus by default.  This means that any devices on the bus can read and modify any mem-
     ory space which can be accessed by an IEEE 1394 OHCI chip.  It is allowed mostly for sbp(4) devices.  This should be changed to allow it only
     for specific devices.  Anyway, FireWire is a bus and not expected to be connected with un-trustable devices because a node can monitor all
     the traffic.

BSD
								   March 3, 2008							       BSD