Home
last modified time | relevance | path

Searched refs:behind (Results 1 – 25 of 96) sorted by relevance

1234

/freebsd/sys/contrib/device-tree/Bindings/usb/
H A Dulpi.txt4 Phys that are behind a ULPI connection can be described with the following
/freebsd/sys/vm/
H A Dvm_fault.c1301 int ahead, behind, cluster_offset, rv; in vm_fault_getpages() local
1352 behind = 0; in vm_fault_getpages()
1357 behind = 0; in vm_fault_getpages()
1371 behind = ulmin(cluster_offset, in vm_fault_getpages()
1377 *behindp = behind; in vm_fault_getpages()
1538 int ahead, behind, faultcount, rv; in vm_fault() local
1636 res = vm_fault_object(&fs, &behind, &ahead); in vm_fault()
1641 faultcount = behind + 1 + ahead; in vm_fault()
1762 faultcount > 0 ? behind : PFBAK, in vm_fault()
1792 PAGE_SIZE + behind * PAGE_SIZE); in vm_fault()
/freebsd/contrib/tzdata/
H A Detcetera17 # behind GMT but uses the completely misleading abbreviation "GMT".
41 # the abbreviation "-04" and corresponds to 4 hours behind UT
H A Dcalendars64 getting there only 13 years behind the original schedule.
/freebsd/sys/contrib/device-tree/Bindings/i2c/
H A Di2c-gate.txt23 Kasei ak8975 compass behind a gate.
H A Di2c-mux-ltc4306.txt19 multiplexers on the bus and the devices behind them use same I2C addresses.
H A Di2c-mux-pca954x.yaml56 the devices behind them use same I2C addresses.
H A Di2c-mux-pca954x.txt32 multiplexers on the bus and the devices behind them use same I2C addresses.
H A Di2c-mux-gpmux.yaml59 However, I2C transactions to devices behind all I2C multiplexers connected
H A Di2c-mux-gpmux.txt37 However, I2C transactions to devices behind all I2C multiplexers connected
/freebsd/tools/test/stress2/
H A DREADME7 The key idea behind stress2 is to randomize as much as possible in
/freebsd/sys/contrib/device-tree/src/arm64/marvell/
H A Dac5-98dx25xx.dtsi208 * Dedicated section for devices behind 32bit controllers so we
211 behind-32bit-controller@7f000000 {
/freebsd/sys/contrib/device-tree/Bindings/crypto/
H A Dhisilicon,hip07-sec.txt22 - iommus: The SEC units are behind smmu-v3 iommus.
/freebsd/crypto/openssh/contrib/
H A DREADME10 which allows the use of outbound SSH from behind a SOCKS4, SOCKS5 or
/freebsd/sys/contrib/device-tree/src/arm/microchip/
H A Dat91-ariag25.dts77 /* TWD2+TCLK2 hidden behind ethernet, so no i2c2 */
/freebsd/crypto/openssl/ssl/statem/
H A DREADME.md4 This file provides some guidance on the thinking behind the design of the
/freebsd/crypto/openssl/ssl/record/
H A DREADME.md4 This file provides some guidance on the thinking behind the design of the
/freebsd/crypto/openssl/doc/man3/
H A DPEM_X509_INFO_read_bio_ex.pod44 The idea behind this is that if, for instance, a certificate is followed by
/freebsd/sys/contrib/device-tree/Bindings/memory-controllers/
H A Dexynos-srom.yaml14 extra properties, describing the bus behind it, should be specified.
/freebsd/contrib/ntp/html/hints/
H A Daix48 > the current time was behind psx_ctime. Since this state
/freebsd/crypto/openssl/doc/man7/
H A DRAND.pod42 The intention behind using a dedicated CSPRNG exclusively for private
/freebsd/sys/contrib/device-tree/Bindings/pci/
H A Dpci.txt19 may be assigned to root buses behind different host bridges. The domain
/freebsd/contrib/libcbor/doc/source/
H A Ddevelopment.rst10 attempts to set out the basic principles of libcbor and the rationale behind
H A Dinternal.rst4 …al choices made during design & implementation and to explicate the reasoning behind those choices.
/freebsd/contrib/tzcode/
H A Dcalendars64 getting there only 13 years behind the original schedule.

1234