| /freebsd/sys/contrib/device-tree/Bindings/pci/ |
| H A D | snps,dw-pcie-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pci
[all...] |
| H A D | designware-pcie.txt | 4 - compatible:
5 "snps,dw-pcie" for RC mode;
6 "snps,dw-pcie-ep" for EP mode;
7 - reg: For designware cores version < 4.80 contains the configuration
9 the configuration and ATU address space
10 - reg-names: Must be "config" for the PCIe configuration space and "atu" for
12 (The old way of getting the configuration address space from "ranges"
15 - #address-cells: set to <3>
16 - #size-cells: set to <2>
17 - device_type: set to "pci"
[all …]
|
| /freebsd/share/man/man9/ |
| H A D | iflibdd.9 | 6 .Nd Device Dependent Configuration Functions
75 .Ss "Device Configuration Functions"
189 The above named functions are device dependent configuration functions.
193 .Ss Device Dependent Functions
195 .Bl -ohang -offset indent
221 .Bl -ohang -offset indent
243 .Ss Device Configuration Functions
244 .Bl -ohang -offset indent
260 The driver sets the appropriate link type and speed in ifmr->ifm_active.
282 .Bl -ohang -offset indent
[all …]
|
| H A D | iflibdi.9 | 6 .Nd Device Independent Configuration Functions
106 .Bl -tag -width ".Va if_capabilities" -offset indent
172 They are independent of the underlying hardware type or configuration.
174 .Bl -ohang -offset indent
181 Unregister vlan events, drain any dependent tasks, and release irq, pci, and
184 Suspend a device by calling the device dependent suspend function and
187 Resume a device by calling the device dependent resume function, the
208 Calls led_create to initialize the ctx->ifc_led_dev field
|
| H A D | kmsan.9 | 1 .\"-
36 .Pa GENERIC-KMSAN
37 kernel configuration can be used to compile a KMSAN-enabled kernel using
39 as a base configuration.
41 kernel configuration file:
42 .Bd -ragged -offset indent
73 runtime component and use hidden, byte-granular shadow state to determine
94 In addition to compiler-detected uses of uninitialized memory,
114 The sanitizer in a KMSAN-configured kernel can be disabled by setting the loader
139 mark device-written memory as initialized.
[all …]
|
| /freebsd/sys/dev/xdma/controller/ |
| H A D | pl330.h | 1 /*-
2 * Copyright (c) 2017-2018 Ruslan Bukin <br@bsdpad.com>
6 * Cambridge Computer Laboratory under DARPA/AFRL contract FA8750-10-C-0237
38 #define INT_EVENT_RIS 0x024 /* Event-Interrupt Raw Status */
67 #define DBGINST0 0xD08 /* Debug Instruction-0 */
68 #define DBGINST1 0xD0C /* Debug Instruction-1 */
69 #define CR0 0xE00 /* Configuration Register 0 */
70 #define CR1 0xE04 /* Configuration Register 1 */
71 #define CR2 0xE08 /* Configuration Register 2 */
72 #define CR3 0xE0C /* Configuration Register 3 */
[all …]
|
| /freebsd/sys/dev/isp/ |
| H A D | DriverManual.txt | 42 and MD (Machine Dependent) portions. The original design therefore was
54 PCI and SBus SCSI cards, and now also drove the QLogic 2100 FC-AL HBA.
56 After this, ports to non-NetBSD platforms became interesting as well.
65 mode support has been added, and 2300 support as well as an FC-IP stack
71 Normally you design via top-down methodologies and set an initial goal
76 as I perceive them to be now- not necessarily what they started as.
90 as well as private loop and private loop, direct-attach topologies.
91 FC-IP support is also a goal.
119 The QLogic HBA cards all contain a tiny 16-bit RISC-like processor and
122 to a set of dual-ranked 16 bit incoming and outgoing mailbox registers
[all …]
|
| /freebsd/share/doc/smm/01.setup/ |
| H A D | 1.t | 58 configuration files into the new system.
70 (3)\0\0 6250bpi 2400' 9-track magnetic tapes, or
76 The tapes contain \*(Bb-byte records.
78 end-of-tape is signaled by a double end-of-file.
79 The first file on the tape is architecture dependent.
93 The standalone system syntax is currently architecture dependent and is
105 refers to the raw (``r'') interface of 9-track tape (``mt'') unit ``0''.
108 to a logical unit number is dependent on the system configuration.
117 advantage of to make the system less dependent on the interconnect
153 they are normally restricted to full-sector transfers.
|
| H A D | 4.t | 35 or when the system configuration changes. Procedures for normal
37 .Sh 2 "Kernel configuration"
75 lfs log-based filesystem
77 nfs Sun-compatible network filesystem
80 fdesc access to per-process file descriptors
95 netiso ISO protocols (TP-4, CLNP, CLTP, etc)
103 hp300 HP 9000/300 series of Motorola 68000-based machines
104 hp code common to both HP 68k and (non-existent) PA-RISC ports
105 i386 Intel 386/486-based PC machines
106 luna68k Omron 68000-based workstations
[all …]
|
| /freebsd/share/doc/smm/02.config/ |
| H A D | 3.t | 39 Create a configuration file for the system.
45 on the configuration file to generate the files required
57 Steps 1 and 2 are usually done only once. When a system configuration
60 on the modified configuration file, rebuild the source code dependencies,
62 however, configuration dependencies may not be noticed in which case
66 Creating a configuration file
68 Configuration files normally reside in the directory ``/sys/conf''.
69 A configuration file is most easily constructed by copying an
70 existing configuration file and modifying it. The 4.4BSD distribution
71 contains a number of configuration files for machines at Berkeley;
[all …]
|
| H A D | 6.t | 34 some of the inner workings of the configuration process as
45 how to add non-standard system facilities to 4.4BSD,
51 If you wish to make site-specific modifications to the system
69 We try to isolate our site-dependent code in individual files
70 which may be configured with pseudo-device specifications.
72 Indicate machine-specific code with ``#ifdef vax'' (or other machine,
75 machines with similar architectures\- you may someday find
79 Adding non-standard system facilities
83 data base files for non-standard system facilities.
106 \fIdir/source.c\fP \fItype\fP \fIoption-list\fP \fImodifiers\fP
[all …]
|
| H A D | 2.t | 28 .\".ds RH "Configuration File Contents
31 CONFIGURATION FILE CONTENTS
33 A system configuration must include at least the following
52 configuration description. Each system image is configured
60 indicates if the system is going to operate on a DEC VAX-11\(dg computer,
68 configuration files.
75 For example, if the system is being configured for a VAX-11, it could
76 be running on a VAX 8600, VAX-11/780, VAX-11/750, VAX-11/730 or MicroVAX II.
92 (Co-VAX), Kim (No-VAX), and so on. The system identifier selected is used to
93 create a global C ``#define'' which may be used to isolate system dependent
[all …]
|
| /freebsd/contrib/tcpdump/ |
| H A D | INSTALL.md | 6 "run-time" version. You can also install The Tcpdump Group version of
22 `AUTORECONF=autoreconf-2.69 ./autogen.sh`
28 control the configuration of tcpdump; `./configure --help` will show
40 depends on the OS and the configuration of the system; see the
52 (`tcpdump --version` can be used to tell different versions apart).
64 CHANGES - description of differences between releases
65 CONTRIBUTING.md - guidelines for contributing
66 CREDITS - people that have helped tcpdump along
67 INSTALL.md - this file
68 LICENSE - the license under which tcpdump is distributed
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/dma/ |
| H A D | atmel-dma.txt | 4 - compatible: Should be "atmel,<chip>-dma".
5 - reg: Should contain DMA registers location and length.
6 - interrupts: Should contain DMA interrupt.
7 - #dma-cells: Must be <2>, used to represent the number of integer cells in
13 compatible = "atmel,at91sam9g45-dma";
16 #dma-cells = <2>;
20 described in the dma.txt file, using a three-cell specifier for each channel:
27 3. Parameters for the at91 DMA configuration register which are device
28 dependent:
29 - bit 7-0: peripheral identifier for the hardware handshaking interface. The
[all …]
|
| H A D | st,stm32-dma.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/st,stm32-dma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The STM32 DMA is a general-purpose direct memory access controller capable of
13 described in the dma.txt file, using a four-cell specifier for each
17 3. A 32bit mask specifying the DMA channel configuration which are device
18 dependent:
19 -bit 9: Peripheral Increment Address
22 -bit 10: Memory Increment Address
[all …]
|
| /freebsd/sys/contrib/dev/acpica/common/ |
| H A D | ahpredef.c | 3 * Module Name: ahpredef - Table of all known ACPI predefined names
11 * Some or all of this work - Copyright (c) 1999 - 2025, Intel Corp.
28 * 2.3. Intel grants Licensee a non-exclusive and non-transferable patent
104 * re-exports any such software from a foreign destination, Licensee shall
105 * ensure that the distribution and export/re-export of the software is in
108 * any of its subsidiaries will export/re-export any technical data, process,
130 * 3. Neither the names of the above-listed copyright holders nor the names
174 …AH_PREDEF ("_ACx", "Active Cooling, x=0-9", "Returns the active cooling policy threshold values…
183 AH_PREDEF ("_ALx", "Active List, x=0-9", "Returns a list of active cooling device objects"),
187 AH_PREDEF ("_ATT", "Type-Specific Attribute", "Resource Descriptor field"),
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/mmc/ |
| H A D | aspeed,sdhci.yaml | 1 # SPDX-License-Identifier: GPL-2.0-or-later
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Andrew Jeffery <andrew@aj.id.au>
12 - Ryan Chen <ryanchen.aspeed@gmail.com>
19 The two slots are supported by a common configuration area. As the SDHCIs for
20 the slots are dependent on the common configuration area, they are described
26 - aspeed,ast2400-sd-controller
27 - aspeed,ast2500-sd-controller
28 - aspeed,ast2600-sd-controller
[all …]
|
| /freebsd/contrib/ntp/ |
| H A D | README | 18 read WHERE-TO-START.
29 INSTALL Generic installation instructions for autoconf-based programs.
37 README.bk Instructions for folks who use the BitKeeper-repository
44 WHERE-TO-START Hints on what to read in order to get a working
45 configuration.
47 Makefile.am Automake file configuration file. Edit only if you have the
53 for HP/UX systems prior to HP-UX 10.0.
72 configuration files for various systems. For example only.
77 config.h.in Configuration file generated automatically from
84 configure.in Master configuration template. Edit only if you have the
[all …]
|
| /freebsd/contrib/sendmail/include/sm/ |
| H A D | config.h | 2 * Copyright (c) 2000-2003 Proofpoint, Inc. and its suppliers.
9 * $Id: config.h,v 1.49 2013-11-22 20:51:31 ca Exp $
13 ** libsm configuration macros.
14 ** The values of these macros are platform dependent.
17 ** in the m4 configuration file in devtools/OS.
40 ** Configuration macros that specify how __P is defined.
56 ** Configuration macro that specifies whether strlcpy/strlcat are available.
66 ** Configuration macro indicating that setitimer is available
114 ** Configuration macro indicating that shared memory is available
143 /* try LLONG tests in libsm/t-types.c? */
[all …]
|
| /freebsd/usr.bin/tip/tip/ |
| H A D | Makefile | 11 # DEC DF02-AC, DF03-AC
12 # DEC DN-11/Able Quadracall
20 # Configuration defines:
37 CFLAGS+=-I${.CURDIR} -DDEFBR=9600 -DDEFFS=BUFSIZ -DACULOG -DPRISTINE \
38 -DCONNECT -DV831 -DVENTEL -DHAYES -DCOURIER -DT3000
45 # -- acutab is configuration dependent, and so depends on the Makefile
46 # -- remote.o depends on the Makefile because of DEFBR and DEFFS
47 # -- log.o depends on the Makefile because of ACULOG
56 # is no cu(1) with the schg-bit set.
59 -chflags noschg ${DESTDIR}${BINDIR}/cu
|
| /freebsd/sys/contrib/device-tree/Bindings/dma/stm32/ |
| H A D | st,stm32-dma.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/stm32/st,stm32-dma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The STM32 DMA is a general-purpose direct memory access controller capable of
13 described in the dma.txt file, using a four-cell specifier for each
17 3. A 32bit mask specifying the DMA channel configuration which are device
18 dependent:
19 -bit 9: Peripheral Increment Address
22 -bit 10: Memory Increment Address
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/usb/ |
| H A D | chipidea,usb2-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/chipidea,usb2-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Xu Yang <xu.yang_2@nxp.com>
25 clock-names:
31 power-domains:
37 reset-names:
40 "#reset-cells":
45 itc-setting:
[all …]
|
| /freebsd/contrib/ntp/html/ |
| H A D | orphan.html | 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
4 <meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
12 <!-- #BeginDate format:En2m -->4-Aug-2011 23:40<!-- #EndDate -->
16 …ng the local clock driver, primarily that the subnet is vulnerable to single-point failures and mu…
17 <p>A common configuration for private networks includes one or more core servers operating at the l…
19 …ervers. However, sufficient headroom should remain so every subnet host dependent on the orphan ch…
27 …o, monospace">tos</font> command in the configuration file. Each orphan child should include in th…
29 <p>Figure 1. Orphan Peer Configuration</p>
31 …configuration in Figure 1, where two or more campus primary or secondary (stratum 2) servers are c…
33 <p>Figure 2. Orphan Broadcast Configuration</p>
|
| /freebsd/sys/contrib/device-tree/Bindings/hwmon/ |
| H A D | ti,ina2xx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Krzysztof Kozlowski <krzk@kernel.org>
14 The INA209 is a high-side current shunt and power monitor with
23 - ti,ina209
24 - ti,ina219
25 - ti,ina220
26 - ti,ina226
27 - ti,ina230
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/reset/ |
| H A D | st,stih407-picophyreset.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reset/st,stih407-picophyreset.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Peter Griffin <peter.griffin@linaro.org>
14 disable on-chip PicoPHY USB2 phy(s) using "softreset" control bits found in
15 the STi family SoC system configuration registers.
17 The actual action taken when softreset is asserted is hardware dependent.
24 const: st,stih407-picophyreset
26 '#reset-cells':
[all …]
|