Query: superhyway_add_device
OS: suse
Section: 9
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
SUPERHYWAY_ADD_DEVIC(9) Busses SUPERHYWAY_ADD_DEVIC(9)NAMEsuperhyway_add_device - Add a SuperHyway moduleSYNOPSISint superhyway_add_device(unsigned long base, struct superhyway_device * sdev, struct superhyway_bus * bus);ARGUMENTSbase Physical address where module is mapped. sdev SuperHyway device to add, or NULL to allocate a new one. bus Bus where SuperHyway module resides.DESCRIPTIONThis is responsible for adding a new SuperHyway module. This sets up a new struct superhyway_device for the module being added if sdev == NULL. Devices are initially added in the order that they are scanned (from the top-down of the memory map), and are assigned an ID based on the order that they are added. Any manual addition of a module will thus get the ID after the devices already discovered regardless of where it resides in memory. Further work can and should be done in superhyway_scan_bus, to be sure that any new modules are properly discovered and subsequently registered.AUTHORPaul Mundt <lethal@linux-sh.org> Author.COPYRIGHTKernel Hackers Manual 2.6. July 2010 SUPERHYWAY_ADD_DEVIC(9)
Related Man Pages |
---|
get_kernel_syms(2) - redhat |
query_module(2) - redhat |
struct_device_driver(9) - centos |
init_module(2) - suse |
struct_ccwgroup_driver(9) - suse |
Similar Topics in the Unix Linux Community |
---|
Tar Command |
A (ksh) Library For and From UNIX.com |
Docker learning Phase-I |
Shopt -s histappend |
32 bit process addressing more than 4GB |