/freebsd/sys/contrib/device-tree/Bindings/usb/ |
H A D | ulpi.txt | 4 Phys that are behind a ULPI connection can be described with the following
|
/freebsd/sys/vm/ |
H A D | vm_fault.c | 1301 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 D | etcetera | 17 # behind GMT but uses the completely misleading abbreviation "GMT". 41 # the abbreviation "-04" and corresponds to 4 hours behind UT
|
H A D | calendars | 64 getting there only 13 years behind the original schedule.
|
/freebsd/sys/contrib/device-tree/Bindings/i2c/ |
H A D | i2c-gate.txt | 23 Kasei ak8975 compass behind a gate.
|
H A D | i2c-mux-ltc4306.txt | 19 multiplexers on the bus and the devices behind them use same I2C addresses.
|
H A D | i2c-mux-pca954x.yaml | 56 the devices behind them use same I2C addresses.
|
H A D | i2c-mux-pca954x.txt | 32 multiplexers on the bus and the devices behind them use same I2C addresses.
|
H A D | i2c-mux-gpmux.yaml | 59 However, I2C transactions to devices behind all I2C multiplexers connected
|
H A D | i2c-mux-gpmux.txt | 37 However, I2C transactions to devices behind all I2C multiplexers connected
|
/freebsd/tools/test/stress2/ |
H A D | README | 7 The key idea behind stress2 is to randomize as much as possible in
|
/freebsd/sys/contrib/device-tree/src/arm64/marvell/ |
H A D | ac5-98dx25xx.dtsi | 208 * Dedicated section for devices behind 32bit controllers so we 211 behind-32bit-controller@7f000000 {
|
/freebsd/sys/contrib/device-tree/Bindings/crypto/ |
H A D | hisilicon,hip07-sec.txt | 22 - iommus: The SEC units are behind smmu-v3 iommus.
|
/freebsd/crypto/openssh/contrib/ |
H A D | README | 10 which allows the use of outbound SSH from behind a SOCKS4, SOCKS5 or
|
/freebsd/sys/contrib/device-tree/src/arm/microchip/ |
H A D | at91-ariag25.dts | 77 /* TWD2+TCLK2 hidden behind ethernet, so no i2c2 */
|
/freebsd/crypto/openssl/ssl/statem/ |
H A D | README.md | 4 This file provides some guidance on the thinking behind the design of the
|
/freebsd/crypto/openssl/ssl/record/ |
H A D | README.md | 4 This file provides some guidance on the thinking behind the design of the
|
/freebsd/crypto/openssl/doc/man3/ |
H A D | PEM_X509_INFO_read_bio_ex.pod | 44 The idea behind this is that if, for instance, a certificate is followed by
|
/freebsd/sys/contrib/device-tree/Bindings/memory-controllers/ |
H A D | exynos-srom.yaml | 14 extra properties, describing the bus behind it, should be specified.
|
/freebsd/contrib/ntp/html/hints/ |
H A D | aix | 48 > the current time was behind psx_ctime. Since this state
|
/freebsd/crypto/openssl/doc/man7/ |
H A D | RAND.pod | 42 The intention behind using a dedicated CSPRNG exclusively for private
|
/freebsd/sys/contrib/device-tree/Bindings/pci/ |
H A D | pci.txt | 19 may be assigned to root buses behind different host bridges. The domain
|
/freebsd/contrib/libcbor/doc/source/ |
H A D | development.rst | 10 attempts to set out the basic principles of libcbor and the rationale behind
|
H A D | internal.rst | 4 …al choices made during design & implementation and to explicate the reasoning behind those choices.
|
/freebsd/contrib/tzcode/ |
H A D | calendars | 64 getting there only 13 years behind the original schedule.
|