| /freebsd-14.2/sys/contrib/device-tree/Bindings/ |
| H A D | .yamllint | 10 min-spaces-inside: 0 11 max-spaces-inside: 1 12 min-spaces-inside-empty: 0 13 max-spaces-inside-empty: 0 15 min-spaces-inside: 0 16 max-spaces-inside: 1 17 min-spaces-inside-empty: 0 18 max-spaces-inside-empty: 0
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/crypto/ |
| H A D | inside-secure-safexcel.txt | 4 - compatible: Should be "inside-secure,safexcel-eip197b", 5 "inside-secure,safexcel-eip197d" or 6 "inside-secure,safexcel-eip97ies". 21 - "inside-secure,safexcel-eip197" is equivalent to 22 "inside-secure,safexcel-eip197b". 23 - "inside-secure,safexcel-eip97" is equivalent to 24 "inside-secure,safexcel-eip97ies". 29 compatible = "inside-secure,safexcel-eip197b";
|
| /freebsd-14.2/tools/tools/whereintheworld/ |
| H A D | whereintheworld.pl | 15 my $inside = 0; 25 $inside = !$inside; 31 if ($inside && $line =~ /^>>>/) {
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/rng/ |
| H A D | omap_rng.txt | 9 - "inside-secure,safexcel-eip76" for SoCs with EIP76 IP block 14 Used for "ti,omap4-rng" and "inside-secure,safexcel-eip76" 16 "inside-secure,safexcel-eip76" compatible, the second clock is 34 compatible = "inside-secure,safexcel-eip76";
|
| H A D | omap_rng.yaml | 17 - inside-secure,safexcel-eip76 50 - inside-secure,safexcel-eip76 75 compatible = "inside-secure,safexcel-eip76";
|
| /freebsd-14.2/sbin/pfctl/tests/files/ |
| H A D | pf0005.in | 3 inside="10.0.0.0/8" 5 block in proto udp from $inside port { echo, $foo, ident } \
|
| /freebsd-14.2/sbin/natd/samples/ |
| H A D | natd.cf.sample | 46 # the inside network is all RFC1918 addresses. 70 # ipconfig must apply any legal IP numbers that inside hosts 76 # DNS in this situation can get hairy. For example, an inside host 85 # NAT, because inside hosts will go through the NAT to get to the legal 86 # number, even when the inside number is on the same subnet as they are!
|
| /freebsd-14.2/sys/contrib/openzfs/module/lua/ |
| H A D | README.zfs | 50 useful inside ZFS / the kernel. We have changed the runtime to use int64_t 53 neither of these make sense from inside channel programs. We have removed 56 version of Lua runs inside the kernel we must handle these failures and 59 4. Running poorly-vetted code inside the kernel is always a risk; even if the 68 Lua source code at the ioctl level and then interpret it inside the kernel.
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/input/ |
| H A D | dlink,dir685-touchkeys.txt | 5 board inside the router is named E119921. 7 The touchkey device node should be placed inside an I2C bus node.
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/mips/ |
| H A D | cpu_irq.txt | 9 Below is an example of a platform describing the cascade inside the devicetree 10 and the code used to load it inside arch_init_irq().
|
| /freebsd-14.2/crypto/openssl/util/ |
| H A D | withlibctx.pl | 132 my $inside = shift @rets; 134 $outline .= $1.'('.$inside.')';
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/perf/ |
| H A D | amlogic,g12-ddr-pmu.yaml | 14 A timer is inside and can generate interrupt when timeout. 32 - description: The IRQ of the inside timer timeout.
|
| /freebsd-14.2/sys/arm64/arm64/ |
| H A D | disassem.c | 500 int inside; in disasm() local 646 inside = 1; in disasm() 650 inside = 0; in disasm() 655 inside = 1; in disasm() 661 if (inside != 0) { in disasm()
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/clock/ |
| H A D | stericsson,u8500-clks.yaml | 13 description: While named "U8500 clocks" these clocks are inside the 53 5, 6. The second cell indicates which clock inside the PRCC block it 67 second cell indicates which clock inside the PRCC block it wants, possible 81 5 and 6. The second cell indicates which reset line inside the PRCC block
|
| H A D | ux500.txt | 20 cell indicates which clock inside the PRCC block it wants, 26 cell indicates which clock inside the PRCC block it wants,
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/gpio/ |
| H A D | mediatek,mt7621-gpio.yaml | 13 The IP core used inside these SoCs has 3 banks of 32 GPIOs each. 14 The registers of all the banks are interwoven inside one single IO range.
|
| H A D | mediatek,mt7621-gpio.txt | 3 The IP core used inside these SoCs has 3 banks of 32 GPIOs each. 4 The registers of all the banks are interwoven inside one single IO range.
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/mmc/ |
| H A D | sdhci-st.txt | 10 subsystem (mmcss) inside the FlashSS (available in STiH407 SoC 27 to configure DLL inside the flashSS, if so reg-names must also be 32 for eMMC on stih407 family silicon to configure DLL inside FlashSS.
|
| /freebsd-14.2/sys/ufs/ffs/ |
| H A D | ffs_tables.c | 47 int inside[9] = { variable
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/interconnect/ |
| H A D | qcom,bcm-voter.yaml | 47 # Example 1: apps bcm_voter on SDM845 SoC should be defined inside &apps_rsc node 55 # Example 2: disp bcm_voter on SDM845 should be defined inside &disp_rsc node
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/leds/ |
| H A D | qcom,spmi-flash-led.yaml | 7 title: Flash LED device inside Qualcomm Technologies, Inc. PMICs 13 Flash LED controller is present inside some Qualcomm Technologies, Inc. PMICs.
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/phy/ |
| H A D | phy-miphy365x.txt | 12 register offset inside the sysconfig group. 16 'reg' and 'reg-names' properties are used inside these
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/net/dsa/ |
| H A D | vitesse,vsc73xx.txt | 17 reside inside a SPI bus device tree node, see spi/spi-bus.txt 21 must reside inside a platform bus device tree node.
|
| /freebsd-14.2/contrib/bmake/unit-tests/ |
| H A D | directive-include-guard.mk | 308 INCS+= variable-undef-inside 309 LINES.variable-undef-inside= \
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/sound/ |
| H A D | inno-rk3036.txt | 3 Inno audio codec is integrated inside RK3036 SoC.
|