svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
bus_activate_resource(9)
These functions activate or deactivate a previously allocated re‐
source. In general, resources must be activated before they can
be accessed by the driver. Bus drivers may perform additional
actions to ensure that the resource is ready to be accessed. For
example, the PCI bus driver enables memory decoding in a PCI de‐
vice's command register when activating a memory resource. The
arguments are as follows: The device that requests ownership of
the resource. Before allocation, the resource is owned by the
parent bus. The type of resource you want to allocate. It is
one of: for PCI bus numbers for IRQs for ISA DMA lines for I/O
ports for I/O memory A pointer to a bus specific handle that
identifies the resource being allocated. A pointer to the re‐
turned by Resources which can be mapped for CPU access by a tag
and handle will create a mapping of the entire resource when ac‐
tivated. The tag and handle for this mapping are stored in and
can be retrieved via and These can be used with the API to access
device registers or memory described by If the mapping is associ‐
ated with a virtual address, the virtual address can be retrieved
via This implicit mapping can be disabled by passing the flag to
A driver may use this if it wishes to allocate its own mappings
of a resource using A wrapper API for is also provided that ac‐
cepts the associated resource as the first argument in place of
the tag and handle. The functions in this wrapper API are named
similarly to the API except that is removed from their name. For
example, can be used in place of The wrapper API is preferred in
new drivers. These two statements both read a 32-bit register at
the start of a resource:
bus_space_read_4(rman_get_bustag(res), rman_get_bushan‐
dle(res), 0); bus_read_4(res, 0); Zero is returned on
success, otherwise an error is returned. This manual page was
written by