Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

discover.conf(5) [debian man page]

discover.conf(5)						File Formats Manual						  discover.conf(5)

NAME

       discover.conf -- configuration file format for discover(1)

Description
       Discover  looks	for  configuration  files  in a configuration directory, containing a number of files.	These define the system buses that
       should be scanned by default, those that should never be scanned, and the URLs for hardware data files beyond the local copy provided  with
       the software.

       The file format is XML; the DTD	   is provided with the Discover software, and can be used for informational or validation purposes.

Examples
       Establishing default buses to scan

       <?xml version="1.0"?>

       <!DOCTYPE conffile SYSTEM "conffile.dtd">

       <conffile>
       <busscan scan="default">
       <bus name="ata"/>
       <bus name="pci"/>
       <bus name="pcmcia"/>
       <bus name="scsi"/>
       <bus name="usb"/>
       </busscan>
       </conffile>

       A more complex example

       <?xml version="1.0"?>

       <!DOCTYPE conffile SYSTEM "conffile.dtd">

       <conffile>
       <busscan scan="default">
       <bus name="ata"/>
       <bus name="pci"/>
       <bus name="pcmcia"/>
       <bus name="usb"/>
       </busscan>
       <!-- My ancient SCSI card locks up when probed -->
       <busscan scan="never">
       <bus name="scsi"/>
       </busscan>
       <data-sources>
       <data-source url="http://www.example.com/discover/xfree86.xml"
       label="Updated XFree86 hardware information">
       </data-sources>
       </conffile>

Authors
       Josh Bressers, John R. Daily, and G. Branden Robinson developed the current implementation of Discover for Progeny Linux Systems.

       The Linux implementation of the system-dependent interfaces is derived from detect, by MandrakeSoft SA.

See Also
       discover(1)

																  discover.conf(5)

Check Out this Related Man Page

FIREWIRE(4)						   BSD Kernel Interfaces Manual 					       FIREWIRE(4)

NAME

     firewire -- IEEE1394 High-performance Serial Bus

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"

DESCRIPTION

     FreeBSD provides machine-independent bus support and raw drivers for firewire interfaces.

     The firewire driver consists of two layers: the controller and the bus layer.  The controller attaches to a physical bus (like pci(4)).  The
     firewire bus attaches to the controller.  Additional drivers can be attached to the bus.

     Up to 63 devices, including the host itself, can be attached to a firewire bus.  The root node is dynamically assigned with a PHY device
     function.	Also, the other firewire bus specific parameters, e.g., node ID, cycle master, isochronous resource manager and bus manager, are
     dynamically assigned, after bus reset is initiated.  On the firewire bus, every device is identified by an EUI 64 address.

FILES

     /dev/fw0.0
     /dev/fwmem0.0

SEE ALSO

     fwe(4), fwip(4), fwohci(4), pci(4), sbp(4), eui64(5), fwcontrol(8), kldload(8), sysctl(8)

HISTORY

     The firewire driver first appeared in FreeBSD 5.0.

AUTHORS

     The firewire driver was written by Katsushi Kobayashi and Hidetoshi Shimokawa for the FreeBSD project.

BUGS

     See fwohci(4) for security notes.

BSD
								   April 1, 2006							       BSD
Man Page