|
|
arpintr(9) -- externally visible ARP functions
|
|
The arp functions provide the interface between the arp module and the network drivers which need arp functionality. Such drivers must request the arp attribute in their "files" declaration. arp_ifi... |
|
arpresolve(9) -- externally visible ARP functions
|
|
The arp functions provide the interface between the arp module and the network drivers which need arp functionality. Such drivers must request the arp attribute in their "files" declaration. arp_ifi... |
|
arp_ifinit(9) -- externally visible ARP functions
|
|
The arp functions provide the interface between the arp module and the network drivers which need arp functionality. Such drivers must request the arp attribute in their "files" declaration. arp_ifi... |
|
audio(9) -- interface between low and high level audio drivers
|
|
The audio device driver is divided into a high level, hardware independent layer, and a low level hardware dependent layer. The interface between these is the audio_hw_if structure. struct audio_hw_if... |
|
autoconf(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
bcmp(9) -- compare byte string
|
|
The bcmp() interface is obsolete. Do not add new code using it. It will soon be purged. Use memcmp(9) instead. (The bcmp() function is now a macro for memcmp(9).) The bcmp() function compares byte str... |
|
bcopy(9) -- copy byte string
|
|
The bcopy() interface is obsolete. Do not add new code using it. It will soon be purged. Use memcpy(9) instead. (The bcopy() function is now a macro for memcpy(9).) The bcopy() function copies len byt... |
|
bdevvp(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
i386/bios32_service(9) -- locate BIOS32 service
|
|
The bios32_service() function calls the BIOS32 to locate the specified BIOS32 service service and fills in the entry point information e and ei. |
|
i386/bioscall(9) -- call system BIOS function from real mode
|
|
The bioscall function switches the processor into real mode, calls the BIOS interrupt numbered function, and returns to protected mode. This function is intended to be called during the initial system... |
|
bitmask_snprintf(9) -- bitmask output conversion
|
|
The bitmask_snprintf() function formats a bitmask into a mnemonic form suitable for printing. This conversion is useful for decoding bit fields in device registers. It formats the integer val into the... |
|
boottime(9) -- system time variables
|
|
The time variable is the system's ``wall time'' clock. It is set at boot by inittodr(9), and is updated by the settimeofday(2) system call and by periodic clock interrupts. The boottime variable ho... |
|
bounds_check_with_label(9) -- disk label management routines
|
|
This collection of routines provides a disklabel management interface to kernel device drivers. These routines are classified as machine- or architecture-dependent because of restrictions imposed by t... |
|
bus_dma(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Provide a bus- and machine-independent "DMA mapping interface." |
|
bus_dmamap_create(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Provide a bus- and machine-independent "DMA mapping interface." |
|
bus_dmamap_destroy(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Provide a bus- and machine-independent "DMA mapping interface." |
|
bus_dmamap_load(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Provide a bus- and machine-independent "DMA mapping interface." |
|
bus_dmamap_load_mbuf(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Provide a bus- and machine-independent "DMA mapping interface." |
|
bus_dmamap_load_raw(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Provide a bus- and machine-independent "DMA mapping interface." |
|
bus_dmamap_load_uio(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Provide a bus- and machine-independent "DMA mapping interface." |
|
bus_dmamap_sync(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Provide a bus- and machine-independent "DMA mapping interface." |
|
bus_dmamap_unload(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Provide a bus- and machine-independent "DMA mapping interface." |
|
bus_dmamem_alloc(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Provide a bus- and machine-independent "DMA mapping interface." |
|
bus_dmamem_free(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Provide a bus- and machine-independent "DMA mapping interface." |
|
bus_dmamem_map(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Provide a bus- and machine-independent "DMA mapping interface." |
|
bus_dmamem_mmap(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Provide a bus- and machine-independent "DMA mapping interface." |
|
bus_dmamem_unmap(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Provide a bus- and machine-independent "DMA mapping interface." |
|
bus_space(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_alloc(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_barrier(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_copy_region_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_copy_region_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_copy_region_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_copy_region_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_free(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_map(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_mmap(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_multi_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_multi_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_multi_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_multi_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_region_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_region_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_region_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_region_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_set_region_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_set_region_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_set_region_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_set_region_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_subregion(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_unmap(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_vaddr(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_multi_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_multi_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_multi_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_multi_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_region_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_region_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_region_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_region_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bzero(9) -- write zeroes to a byte string
|
|
The bzero() interface is obsolete. Do not add new code using it. It will soon be purged. Use memset(9) instead. (The bzero() function is now a macro for memset(9).) The bzero() function writes len zer... |
|
cache_enter(9) -- name lookup cache
|
|
The name lookup cache is the mechanism to allow the file system type dependent algorithms to quickly resolve a file's vnode from its pathname. The name lookup cache is generally accessed through the ... |
|
cache_lookup(9) -- name lookup cache
|
|
The name lookup cache is the mechanism to allow the file system type dependent algorithms to quickly resolve a file's vnode from its pathname. The name lookup cache is generally accessed through the ... |
|
cache_purge(9) -- name lookup cache
|
|
The name lookup cache is the mechanism to allow the file system type dependent algorithms to quickly resolve a file's vnode from its pathname. The name lookup cache is generally accessed through the ... |
|
cache_purgevfs(9) -- name lookup cache
|
|
The name lookup cache is the mechanism to allow the file system type dependent algorithms to quickly resolve a file's vnode from its pathname. The name lookup cache is generally accessed through the ... |
|
cache_revlookup(9) -- name lookup cache
|
|
The name lookup cache is the mechanism to allow the file system type dependent algorithms to quickly resolve a file's vnode from its pathname. The name lookup cache is generally accessed through the ... |
|
callout(9) -- execute a function after a specified length of time
|
|
The callout facility provides a mechanism to execute a function at a given time. The timer is based on the hardclock timer which ticks hz times per second. The function is called at softclock interrup... |
|
callout_active(9) -- execute a function after a specified length of time
|
|
The callout facility provides a mechanism to execute a function at a given time. The timer is based on the hardclock timer which ticks hz times per second. The function is called at softclock interrup... |
|
callout_deactivate(9) -- execute a function after a specified length of time
|
|
The callout facility provides a mechanism to execute a function at a given time. The timer is based on the hardclock timer which ticks hz times per second. The function is called at softclock interrup... |
|
callout_init(9) -- execute a function after a specified length of time
|
|
The callout facility provides a mechanism to execute a function at a given time. The timer is based on the hardclock timer which ticks hz times per second. The function is called at softclock interrup... |
|
callout_pending(9) -- execute a function after a specified length of time
|
|
The callout facility provides a mechanism to execute a function at a given time. The timer is based on the hardclock timer which ticks hz times per second. The function is called at softclock interrup... |
|
callout_reset(9) -- execute a function after a specified length of time
|
|
The callout facility provides a mechanism to execute a function at a given time. The timer is based on the hardclock timer which ticks hz times per second. The function is called at softclock interrup... |
|
callout_stop(9) -- execute a function after a specified length of time
|
|
The callout facility provides a mechanism to execute a function at a given time. The timer is based on the hardclock timer which ticks hz times per second. The function is called at softclock interrup... |
|
cardbus(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
cardbus_attach_card(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
cardbus_conf_read(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
Cardbus_conf_read(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
cardbus_conf_write(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
Cardbus_conf_write(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
cardbus_detach_card(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
cardbus_free_tag(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
Cardbus_free_tag(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
cardbus_function_disable(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
Cardbus_function_disable(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
cardbus_function_enable(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
Cardbus_function_enable(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
cardbus_get_capability(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
cardbus_intr_disestablish(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
cardbus_intr_establish(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
cardbus_make_tag(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
Cardbus_make_tag(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
cardbus_mapreg_map(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
Cardbus_mapreg_map(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
cardbus_mapreg_unmap(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
Cardbus_mapreg_unmap(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
CARDBUS_PRODUCT(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
CARDBUS_VENDOR(9) -- support for
|
|
The machine-independent Cardbus subsystem provides support for Cardbus devices. The Cardbus interface is an improvement to the PC-Card interface supported by pcmcia(9). It introduces several new capab... |
|
cdevvp(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
checkalias(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
clock_secs_to_ymdhms(9) -- time-of-day clock support
|
|
The todr_*() functions provide an interface to read, set and control `time-of-day' devices. The todr_chip_handle_t should be obtained from a driver for a particular hardware device that implements th... |
|
clock_ymdhms_to_secs(9) -- time-of-day clock support
|
|
The todr_*() functions provide an interface to read, set and control `time-of-day' devices. The todr_chip_handle_t should be obtained from a driver for a particular hardware device that implements th... |
|
cltom(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
cnbell(9) -- console access interface
|
|
These functions operate over current console device. The console has to be initialized first, before these functions could be used. Console input polling functions cngetc(), cngetsn() and cnpollc() ar... |
|
cngetc(9) -- console access interface
|
|
These functions operate over current console device. The console has to be initialized first, before these functions could be used. Console input polling functions cngetc(), cngetsn() and cnpollc() ar... |
|
cngetsn(9) -- console access interface
|
|
These functions operate over current console device. The console has to be initialized first, before these functions could be used. Console input polling functions cngetc(), cngetsn() and cnpollc() ar... |
|
cnmagic(9) -- console magic key sequence management
|
|
The NetBSD console magic key sequence management framework is designed to provide flexible methods to set, change, and detect magic key sequences on console devices and break into the debugger or ROM ... |
|
cnpollc(9) -- console access interface
|
|
These functions operate over current console device. The console has to be initialized first, before these functions could be used. Console input polling functions cngetc(), cngetsn() and cnpollc() ar... |
|
cnputc(9) -- console access interface
|
|
These functions operate over current console device. The console has to be initialized first, before these functions could be used. Console input polling functions cngetc(), cngetsn() and cnpollc() ar... |
|
config(9) -- the autoconfiguration framework ``device definition'' language
|
|
In NetBSD, the config(8) program reads and verifies a machine description file specifying the devices to include in the kernel. A table is produced by config(8) which is used by the kernel during auto... |
|
config_activate(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_attach(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_deactivate(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_defer(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_detach(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_found(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_found_sm(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_interrupts(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_pending_decr(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_pending_incr(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_search(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
cons(9) -- console access interface
|
|
These functions operate over current console device. The console has to be initialized first, before these functions could be used. Console input polling functions cngetc(), cngetsn() and cnpollc() ar... |
|
copy(9) -- kernel space to/from user space copy functions
|
|
The copy functions are designed to copy contiguous data from one address to another. All but copystr() copy data from user-space to kernel-space or vice-versa. The copy routines provide the following ... |
|
copyin(9) -- kernel space to/from user space copy functions
|
|
The copy functions are designed to copy contiguous data from one address to another. All but copystr() copy data from user-space to kernel-space or vice-versa. The copy routines provide the following ... |
|
copyinstr(9) -- kernel space to/from user space copy functions
|
|
The copy functions are designed to copy contiguous data from one address to another. All but copystr() copy data from user-space to kernel-space or vice-versa. The copy routines provide the following ... |
|
copyin_proc(9) -- kernel space to/from user space copy functions
|
|
The copy functions are designed to copy contiguous data from one address to another. All but copystr() copy data from user-space to kernel-space or vice-versa. The copy routines provide the following ... |
|
copyout(9) -- kernel space to/from user space copy functions
|
|
The copy functions are designed to copy contiguous data from one address to another. All but copystr() copy data from user-space to kernel-space or vice-versa. The copy routines provide the following ... |
|
copyoutstr(9) -- kernel space to/from user space copy functions
|
|
The copy functions are designed to copy contiguous data from one address to another. All but copystr() copy data from user-space to kernel-space or vice-versa. The copy routines provide the following ... |
|
copyout_proc(9) -- kernel space to/from user space copy functions
|
|
The copy functions are designed to copy contiguous data from one address to another. All but copystr() copy data from user-space to kernel-space or vice-versa. The copy routines provide the following ... |
|
copystr(9) -- kernel space to/from user space copy functions
|
|
The copy functions are designed to copy contiguous data from one address to another. All but copystr() copy data from user-space to kernel-space or vice-versa. The copy routines provide the following ... |
|
cpu_reboot(9) -- halt or reboot the system
|
|
The cpu_reboot() function handles final system shutdown, and either halts or reboots the system. The exact action to be taken is determined by the flags passed in howto and by whether or not the syste... |
|
cpu_switch(9) -- switch to another process context
|
|
The mi_switch() function implements the machine-independent prelude to a process context switch. It is called from only a few distinguished places in the kernel code as a result of the principle of no... |
|
ctxsw(9) -- switch to another process context
|
|
The mi_switch() function implements the machine-independent prelude to a process context switch. It is called from only a few distinguished places in the kernel code as a result of the principle of no... |
|
disk(9) -- generic disk framework
|
|
The NetBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk stru... |
|
disklabel(9) -- disk label management routines
|
|
This collection of routines provides a disklabel management interface to kernel device drivers. These routines are classified as machine- or architecture-dependent because of restrictions imposed by t... |
|
disk_attach(9) -- generic disk framework
|
|
The NetBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk stru... |
|
disk_busy(9) -- generic disk framework
|
|
The NetBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk stru... |
|
disk_detach(9) -- generic disk framework
|
|
The NetBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk stru... |
|
disk_find(9) -- generic disk framework
|
|
The NetBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk stru... |
|
disk_init(9) -- generic disk framework
|
|
The NetBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk stru... |
|
disk_resetstat(9) -- generic disk framework
|
|
The NetBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk stru... |
|
disk_unbusy(9) -- generic disk framework
|
|
The NetBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk stru... |
|
dopowerhooks(9) -- run all power hooks
|
|
The dopowerhooks() function invokes all power hooks established using the powerhook_establish(9) function. When power is disappearing the power hooks are called in reverse order, i.e., the power hook ... |
|
doshutdownhooks(9) -- run all shutdown hooks
|
|
The doshutdownhooks() function invokes all shutdown hooks established using the shutdownhook_establish(9) function. Shutdown hooks are called in reverse order, i.e. the shutdown hook established last ... |
|
driver(9) -- description of a device driver
|
|
This page briefly describes the basic NetBSD autoconfiguration interface utilised by device drivers. For a detailed overview of the autoconfiguration framework see autoconf(9). Each device driver must... |
|
ethersubr(9) -- Ethernet and FDDI driver support functions and macros
|
|
The ethersubr functions provide the interface between the ethersubr module and the network drivers which need Ethernet support. Such drivers must request the ether attribute in their files declaration... |
|
ether_addmulti(9) -- Ethernet and FDDI driver support functions and macros
|
|
The ethersubr functions provide the interface between the ethersubr module and the network drivers which need Ethernet support. Such drivers must request the ether attribute in their files declaration... |
|
ether_delmulti(9) -- Ethernet and FDDI driver support functions and macros
|
|
The ethersubr functions provide the interface between the ethersubr module and the network drivers which need Ethernet support. Such drivers must request the ether attribute in their files declaration... |
|
ETHER_FIRST_MULTI(9) -- Ethernet and FDDI driver support functions and macros
|
|
The ethersubr functions provide the interface between the ethersubr module and the network drivers which need Ethernet support. Such drivers must request the ether attribute in their files declaration... |
|
ether_ifattach(9) -- Ethernet and FDDI driver support functions and macros
|
|
The ethersubr functions provide the interface between the ethersubr module and the network drivers which need Ethernet support. Such drivers must request the ether attribute in their files declaration... |
|
ETHER_IS_MULTICAST(9) -- Ethernet and FDDI driver support functions and macros
|
|
The ethersubr functions provide the interface between the ethersubr module and the network drivers which need Ethernet support. Such drivers must request the ether attribute in their files declaration... |
|
ETHER_NEXT_MULTI(9) -- Ethernet and FDDI driver support functions and macros
|
|
The ethersubr functions provide the interface between the ethersubr module and the network drivers which need Ethernet support. Such drivers must request the ether attribute in their files declaration... |
|
evcnt(9) -- generic event counter framework
|
|
The NetBSD generic event counter framework is designed to provide a flexible and hierarchical event counting facility, which is useful for tracking system events (including device interrupts). The fun... |
|
evcnt_attach_dynamic(9) -- generic event counter framework
|
|
The NetBSD generic event counter framework is designed to provide a flexible and hierarchical event counting facility, which is useful for tracking system events (including device interrupts). The fun... |
|
evcnt_attach_static(9) -- generic event counter framework
|
|
The NetBSD generic event counter framework is designed to provide a flexible and hierarchical event counting facility, which is useful for tracking system events (including device interrupts). The fun... |
|
evcnt_detach(9) -- generic event counter framework
|
|
The NetBSD generic event counter framework is designed to provide a flexible and hierarchical event counting facility, which is useful for tracking system events (including device interrupts). The fun... |
|
extent(9) -- general purpose extent manager
|
|
The NetBSD extent manager provides management of areas of memory or other number spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the number... |
|
extent_alloc(9) -- general purpose extent manager
|
|
The NetBSD extent manager provides management of areas of memory or other number spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the number... |
|
extent_alloc_region(9) -- general purpose extent manager
|
|
The NetBSD extent manager provides management of areas of memory or other number spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the number... |
|
extent_alloc_subregion(9) -- general purpose extent manager
|
|
The NetBSD extent manager provides management of areas of memory or other number spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the number... |
|
extent_create(9) -- general purpose extent manager
|
|
The NetBSD extent manager provides management of areas of memory or other number spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the number... |
|
extent_destroy(9) -- general purpose extent manager
|
|
The NetBSD extent manager provides management of areas of memory or other number spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the number... |
|
extent_free(9) -- general purpose extent manager
|
|
The NetBSD extent manager provides management of areas of memory or other number spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the number... |
|
extent_print(9) -- general purpose extent manager
|
|
The NetBSD extent manager provides management of areas of memory or other number spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the number... |
|
fddi_addmulti(9) -- Ethernet and FDDI driver support functions and macros
|
|
The ethersubr functions provide the interface between the ethersubr module and the network drivers which need Ethernet support. Such drivers must request the ether attribute in their files declaration... |
|
fddi_delmulti(9) -- Ethernet and FDDI driver support functions and macros
|
|
The ethersubr functions provide the interface between the ethersubr module and the network drivers which need Ethernet support. Such drivers must request the ether attribute in their files declaration... |
|
fddi_ifattach(9) -- Ethernet and FDDI driver support functions and macros
|
|
The ethersubr functions provide the interface between the ethersubr module and the network drivers which need Ethernet support. Such drivers must request the ether attribute in their files declaration... |
|
fetch(9) -- fetch data
|
|
The fetch functions are designed to copy small amounts of data from userspace. The fetch routines provide the following functionality: fubyte() Fetches a byte of data from the user-space address base.... |
|
fork1(9) -- create a new process
|
|
fork1() creates a new process out of p1, which is assumed to be the current process. This function is used primarily to implement the fork(2) and vfork(2) system calls. The flags argument controls the... |
|
format_bytes(9) -- format a number into a human readable form
|
|
humanize_number The humanize_number() function formats the unsigned 64 bit quantity given in number into buffer. A space and then suffix is appended to the end. buffer must be at least len bytes bytes... |
|
free(9) -- kernel memory allocator
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. malloc_roundup() returns the actual size of the allocation unit for the give... |
|
FREE(9) -- kernel memory allocator
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. malloc_roundup() returns the actual size of the allocation unit for the give... |
|
fubyte(9) -- fetch data
|
|
The fetch functions are designed to copy small amounts of data from userspace. The fetch routines provide the following functionality: fubyte() Fetches a byte of data from the user-space address base.... |
|
fuibyte(9) -- fetch data
|
|
The fetch functions are designed to copy small amounts of data from userspace. The fetch routines provide the following functionality: fubyte() Fetches a byte of data from the user-space address base.... |
|
fuiword(9) -- fetch data
|
|
The fetch functions are designed to copy small amounts of data from userspace. The fetch routines provide the following functionality: fubyte() Fetches a byte of data from the user-space address base.... |
|
fuswintr(9) -- fetch data
|
|
The fetch functions are designed to copy small amounts of data from userspace. The fetch routines provide the following functionality: fubyte() Fetches a byte of data from the user-space address base.... |
|
fusword(9) -- fetch data
|
|
The fetch functions are designed to copy small amounts of data from userspace. The fetch routines provide the following functionality: fubyte() Fetches a byte of data from the user-space address base.... |
|
fuword(9) -- fetch data
|
|
The fetch functions are designed to copy small amounts of data from userspace. The fetch routines provide the following functionality: fubyte() Fetches a byte of data from the user-space address base.... |
|
getnewvnode(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
gsignal(9) -- post signal to a process
|
|
These functions post a signal to one or more processes. The argument signum common to all three functions should be in the range [1-NSIG]. The psignal() function posts signal number signum to the proc... |
|
hardclock(9) -- real-time timer
|
|
The hardclock() function gets called hz(9) times per second. It performs different tasks: +o Run the current process's virtual and profile time (decrease the corresponding timers, if they are activat... |
|
hash(9) -- kernel hash functions
|
|
The hash functions returns a hash of the given buffer. The hash32_buf() function returns a 32 bit hash of buf, which is len bytes long, seeded with an initial hash of ihash (which is usually HASH32_BU... |
|
hash32_buf(9) -- kernel hash functions
|
|
The hash functions returns a hash of the given buffer. The hash32_buf() function returns a 32 bit hash of buf, which is len bytes long, seeded with an initial hash of ihash (which is usually HASH32_BU... |
|
hash32_str(9) -- kernel hash functions
|
|
The hash functions returns a hash of the given buffer. The hash32_buf() function returns a 32 bit hash of buf, which is len bytes long, seeded with an initial hash of ihash (which is usually HASH32_BU... |
|
hash32_strn(9) -- kernel hash functions
|
|
The hash functions returns a hash of the given buffer. The hash32_buf() function returns a 32 bit hash of buf, which is len bytes long, seeded with an initial hash of ihash (which is usually HASH32_BU... |
|
holdrele(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
HOLDRELE(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
humanize_number(9) -- format a number into a human readable form
|
|
humanize_number The humanize_number() function formats the unsigned 64 bit quantity given in number into buffer. A space and then suffix is appended to the end. buffer must be at least len bytes bytes... |
|
hz(9) -- system clock frequency
|
|
hz specifies the number of times the hardclock(9) timer ticks per second. hz is hardware-dependent; it can be overridden (if the machine dependent code supports this) by defining HZ in the kernel conf... |
|
in4_cksum(9) -- compute Internet checksum
|
|
These functions are used to compute the ones-complement checksum required by IP and IPv6. The in4_cksum() function is used to compute the transport-layer checksum required by tcp(4) and udp(4) over a ... |
|
in6_cksum(9) -- compute Internet checksum
|
|
These functions are used to compute the ones-complement checksum required by IP and IPv6. The in4_cksum() function is used to compute the transport-layer checksum required by tcp(4) and udp(4) over a ... |
|
inittodr(9) -- initialize system time
|
|
The inittodr() function determines the time and sets the system clock. It tries to pick the correct time using a set of heuristics that examine the system's battery backed clock and the time reported... |
|
intro(9) -- introduction to kernel internals
|
|
This section contains information related to the internal operation of the system kernel. It describes function interfaces and variables of use to the systems and device driver programmer. In addition... |
|
in_cksum(9) -- compute Internet checksum
|
|
These functions are used to compute the ones-complement checksum required by IP and IPv6. The in4_cksum() function is used to compute the transport-layer checksum required by tcp(4) and udp(4) over a ... |
|
ioasic(9) -- baseboard I/O control ASIC for DEC TURBOchannel systems
|
|
The IOASIC device provides support for the DEC proprietary IOCTL ASIC found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems.... |
|
ioasic_attach_devs(9) -- baseboard I/O control ASIC for DEC TURBOchannel systems
|
|
The IOASIC device provides support for the DEC proprietary IOCTL ASIC found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems.... |
|
ioasic_intr_disestablish(9) -- baseboard I/O control ASIC for DEC TURBOchannel systems
|
|
The IOASIC device provides support for the DEC proprietary IOCTL ASIC found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems.... |
|
ioasic_intr_establish(9) -- baseboard I/O control ASIC for DEC TURBOchannel systems
|
|
The IOASIC device provides support for the DEC proprietary IOCTL ASIC found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems.... |
|
ioasic_intr_evcnt(9) -- baseboard I/O control ASIC for DEC TURBOchannel systems
|
|
The IOASIC device provides support for the DEC proprietary IOCTL ASIC found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems.... |
|
ioasic_submatch(9) -- baseboard I/O control ASIC for DEC TURBOchannel systems
|
|
The IOASIC device provides support for the DEC proprietary IOCTL ASIC found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems.... |
|
ioctl(9) -- how to implement a new ioctl call to access device drivers
|
|
ioctl are internally defined as #define FOOIOCTL fun(t,n,pt) where the different variables and functions are: FOOIOCTL the name which will later be given in the ioctl(2) system call as second argument... |
|
isa(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isapnp(9) -- Plug 'n' Play ISA bus
|
|
The machine-independent ISAPNP subsystem provides support for ISAPNP devices. ISAPNP devices were developed to support "plug and play" connection on the ISA bus. In all other aspects, the ISAPNP bus... |
|
isapnp_config(9) -- Plug 'n' Play ISA bus
|
|
The machine-independent ISAPNP subsystem provides support for ISAPNP devices. ISAPNP devices were developed to support "plug and play" connection on the ISA bus. In all other aspects, the ISAPNP bus... |
|
isapnp_devmatch(9) -- Plug 'n' Play ISA bus
|
|
The machine-independent ISAPNP subsystem provides support for ISAPNP devices. ISAPNP devices were developed to support "plug and play" connection on the ISA bus. In all other aspects, the ISAPNP bus... |
|
isapnp_unconfig(9) -- Plug 'n' Play ISA bus
|
|
The machine-independent ISAPNP subsystem provides support for ISAPNP devices. ISAPNP devices were developed to support "plug and play" connection on the ISA bus. In all other aspects, the ISAPNP bus... |
|
isa_dmaabort(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_dmacascade(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_dmacount(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_dmadone(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_dmamap_create(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_dmamap_destroy(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_dmamaxsize(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_dmamem_alloc(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_dmamem_free(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_dmamem_map(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_dmamem_unmap(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_dmastart(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_drq_isfree(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_free(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_intr_alloc(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_intr_disestablish(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_intr_establish(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_intr_evcnt(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_malloc(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
isa_mappage(9) -- Industry-standard Architecture
|
|
The machine-independent ISA subsystem provides support for the ISA bus. The ISA bus was introduced on the IBM PC/AT. It is an extension to the original bus found on the original IBM PC. The ISA bus is... |
|
sun3/isr_add(9) -- establish interrupt handler
|
|
The isr_add functions establish interrupt handlers into the system interrupt dispatch table and are typically called from device drivers during the autoconfiguration process. There are two types of in... |
|
sun3/isr_add_autovect(9) -- establish interrupt handler
|
|
The isr_add functions establish interrupt handlers into the system interrupt dispatch table and are typically called from device drivers during the autoconfiguration process. There are two types of in... |
|
sun3/isr_add_custom(9) -- establish interrupt handler
|
|
The isr_add functions establish interrupt handlers into the system interrupt dispatch table and are typically called from device drivers during the autoconfiguration process. There are two types of in... |
|
sun3/isr_add_vectored(9) -- establish interrupt handler
|
|
The isr_add functions establish interrupt handlers into the system interrupt dispatch table and are typically called from device drivers during the autoconfiguration process. There are two types of in... |
|
itimerfix(9) -- check that a timeval value is valid, and correct
|
|
The itimerfix function checks that the value in tv is valid (0 <= tv->tv_sec 0 <= tv->tv_usec < 1000000), and that the total time represented is at least tick. If it is smaller, then it is adjusted to... |
|
kprintf(9) -- kernel formatted output conversion
|
|
The printf() family of functions allows the kernel to send formatted messages to various output devices. The functions printf() and vprintf() send formatted strings to the system console. The function... |
|
kthread(9) -- kernel threads
|
|
Kernel threads are light-weight processes which execute entirely within the kernel. Any process can request the creation of a new kernel thread. Kernel threads are not swapped out during memory conges... |
|
kthread_create(9) -- kernel threads
|
|
Kernel threads are light-weight processes which execute entirely within the kernel. Any process can request the creation of a new kernel thread. Kernel threads are not swapped out during memory conges... |
|
kthread_create1(9) -- kernel threads
|
|
Kernel threads are light-weight processes which execute entirely within the kernel. Any process can request the creation of a new kernel thread. Kernel threads are not swapped out during memory conges... |
|
kthread_exit(9) -- kernel threads
|
|
Kernel threads are light-weight processes which execute entirely within the kernel. Any process can request the creation of a new kernel thread. Kernel threads are not swapped out during memory conges... |
|
linedisc(9) -- extensible line discipline framework
|
|
The NetBSD TTY line discipline framework allows extensibility. Modules that need special line disciplines can add them as convenient and do not need to modify tty_conf.c. Line disciplines are now mana... |
|
lock(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple threads from simultaneously executing critical sections of code accessing shared data. A number of different locks are a... |
|
lockinit(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple threads from simultaneously executing critical sections of code accessing shared data. A number of different locks are a... |
|
lockmgr(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple threads from simultaneously executing critical sections of code accessing shared data. A number of different locks are a... |
|
lockmgr_printinfo(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple threads from simultaneously executing critical sections of code accessing shared data. A number of different locks are a... |
|
lockstatus(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple threads from simultaneously executing critical sections of code accessing shared data. A number of different locks are a... |
|
log(9) -- log a message from the kernel through the /dev/klog device
|
|
The log() function allows the kernel to send messages to user processes listening on /dev/klog. Usually syslogd(8) monitors /dev/klog for these messages and writes them to a log file. All messages are... |
|
lookup(9) -- pathname lookup
|
|
The namei interface is used to convert pathnames to file system vnodes. The name of the interface is actually a contraction of the words name and inode for name-to-inode conversion, in the days before... |
|
ltsleep(9) -- process context sleep and and wakeup
|
|
These functions implement voluntary context switching. ltsleep(), tsleep() and sleep() are used throughout the kernel whenever processing in the current context can not continue for any of the followi... |
|
malloc(9) -- kernel memory allocator
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. malloc_roundup() returns the actual size of the allocation unit for the give... |
|
MALLOC(9) -- kernel memory allocator
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. malloc_roundup() returns the actual size of the allocation unit for the give... |
|
malloc_roundup(9) -- kernel memory allocator
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. malloc_roundup() returns the actual size of the allocation unit for the give... |
|
mbuf(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
mca(9) -- MicroChannel Architecture bus
|
|
The MCA device provides support for IBM's MicroChannel Architecture bus found on IBM PS/2 systems and selected workstations. It was designed as a replacement bus for the ISA bus found on IBM's older... |
|
mca_conf_read(9) -- MicroChannel Architecture bus
|
|
The MCA device provides support for IBM's MicroChannel Architecture bus found on IBM PS/2 systems and selected workstations. It was designed as a replacement bus for the ISA bus found on IBM's older... |
|
mca_conf_write(9) -- MicroChannel Architecture bus
|
|
The MCA device provides support for IBM's MicroChannel Architecture bus found on IBM PS/2 systems and selected workstations. It was designed as a replacement bus for the ISA bus found on IBM's older... |
|
mca_intr_disestablish(9) -- MicroChannel Architecture bus
|
|
The MCA device provides support for IBM's MicroChannel Architecture bus found on IBM PS/2 systems and selected workstations. It was designed as a replacement bus for the ISA bus found on IBM's older... |
|
mca_intr_establish(9) -- MicroChannel Architecture bus
|
|
The MCA device provides support for IBM's MicroChannel Architecture bus found on IBM PS/2 systems and selected workstations. It was designed as a replacement bus for the ISA bus found on IBM's older... |
|
mca_intr_evcnt(9) -- MicroChannel Architecture bus
|
|
The MCA device provides support for IBM's MicroChannel Architecture bus found on IBM PS/2 systems and selected workstations. It was designed as a replacement bus for the ISA bus found on IBM's older... |
|
MCHTYPE(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
MCLGET(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
memcmp(9) -- compare byte string
|
|
The memcmp() function compares byte string b1 against byte string b2. Both strings are assumed to be len bytes long. |
|
memcpy(9) -- copy byte string
|
|
The memcpy() function copies len bytes from string src to string dst. The arguments must not overlap -- behavior if the arguments overlap is undefined. To copy byte strings that overlap, use memmove(9... |
|
memmove(9) -- copy byte string
|
|
The memmove() function copies len bytes from string src to string dst. The two strings may overlap; the copy is always done in a non-destructive manner. |
|
memset(9) -- write a byte to byte string
|
|
The memset() function writes len bytes of value c (converted to an unsigned char) to the string b. |
|
MEXTADD(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
MEXTMALLOC(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
MEXTREMOVE(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
MFREE(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
MGET(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
MGETHDR(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
MH_ALIGN(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
microtime(9) -- realtime system clock
|
|
microtime() returns the current value of the system realtime clock in the structure pointed to by the argument tv. The system realtime clock is guaranteed to be monotonically increasing at all times. ... |
|
mi_switch(9) -- switch to another process context
|
|
The mi_switch() function implements the machine-independent prelude to a process context switch. It is called from only a few distinguished places in the kernel code as a result of the principle of no... |
|
mono_time(9) -- system time variables
|
|
The time variable is the system's ``wall time'' clock. It is set at boot by inittodr(9), and is updated by the settimeofday(2) system call and by periodic clock interrupts. The boottime variable ho... |
|
mstohz(9) -- convert milliseconds to system clock ticks
|
|
mstohz can be used to convert time in milliseconds to system clock ticks, as used by the callout(9) facility, in an integer-overflow safe way. This function is implemented as a define in the |
|
mtocl(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
mtod(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_adj(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
M_ALIGN(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_cat(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_copyback(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_copydata(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_copym(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_copypacket(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
M_COPY_PKTHDR(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_devget(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_dup(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_free(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_freem(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_get(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_getclr(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_gethdr(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
M_LEADINGSPACE(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_prepend(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
M_PREPEND(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_pulldown(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_pullup(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
m_split(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
M_TRAILINGSPACE(9) -- functions and macros for managing memory used by networking code
|
|
The mbuf functions and macros provide an easy and consistent way to handle a networking stack's memory management needs. An mbuf consists of a header and a data area. It is of a fixed size, MSIZE (de... |
|
namecache(9) -- name lookup cache
|
|
The name lookup cache is the mechanism to allow the file system type dependent algorithms to quickly resolve a file's vnode from its pathname. The name lookup cache is generally accessed through the ... |
|
namecache_print(9) -- name lookup cache
|
|
The name lookup cache is the mechanism to allow the file system type dependent algorithms to quickly resolve a file's vnode from its pathname. The name lookup cache is generally accessed through the ... |
|
namei(9) -- pathname lookup
|
|
The namei interface is used to convert pathnames to file system vnodes. The name of the interface is actually a contraction of the words name and inode for name-to-inode conversion, in the days before... |
|
NDINIT(9) -- pathname lookup
|
|
The namei interface is used to convert pathnames to file system vnodes. The name of the interface is actually a contraction of the words name and inode for name-to-inode conversion, in the days before... |
|
panic(9) -- Bring down system on fatal error
|
|
The panic() function terminates the NetBSD system. The message fmt is a printf(3) style format string which is printed to the console and saved in the variable panicstr for later retrieval via core du... |
|
pci(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_configure_bus(9) -- perform PCI bus configuration
|
|
The pci_configure_bus() function configures a PCI bus for use. This involves: +o Defining bus numbers for all busses on the system, +o Setting the Base Address Registers for all devices, +o Setting up... |
|
pci_conf_hook(9) -- perform PCI bus configuration
|
|
The pci_configure_bus() function configures a PCI bus for use. This involves: +o Defining bus numbers for all busses on the system, +o Setting the Base Address Registers for all devices, +o Setting up... |
|
pci_conf_interrupt(9) -- perform PCI bus configuration
|
|
The pci_configure_bus() function configures a PCI bus for use. This involves: +o Defining bus numbers for all busses on the system, +o Setting the Base Address Registers for all devices, +o Setting up... |
|
pci_conf_print(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_conf_read(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_conf_write(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_decompose_tag(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_devinfo(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_findvendor(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_find_device(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_get_capability(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_intr(9) -- PCI bus interrupt manipulation functions
|
|
The pci_intr functions exist to allow device drivers machine-independent access to PCI bus interrupts. The functions described in this page are typically declared in a port's ~ |
|
pci_intr_disestablish(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_intr_establish(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_intr_evcnt(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_intr_map(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_intr_string(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_make_tag(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_mapreg_info(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_mapreg_map(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pci_mapreg_type(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
PCI_PRODUCT(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
PCI_REVISION(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
PCI_VENDOR(9) -- Peripheral Component Interconnect
|
|
The machine-independent PCI subsystem provides support for PCI devices. The PCI bus was initially developed by Intel in the early 1990's to replace the ISA bus for interfacing with their Pentium proc... |
|
pcmcia(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_cis_read_1(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_cis_read_2(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_cis_read_3(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_cis_read_4(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_cis_read_n(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_function_disable(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_function_enable(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_function_init(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_intr_disestablish(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_intr_establish(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_io_alloc(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_io_free(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_io_map(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_io_unmap(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_mem_alloc(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_mem_free(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_mem_map(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_mem_unmap(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pcmcia_scan_cis(9) -- support for PCMCIA
|
|
The machine-independent PCMCIA subsystem provides support for PC-Card devices defined by the Personal Computer Memory Card International Assocation (PCMCIA). The PCMCIA bus supports insertion and remo... |
|
pfil(9) -- packet filter interface
|
|
The pfil framework allows for a specified function to be invoked for every incoming or outgoing packet for a particular network I/O stream. These hooks may be used to implement a firewall or perform p... |
|
pfil_add_hook(9) -- packet filter interface
|
|
The pfil framework allows for a specified function to be invoked for every incoming or outgoing packet for a particular network I/O stream. These hooks may be used to implement a firewall or perform p... |
|
pfil_hook_get(9) -- packet filter interface
|
|
The pfil framework allows for a specified function to be invoked for every incoming or outgoing packet for a particular network I/O stream. These hooks may be used to implement a firewall or perform p... |
|
pfil_remove_hook(9) -- packet filter interface
|
|
The pfil framework allows for a specified function to be invoked for every incoming or outgoing packet for a particular network I/O stream. These hooks may be used to implement a firewall or perform p... |
|
pgsignal(9) -- post signal to a process
|
|
These functions post a signal to one or more processes. The argument signum common to all three functions should be in the range [1-NSIG]. The psignal() function posts signal number signum to the proc... |
|
physio(9) -- initiate I/O on raw devices
|
|
The physio() is a helper function typically called from character device read and write routines to start I/O on a user process buffer. It calls back on the provided strategy routine one or more times... |
|
pmap(9) -- machine-dependent portion of the virtual memory system
|
|
The pmap module is the machine-dependent portion of the NetBSD virtual memory system uvm(9). The purpose of the pmap module is to manage physical address maps, to program the memory management hardwar... |
|
pool(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixed-sized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applic... |
|
pool_create(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixed-sized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applic... |
|
pool_destroy(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixed-sized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applic... |
|
pool_get(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixed-sized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applic... |
|
pool_init(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixed-sized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applic... |
|
pool_prime(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixed-sized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applic... |
|
pool_put(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixed-sized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applic... |
|
pool_sethiwat(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixed-sized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applic... |
|
pool_setlowat(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixed-sized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applic... |
|
powerhook_disestablish(9) -- add or remove a power change hook
|
|
The powerhook_establish() function adds fn of the list of hooks invoked by dopowerhooks(9) at power change. When invoked, the hook function fn will be passed the new power state as the first argument ... |
|
powerhook_establish(9) -- add or remove a power change hook
|
|
The powerhook_establish() function adds fn of the list of hooks invoked by dopowerhooks(9) at power change. When invoked, the hook function fn will be passed the new power state as the first argument ... |
|
ppsratecheck(9) -- function to help implement rate-limited actions
|
|
The ppsratecheck() function provides easy way to perform packet-per-sec, or event-per-sec, rate limitation. The motivation for implementing ppsratecheck() was to provide a mechanism that could be used... |
|
printf(9) -- kernel formatted output conversion
|
|
The printf() family of functions allows the kernel to send formatted messages to various output devices. The functions printf() and vprintf() send formatted strings to the system console. The function... |
|
propdb_create(9) -- generic kernel properties
|
|
The NetBSD property management routines allow kernel subsystems to associate (name, value) pairs with arbitrary keys in a generalized manner. A database is a container for a set of properties. It is c... |
|
propdb_destroy(9) -- generic kernel properties
|
|
The NetBSD property management routines allow kernel subsystems to associate (name, value) pairs with arbitrary keys in a generalized manner. A database is a container for a set of properties. It is c... |
|
properties(9) -- generic kernel properties
|
|
The NetBSD property management routines allow kernel subsystems to associate (name, value) pairs with arbitrary keys in a generalized manner. A database is a container for a set of properties. It is c... |
|
prop_copy(9) -- generic kernel properties
|
|
The NetBSD property management routines allow kernel subsystems to associate (name, value) pairs with arbitrary keys in a generalized manner. A database is a container for a set of properties. It is c... |
|
prop_delete(9) -- generic kernel properties
|
|
The NetBSD property management routines allow kernel subsystems to associate (name, value) pairs with arbitrary keys in a generalized manner. A database is a container for a set of properties. It is c... |
|
prop_get(9) -- generic kernel properties
|
|
The NetBSD property management routines allow kernel subsystems to associate (name, value) pairs with arbitrary keys in a generalized manner. A database is a container for a set of properties. It is c... |
|
prop_list(9) -- generic kernel properties
|
|
The NetBSD property management routines allow kernel subsystems to associate (name, value) pairs with arbitrary keys in a generalized manner. A database is a container for a set of properties. It is c... |
|
prop_objs(9) -- generic kernel properties
|
|
The NetBSD property management routines allow kernel subsystems to associate (name, value) pairs with arbitrary keys in a generalized manner. A database is a container for a set of properties. It is c... |
|
prop_set(9) -- generic kernel properties
|
|
The NetBSD property management routines allow kernel subsystems to associate (name, value) pairs with arbitrary keys in a generalized manner. A database is a container for a set of properties. It is c... |
|
psignal(9) -- post signal to a process
|
|
These functions post a signal to one or more processes. The argument signum common to all three functions should be in the range [1-NSIG]. The psignal() function posts signal number signum to the proc... |
|
radio(9) -- interface between low and high level radio drivers
|
|
The radio device driver is divided into a high level, hardware independent layer, and a low level hardware dependent layer. The interface between these is the radio_hw_if structure. struct radio_hw_if... |
|
rasops(9) -- raster display operations
|
|
The rasops subsystem is a set of raster operations for wscons(9). The primary data type for using the raster operations is the rasops_info structure in dev/rasops/rasops.h: struct rasops_info { /* * T... |
|
rasops_init(9) -- raster display operations
|
|
The rasops subsystem is a set of raster operations for wscons(9). The primary data type for using the raster operations is the rasops_info structure in dev/rasops/rasops.h: struct rasops_info { /* * T... |
|
rasops_reconfig(9) -- raster display operations
|
|
The rasops subsystem is a set of raster operations for wscons(9). The primary data type for using the raster operations is the rasops_info structure in dev/rasops/rasops.h: struct rasops_info { /* * T... |
|
ratecheck(9) -- function to help implement rate-limited actions
|
|
The ratecheck() function provides a simple time interval check which can be used when implementing time-based rate-limited actions. If the difference between the current monotonically-increasing syste... |
|
readdisklabel(9) -- disk label management routines
|
|
This collection of routines provides a disklabel management interface to kernel device drivers. These routines are classified as machine- or architecture-dependent because of restrictions imposed by t... |
|
relookup(9) -- pathname lookup
|
|
The namei interface is used to convert pathnames to file system vnodes. The name of the interface is actually a contraction of the words name and inode for name-to-inode conversion, in the days before... |
|
remrunqueue(9) -- manipulate system run queue
|
|
The setrunqueue and remrunqueue functions manipulate the system queue of runnable processes. The system scheduler uses this queue to find the highest-priority process when a process switch occurs. The... |
|
resettodr(9) -- set battery-backed clock from system time
|
|
The resettodr() function sets the system's battery backed clock based on the contents of the system time variable. |
|
rnd(9) -- functions to make a device available for entropy collection
|
|
These RND functions make a device available for entropy collection for /dev/random. Ideally the first argument rnd_source of these functions gets included in the devices' entity struct, but any means... |
|
rnd_add_data(9) -- functions to make a device available for entropy collection
|
|
These RND functions make a device available for entropy collection for /dev/random. Ideally the first argument rnd_source of these functions gets included in the devices' entity struct, but any means... |
|
rnd_add_uint32(9) -- functions to make a device available for entropy collection
|
|
These RND functions make a device available for entropy collection for /dev/random. Ideally the first argument rnd_source of these functions gets included in the devices' entity struct, but any means... |
|
rnd_attach_source(9) -- functions to make a device available for entropy collection
|
|
These RND functions make a device available for entropy collection for /dev/random. Ideally the first argument rnd_source of these functions gets included in the devices' entity struct, but any means... |
|
rnd_detach_source(9) -- functions to make a device available for entropy collection
|
|
These RND functions make a device available for entropy collection for /dev/random. Ideally the first argument rnd_source of these functions gets included in the devices' entity struct, but any means... |
|
rt_timer(9) -- route callout functions
|
|
The rt_timer functions provide a generic route callout functionality. They allow a function to be called for a route at any time. This was originally intended to be used to remove routes added by path... |
|
rt_timer_add(9) -- route callout functions
|
|
The rt_timer functions provide a generic route callout functionality. They allow a function to be called for a route at any time. This was originally intended to be used to remove routes added by path... |
|
rt_timer_queue_change(9) -- route callout functions
|
|
The rt_timer functions provide a generic route callout functionality. They allow a function to be called for a route at any time. This was originally intended to be used to remove routes added by path... |
|
rt_timer_queue_create(9) -- route callout functions
|
|
The rt_timer functions provide a generic route callout functionality. They allow a function to be called for a route at any time. This was originally intended to be used to remove routes added by path... |
|
rt_timer_queue_destroy(9) -- route callout functions
|
|
The rt_timer functions provide a generic route callout functionality. They allow a function to be called for a route at any time. This was originally intended to be used to remove routes added by path... |
|
rt_timer_remove_all(9) -- route callout functions
|
|
The rt_timer functions provide a generic route callout functionality. They allow a function to be called for a route at any time. This was originally intended to be used to remove routes added by path... |
|
runtime(9) -- system time variables
|
|
The time variable is the system's ``wall time'' clock. It is set at boot by inittodr(9), and is updated by the settimeofday(2) system call and by periodic clock interrupts. The boottime variable ho... |
|
scsipi(9) -- SCSI/ATAPI middle-layer interface
|
|
The scsipi system is the middle layer interface between SCSI/ATAPI host bus adapters (HBA) and high-level SCSI/ATAPI drivers. This document describes the interfaces provided by the scsipi layer toward... |
|
setdisklabel(9) -- disk label management routines
|
|
This collection of routines provides a disklabel management interface to kernel device drivers. These routines are classified as machine- or architecture-dependent because of restrictions imposed by t... |
|
setrunqueue(9) -- manipulate system run queue
|
|
The setrunqueue and remrunqueue functions manipulate the system queue of runnable processes. The system scheduler uses this queue to find the highest-priority process when a process switch occurs. The... |
|
shutdownhook_disestablish(9) -- add or remove a shutdown hook
|
|
The shutdownhook_establish() function adds fn to the list of hooks invoked by doshutdownhooks(9) at shutdown. When invoked, the hook function fn will be passed arg as its only argument. The shutdownho... |
|
shutdownhook_establish(9) -- add or remove a shutdown hook
|
|
The shutdownhook_establish() function adds fn to the list of hooks invoked by doshutdownhooks(9) at shutdown. When invoked, the hook function fn will be passed arg as its only argument. The shutdownho... |
|
simple_lock(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple threads from simultaneously executing critical sections of code accessing shared data. A number of different locks are a... |
|
simple_lock_dump(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple threads from simultaneously executing critical sections of code accessing shared data. A number of different locks are a... |
|
simple_lock_freecheck(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple threads from simultaneously executing critical sections of code accessing shared data. A number of different locks are a... |
|
simple_lock_init(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple threads from simultaneously executing critical sections of code accessing shared data. A number of different locks are a... |
|
simple_lock_try(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple threads from simultaneously executing critical sections of code accessing shared data. A number of different locks are a... |
|
simple_lock_unlock(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple threads from simultaneously executing critical sections of code accessing shared data. A number of different locks are a... |
|
sleep(9) -- process context sleep and and wakeup
|
|
These functions implement voluntary context switching. ltsleep(), tsleep() and sleep() are used throughout the kernel whenever processing in the current context can not continue for any of the followi... |
|
snprintf(9) -- kernel formatted output conversion
|
|
The printf() family of functions allows the kernel to send formatted messages to various output devices. The functions printf() and vprintf() send formatted strings to the system console. The function... |
|
softintr(9) -- machine-independent software interrupt framework
|
|
The NetBSD machine-independent software interrupt framework is designed to provide a generic software interrupt mechanism which can be used any time a low-priority callback is needed. It allows dynami... |
|
softintr_disestablish(9) -- machine-independent software interrupt framework
|
|
The NetBSD machine-independent software interrupt framework is designed to provide a generic software interrupt mechanism which can be used any time a low-priority callback is needed. It allows dynami... |
|
softintr_establish(9) -- machine-independent software interrupt framework
|
|
The NetBSD machine-independent software interrupt framework is designed to provide a generic software interrupt mechanism which can be used any time a low-priority callback is needed. It allows dynami... |
|
softintr_schedule(9) -- machine-independent software interrupt framework
|
|
The NetBSD machine-independent software interrupt framework is designed to provide a generic software interrupt mechanism which can be used any time a low-priority callback is needed. It allows dynami... |
|
spinlockinit(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple threads from simultaneously executing critical sections of code accessing shared data. A number of different locks are a... |
|
spinlockmgr(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple threads from simultaneously executing critical sections of code accessing shared data. A number of different locks are a... |
|
spl(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
spl0(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
splbio(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
splclock(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
splhigh(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
splimp(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
spllowersoftclock(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
splnet(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
splsched(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
splserial(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
splsoftclock(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
splsoftnet(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
splsoftserial(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
splstatclock(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
spltty(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
splvm(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
splx(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts in critical sections, in order to protect data structures (much like a locking primitive) or... |
|
sprintf(9) -- kernel formatted output conversion
|
|
The printf() family of functions allows the kernel to send formatted messages to various output devices. The functions printf() and vprintf() send formatted strings to the system console. The function... |
|
store(9) -- store data
|
|
The store functions are designed to copy small amounts of data to the user-space of the currently running process. The store routines provide the following functionality: subyte() Stores a byte of dat... |
|
subyte(9) -- store data
|
|
The store functions are designed to copy small amounts of data to the user-space of the currently running process. The store routines provide the following functionality: subyte() Stores a byte of dat... |
|
suibyte(9) -- store data
|
|
The store functions are designed to copy small amounts of data to the user-space of the currently running process. The store routines provide the following functionality: subyte() Stores a byte of dat... |
|
suiword(9) -- store data
|
|
The store functions are designed to copy small amounts of data to the user-space of the currently running process. The store routines provide the following functionality: subyte() Stores a byte of dat... |
|
suswintr(9) -- store data
|
|
The store functions are designed to copy small amounts of data to the user-space of the currently running process. The store routines provide the following functionality: subyte() Stores a byte of dat... |
|
susword(9) -- store data
|
|
The store functions are designed to copy small amounts of data to the user-space of the currently running process. The store routines provide the following functionality: subyte() Stores a byte of dat... |
|
suword(9) -- store data
|
|
The store functions are designed to copy small amounts of data to the user-space of the currently running process. The store routines provide the following functionality: subyte() Stores a byte of dat... |
|
tc(9) -- TURBOchannel bus
|
|
The TC device provides support for the DEC TURBOchannel bus found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems. TURBOchan... |
|
tc_badaddr(9) -- TURBOchannel bus
|
|
The TC device provides support for the DEC TURBOchannel bus found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems. TURBOchan... |
|
TC_DENSE_TO_SPARSE(9) -- TURBOchannel bus
|
|
The TC device provides support for the DEC TURBOchannel bus found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems. TURBOchan... |
|
tc_intr_disestablish(9) -- TURBOchannel bus
|
|
The TC device provides support for the DEC TURBOchannel bus found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems. TURBOchan... |
|
tc_intr_establish(9) -- TURBOchannel bus
|
|
The TC device provides support for the DEC TURBOchannel bus found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems. TURBOchan... |
|
tc_intr_evcnt(9) -- TURBOchannel bus
|
|
The TC device provides support for the DEC TURBOchannel bus found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems. TURBOchan... |
|
tc_mb(9) -- TURBOchannel bus
|
|
The TC device provides support for the DEC TURBOchannel bus found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems. TURBOchan... |
|
TC_PHYS_TO_UNCACHED(9) -- TURBOchannel bus
|
|
The TC device provides support for the DEC TURBOchannel bus found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems. TURBOchan... |
|
tc_syncbus(9) -- TURBOchannel bus
|
|
The TC device provides support for the DEC TURBOchannel bus found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems. TURBOchan... |
|
tc_wmb(9) -- TURBOchannel bus
|
|
The TC device provides support for the DEC TURBOchannel bus found on all DEC TURBOchannel machines with MIPS (DECstation 5000 series, excluding the 5000/200) and Alpha (3000-series) systems. TURBOchan... |
|
time(9) -- system time variables
|
|
The time variable is the system's ``wall time'' clock. It is set at boot by inittodr(9), and is updated by the settimeofday(2) system call and by periodic clock interrupts. The boottime variable ho... |
|
timeout(9) -- execute a function after a specified length of time
|
|
The callout facility provides a mechanism to execute a function at a given time. The timer is based on the hardclock timer which ticks hz times per second. The function is called at softclock interrup... |
|
todr(9) -- time-of-day clock support
|
|
The todr_*() functions provide an interface to read, set and control `time-of-day' devices. The todr_chip_handle_t should be obtained from a driver for a particular hardware device that implements th... |
|
todr_getcal(9) -- time-of-day clock support
|
|
The todr_*() functions provide an interface to read, set and control `time-of-day' devices. The todr_chip_handle_t should be obtained from a driver for a particular hardware device that implements th... |
|
todr_gettime(9) -- time-of-day clock support
|
|
The todr_*() functions provide an interface to read, set and control `time-of-day' devices. The todr_chip_handle_t should be obtained from a driver for a particular hardware device that implements th... |
|
todr_setcal(9) -- time-of-day clock support
|
|
The todr_*() functions provide an interface to read, set and control `time-of-day' devices. The todr_chip_handle_t should be obtained from a driver for a particular hardware device that implements th... |
|
todr_settime(9) -- time-of-day clock support
|
|
The todr_*() functions provide an interface to read, set and control `time-of-day' devices. The todr_chip_handle_t should be obtained from a driver for a particular hardware device that implements th... |
|
tprintf(9) -- kernel formatted output conversion
|
|
The printf() family of functions allows the kernel to send formatted messages to various output devices. The functions printf() and vprintf() send formatted strings to the system console. The function... |
|
tprintf_close(9) -- kernel formatted output conversion
|
|
The printf() family of functions allows the kernel to send formatted messages to various output devices. The functions printf() and vprintf() send formatted strings to the system console. The function... |
|
tprintf_open(9) -- kernel formatted output conversion
|
|
The printf() family of functions allows the kernel to send formatted messages to various output devices. The functions printf() and vprintf() send formatted strings to the system console. The function... |
|
tsleep(9) -- process context sleep and and wakeup
|
|
These functions implement voluntary context switching. ltsleep(), tsleep() and sleep() are used throughout the kernel whenever processing in the current context can not continue for any of the followi... |
|
ttyprintf(9) -- kernel formatted output conversion
|
|
The printf() family of functions allows the kernel to send formatted messages to various output devices. The functions printf() and vprintf() send formatted strings to the system console. The function... |
|
uao_create(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uao_detach(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uao_reference(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
ubc_alloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
ubc_release(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
ucom(9) -- interface for USB tty like devices
|
|
The ucom driver is a (relatively) easy way to make a USB device look like a tty(4). It basically takes two bulk pipes, input and output, and makes a tty out of them. This is useful for a number of dev... |
|
uiomove(9) -- move data described by a struct uio
|
|
The uiomove function copies up to n bytes between the kernel-space address pointed to by buf and the addresses described by uio, which may be in user-space or kernel-space. The uio argument is a point... |
|
ungetnewvnode(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
untimeout(9) -- execute a function after a specified length of time
|
|
The callout facility provides a mechanism to execute a function at a given time. The timer is based on the hardclock timer which ticks hz times per second. The function is called at softclock interrup... |
|
uprintf(9) -- kernel formatted output conversion
|
|
The printf() family of functions allows the kernel to send formatted messages to various output devices. The functions printf() and vprintf() send formatted strings to the system console. The function... |
|
usbdi(9) -- USB device drivers interface
|
|
Device driver access to the USB bus centers around transfers. A transfer describes a communication with a USB device. A transfer is an abstract concept that can result in several physical packets bein... |
|
uvm(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvmspace_alloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvmspace_exec(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvmspace_fork(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvmspace_free(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvmspace_share(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvmspace_unshare(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_chgkprot(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_coredump(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_deallocate(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_fault(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_fork(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_grow(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_init(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_init_limits(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_io(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_kernacc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_alloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_alloc1(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_free(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_free_wakeup(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_kmemalloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_suballoc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_valloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_valloc_wait(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_zalloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_loan(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_map(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_map_checkprot(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_map_pageable(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_map_protect(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_meter(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_pagealloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_pagefree(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_pageout(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_pagerealloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_page_physload(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_pglistalloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_pglistfree(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_scheduler(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_setpagesize(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_swapin(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_swap_init(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_sysctl(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_unloan(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_useracc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_vnp_setsize(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_vslock(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_vsunlock(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvn_attach(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvn_findpages(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
vaccess(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vattr(9) -- vnode attributes
|
|
Vnode attributes describe attributes of a file or directory including file permissions, owner, group, size, access time and modication time. A vnode attribute has the following structure: struct vattr... |
|
vattr_null(9) -- vnode attributes
|
|
Vnode attributes describe attributes of a file or directory including file permissions, owner, group, size, access time and modication time. A vnode attribute has the following structure: struct vattr... |
|
VATTR_NULL(9) -- vnode attributes
|
|
Vnode attributes describe attributes of a file or directory including file permissions, owner, group, size, access time and modication time. A vnode attribute has the following structure: struct vattr... |
|
vcount(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vdevgone(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vfinddev(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vflush(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vflushbuf(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vfs(9) -- kernel interface to file systems
|
|
The virtual file system, vfs, is the kernel interface to file systems. The interface specifies the calls for the kernel to access file systems. It also specifies the core functionality that a file sys... |
|
vfsops(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
VFS_CHECKEXP(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
vfs_export_lookup(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
VFS_FHTOVP(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
vfs_getnewfsid(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
VFS_MOUNT(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
VFS_QUOTACTL(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
VFS_ROOT(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
vfs_rootmountalloc(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
VFS_START(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
VFS_STATFS(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
VFS_SYNC(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
VFS_UNMOUNT(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
VFS_VGET(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
VFS_VPTOFH(9) -- kernel file system interface
|
|
In a similar fashion to the vnode(9) interface, all operations that are done on a file system are conducted through a single interface that allows the system to carry out operations on a file system w... |
|
vget(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vgone(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vhold(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
VHOLD(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vinvalbuf(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vme(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vme_dmamap_create(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vme_dmamap_destroy(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vme_dmamem_alloc(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vme_dmamem_free(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vme_intr_disestablish(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vme_intr_establish(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vme_intr_evcnt(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vme_intr_map(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vme_probe(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vme_space_alloc(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vme_space_free(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vme_space_get(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vme_space_map(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vme_space_unmap(9) -- Versa Module Euroboard bus
|
|
The VME bus provides support for VME devices. The VME bus is a high-performance backplane bus for use in computer systems. It is based on the VMEbus specification initially released by the VMEbus Inte... |
|
vnode(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vnodeops(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
vnsubr(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_bwrite(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_close(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_closefile(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_default_error(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_fcntl(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_ioctl(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_isunder(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_lock(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_markexec(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_open(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_poll(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_read(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_restorerecurse(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_setrecurse(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_stat(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_write(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
vn_writechk(9) -- high-level convenience functions for vnode operations
|
|
The high-level functions described in this page are convenience functions for simplied access to the vnode operations described in vnodeops(9). |
|
VOP_ABORTOP(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_ACCESS(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_ADVLOCK(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_BALLOC(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_BLKATOFF(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_BMAP(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_BWRITE(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_CLOSE(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_CREATE(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_FCNTL(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_FSYNC(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_GETATTR(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_GETPAGES(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_INACTIVE(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_IOCTL(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_ISLOCKED(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_LEASE(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_LINK(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_LOCK(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_LOOKUP(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_MKDIR(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_MKNOD(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_MMAP(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_OPEN(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_PATHCONF(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_POLL(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_PRINT(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_PUTPAGES(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_READ(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_READDIR(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_READLINK(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_REALLOCBLKS(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_RECLAIM(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_REMOVE(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_RENAME(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_REVOKE(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_RMDIR(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_SEEK(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_SETATTR(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_STRATEGY(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_SYMLINK(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_TRUNCATE(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_UNLOCK(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_UPDATE(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_VALLOC(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_VFREE(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_WHITEOUT(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
VOP_WRITE(9) -- vnode operations
|
|
The vnode operations vector describes what operations can be done to the file associated with the vnode. The system maintains one vnode operations vector for each file system type configured into the ... |
|
vprint(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vprintf(9) -- kernel formatted output conversion
|
|
The printf() family of functions allows the kernel to send formatted messages to various output devices. The functions printf() and vprintf() send formatted strings to the system console. The function... |
|
vput(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vrecycle(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vref(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
VREF(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vrele(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vsnprintf(9) -- kernel formatted output conversion
|
|
The printf() family of functions allows the kernel to send formatted messages to various output devices. The functions printf() and vprintf() send formatted strings to the system console. The function... |
|
vsprintf(9) -- kernel formatted output conversion
|
|
The printf() family of functions allows the kernel to send formatted messages to various output devices. The functions printf() and vprintf() send formatted strings to the system console. The function... |
|
vtruncbuf(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
vwakeup(9) -- kernel representation of a file or directory
|
|
The vnode is the focus of all file activity in NetBSD. There is a unique vnode allocated for each active file, directory, mounted-on file, fifo, domain socket, symbolic link and device. The kernel has... |
|
wakeup(9) -- process context sleep and and wakeup
|
|
These functions implement voluntary context switching. ltsleep(), tsleep() and sleep() are used throughout the kernel whenever processing in the current context can not continue for any of the followi... |
|
wdc(9) -- machine-independent IDE/ATAPI driver
|
|
The wdc driver provides the machine independent core functions for driving IDE devices. IDE devices-specific drivers ( wd or atapibus) will use services provided by wdc. The machine-dependent bus fron... |
|
writedisklabel(9) -- disk label management routines
|
|
This collection of routines provides a disklabel management interface to kernel device drivers. These routines are classified as machine- or architecture-dependent because of restrictions imposed by t... |
|
wscons(9) -- machine-independent console support
|
|
The wscons driver provides a machine-independent framework for workstation consoles. It consists of several cooperating modules: +o display adapters (see wsdisplay(9)) +o keyboards (see wskbd(9)) +o p... |
|
wsdisplay(9) -- wscons display support
|
|
The wsdisplay module is a component of the wscons(9) framework to provide machine-independent display support. Most of the support is provided by the wsdisplay(4) device driver, which must be a child ... |
|
wsdisplaydevprint(9) -- wscons display support
|
|
The wsdisplay module is a component of the wscons(9) framework to provide machine-independent display support. Most of the support is provided by the wsdisplay(4) device driver, which must be a child ... |
|
wsdisplay_cnattach(9) -- wscons display support
|
|
The wsdisplay module is a component of the wscons(9) framework to provide machine-independent display support. Most of the support is provided by the wsdisplay(4) device driver, which must be a child ... |
|
wsdisplay_switchtoconsole(9) -- wscons display support
|
|
The wsdisplay module is a component of the wscons(9) framework to provide machine-independent display support. Most of the support is provided by the wsdisplay(4) device driver, which must be a child ... |
|
wsemuldisplaydevprint(9) -- wscons display support
|
|
The wsdisplay module is a component of the wscons(9) framework to provide machine-independent display support. Most of the support is provided by the wsdisplay(4) device driver, which must be a child ... |
|
wsfont(9) -- wscons font support
|
|
The wsfont module is a component of the wscons(9) framework to provide access to display fonts. Fonts may be loaded dynamically into the kernel or included statically in the kernel at compile time. Di... |
|
wsfont_add(9) -- wscons font support
|
|
The wsfont module is a component of the wscons(9) framework to provide access to display fonts. Fonts may be loaded dynamically into the kernel or included statically in the kernel at compile time. Di... |
|
wsfont_enum(9) -- wscons font support
|
|
The wsfont module is a component of the wscons(9) framework to provide access to display fonts. Fonts may be loaded dynamically into the kernel or included statically in the kernel at compile time. Di... |
|
wsfont_find(9) -- wscons font support
|
|
The wsfont module is a component of the wscons(9) framework to provide access to display fonts. Fonts may be loaded dynamically into the kernel or included statically in the kernel at compile time. Di... |
|
wsfont_getflg(9) -- wscons font support
|
|
The wsfont module is a component of the wscons(9) framework to provide access to display fonts. Fonts may be loaded dynamically into the kernel or included statically in the kernel at compile time. Di... |
|
wsfont_init(9) -- wscons font support
|
|
The wsfont module is a component of the wscons(9) framework to provide access to display fonts. Fonts may be loaded dynamically into the kernel or included statically in the kernel at compile time. Di... |
|
wsfont_lock(9) -- wscons font support
|
|
The wsfont module is a component of the wscons(9) framework to provide access to display fonts. Fonts may be loaded dynamically into the kernel or included statically in the kernel at compile time. Di... |
|
wsfont_map_unichar(9) -- wscons font support
|
|
The wsfont module is a component of the wscons(9) framework to provide access to display fonts. Fonts may be loaded dynamically into the kernel or included statically in the kernel at compile time. Di... |
|
wsfont_matches(9) -- wscons font support
|
|
The wsfont module is a component of the wscons(9) framework to provide access to display fonts. Fonts may be loaded dynamically into the kernel or included statically in the kernel at compile time. Di... |
|
wsfont_remove(9) -- wscons font support
|
|
The wsfont module is a component of the wscons(9) framework to provide access to display fonts. Fonts may be loaded dynamically into the kernel or included statically in the kernel at compile time. Di... |
|
wsfont_unlock(9) -- wscons font support
|
|
The wsfont module is a component of the wscons(9) framework to provide access to display fonts. Fonts may be loaded dynamically into the kernel or included statically in the kernel at compile time. Di... |
|
wskbd(9) -- wscons keyboard support
|
|
The wskbd module is a component of the wscons(9) framework to provide machine-indpendent keyboard support. Most of the support is provided by the wskbd(4) device driver, which must be a child of the h... |
|
wskbddevprint(9) -- wscons keyboard support
|
|
The wskbd module is a component of the wscons(9) framework to provide machine-indpendent keyboard support. Most of the support is provided by the wskbd(4) device driver, which must be a child of the h... |
|
wskbd_cnattach(9) -- wscons keyboard support
|
|
The wskbd module is a component of the wscons(9) framework to provide machine-indpendent keyboard support. Most of the support is provided by the wskbd(4) device driver, which must be a child of the h... |
|
wskbd_cndetach(9) -- wscons keyboard support
|
|
The wskbd module is a component of the wscons(9) framework to provide machine-indpendent keyboard support. Most of the support is provided by the wskbd(4) device driver, which must be a child of the h... |
|
wskbd_input(9) -- wscons keyboard support
|
|
The wskbd module is a component of the wscons(9) framework to provide machine-indpendent keyboard support. Most of the support is provided by the wskbd(4) device driver, which must be a child of the h... |
|
wskbd_rawinput(9) -- wscons keyboard support
|
|
The wskbd module is a component of the wscons(9) framework to provide machine-indpendent keyboard support. Most of the support is provided by the wskbd(4) device driver, which must be a child of the h... |
|
wsmouse(9) -- wscons mouse support
|
|
The wsmouse module is a component of the wscons(9) framework to provide machine-indpendent mouse support. Most of the support is provided by the wsmouse(4) device driver, which must be a child of the ... |
|
wsmousedevprint(9) -- wscons mouse support
|
|
The wsmouse module is a component of the wscons(9) framework to provide machine-indpendent mouse support. Most of the support is provided by the wsmouse(4) device driver, which must be a child of the ... |
|
wsmouse_input(9) -- wscons mouse support
|
|
The wsmouse module is a component of the wscons(9) framework to provide machine-indpendent mouse support. Most of the support is provided by the wsmouse(4) device driver, which must be a child of the ... |
