|
|
bus_dma_tag_create(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_dma_tag_destroy(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_generic_attach(9) -- generic implementation of DEVICE_ATTACH for busses
|
|
This function provides an implementation of the DEVICE_ATTACH(9) method which can be used by most bus code. It simply calls device_probe_and_attach(9) for each child device attached to the bus. |
|
bus_generic_detach(9) -- generic implementation of DEVICE_DETACH for busses
|
|
This function provides an implementation of the DEVICE_DETACH(9) method which can be used by most bus code. It simply calls the DEVICE_DETACH(9) method of each child device attached to the bus. |
|
bus_generic_print_child(9) -- generic implementation of DEVICE_PRINT_CHILD for busses
|
|
This implementation prints out the default device announcement message. Given device 'foo0' on bus 'bar0' where foo0 has the name "FooCard 1234" the following would be printed: foo0: |
|
bus_generic_read_ivar(9) -- generic implementation of BUS_READ_IVAR and BUS_WRITE_IVAR for busses
|
|
These functions simply return ENOENT. |
|
bus_generic_shutdown(9) -- generic implementation of DEVICE_SHUTDOWN for busses
|
|
This function provides an implementation of the DEVICE_SHUTDOWN(9) method which can be used by most bus code. It simply calls the DEVICE_SHUTDOWN(9) method of each child device attached to the bus. |
|
bus_generic_write_ivar(9) -- generic implementation of BUS_READ_IVAR and BUS_WRITE_IVAR for busses
|
|
These functions simply return ENOENT. |
|
BUS_PRINT_CHILD(9) -- print information about a device
|
|
This is called from system code which prints out a description of a device. It should describe the attachment that the child has with the parent. For instance the TurboLaser bus prints which node the ... |
|
BUS_READ_IVAR(9) -- manipulate bus-specific device instance variables
|
|
These two methods manage a bus specific set of instance variables of a child device. The intention is that each different type of bus defines a set of appropriate instance variables (such as ports and... |
|
bus_release_resource(9) -- release resources on a bus
|
|
Free a resource allocated by bus_alloc_resource(9). The resource must not be in use on release, i.e. call an appropriate function before (e.g. bus_teardown_intr(9) for IRQs). dev is the device that ow... |
|
BUS_SETUP_INTR(9) -- create, attach and teardown an interrupt handler
|
|
The method BUS_SETUP_INTR will create and attach an interrupt handler to an interrupt previously allocated by the resource manager's BUS_ALLOC_RESOURCE(9) method. The flags are found in , ... |
|
bus_setup_intr(9) -- create, attach and teardown an interrupt handler
|
|
The method BUS_SETUP_INTR will create and attach an interrupt handler to an interrupt previously allocated by the resource manager's BUS_ALLOC_RESOURCE(9) method. The flags are found in , ... |
