| /freebsd/share/doc/smm/02.config/ |
| H A D | 2.t | 48 available hardware
52 configuration description. Each system image is configured
53 for identical hardware, but may have different locations for the root
60 indicates if the system is going to operate on a DEC VAX-11\(dg computer,
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.
77 (Other VAX cpu types, including the 8650, 785 and 725, are configured using
80 more than one cpu type implies that the system should be configured to run
92 (Co-VAX), Kim (No-VAX), and so on. The system identifier selected is used to
96 code in the driver which understood how to handle this non-standard hardware
[all …]
|
| H A D | 5.t | 34 sample VAX-11/780 system on which the hardware can be
35 reconfigured to guard against various hardware mishaps.
36 We then study the rules needed to configure a VAX-11/750
39 VAX-11/780 System
41 Our VAX-11/780 is configured with hardware
43 (this is one of the high-end configurations).
44 Table 1 lists the pertinent hardware to be configured.
69 Table 1. VAX-11/780 Hardware support.
111 Finally, the hardware must be specified. Let us first just try
162 VAX-11/750 with network support
[all …]
|
| H A D | 3.t | 35 and that, initially, the system is being configured from source code.
49 configured system with
76 which the configured system is to be built.
97 must be specified. The specification of the hardware present may take
98 a bit of work; particularly if your hardware is configured at non-standard
104 the system. If the devices to be configured are not already
138 system supports, which define the hardware configured.
163 directory for the system just configured and type ``make depend''
190 should allow a new system to be rebuilt by simply typing ``make image-name''.
199 Thus, if you have configured ``kernel'' to be a system with the root file
[all …]
|
| /freebsd/share/man/man4/ |
| H A D | hwpmc.4 | 1 .\" Copyright (c) 2003-2008 Joseph Koshy
36 .Nd "Hardware Performance Monitoring Counter support"
39 .Bd -ragged -offset indent
44 .Bd -ragged -offset indent
49 .Bd -literal -offset indent
54 .Bd -ragged -offset indent
62 .Bd -ragged -offset indent
71 driver virtualizes the hardware performance monitoring facilities in
75 The driver supports multi-processor systems.
89 .Bl -tag -width ".Em Process-scope"
[all …]
|
| H A D | vxlan.4 | 35 .Bd -ragged -offset indent
42 .Bd -literal -offset indent
95 interface may be configured in either unicast or multicast mode.
128 configuration would be a physical interface configured as
133 segment is identified by a 24-bit value in the
139 When configured with the
150 Otherwise, when configured in multicast mode,
174 specification recommends the physical network MTU be configured
194 .Sh HARDWARE
197 driver supports hardware checksum offload (receive and transmit) and TSO on the
[all …]
|
| H A D | ath.4 | 1 .\"-
2 .\" Copyright (c) 2002-2009 Sam Leffler, Errno Consulting
39 .Bd -ragged -offset indent
49 .Bd -literal -offset indent
61 IBSS, MBSS, WDS/DWDS TDMA, and host-based access point operation modes.
70 AR5210-based devices support 802.11a operation with transmit speeds
72 AR5211-based devices support 802.11a and 802.11b operation with transmit
75 AR5212-based devices support 802.11a, 802.11b, and 802.11g operation
83 only interoperable with other Atheros-based devices.)
84 AR5212-based and AR5416-based devices also support half- (10MHz) and quarter-width (5MHz) channels.
[all …]
|
| H A D | wpi.4 | 1 .\"-
2 .\" SPDX-License-Identifier: BSD-2-Clause
4 .\" Copyright (c) 2004-2007
42 .Bd -ragged -offset indent
63 .Cm adhoc-demo ,
69 and can be configured at runtime with
73 Only one virtual interface may be configured at any time.
77 driver can be configured to use
79 Wi-Fi Protected Access (WPA-PSK and WPA2-PSK).
88 hardware for the CCMP cipher.
[all …]
|
| H A D | iicbus.4 | 41 system provides a uniform, modular and architecture-independent
49 easy way to connect a CPU to peripheral chips in a TV-set.
71 As mentioned before, the IC bus is a Multi-MASTER BUS.
77 .Bl -column "Device drivers" -compact
84 The I2C protocol may be implemented by hardware or software.
86 interfaces rely on very simple hardware, usually two lines
88 Hardware interfaces are more intelligent and receive
89 8-bit characters they write to the bus according to the I2C protocol.
92 bidirectional communications, thanks to the multi-master capabilities of the
97 .Bl -column "Interface drivers" -compact
[all …]
|
| H A D | watchdog.4 | 1 .\" Copyright (c) 2004 Poul-Henning Kamp <phk@FreeBSD.org>
31 .Nd "hardware and software watchdog"
37 facility is used for controlling hardware and software watchdogs.
49 power of two nanoseconds, or-ed with a flag selecting active or passive control
71 By default, this will be a hardware watchdog if one is present, but if
72 no hardware watchdog is able to process the request, a default software
78 be explicitly re-enabled.
91 .Bl -tag -width "WDIOC_SETSOFTTIMEOUTACT int "
99 get the pre-timeout
101 set the pre-timeout
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/pinctrl/ |
| H A D | renesas,rza1-pinctrl.txt | 4 named "Ports" in the hardware reference manual.
5 Pin multiplexing and GPIO configuration is performed on a per-pin basis
6 writing configuration values to per-port register sets.
12 -------------------
15 - compatible: should be:
16 - "renesas,r7s72100-ports": for RZ/A1H
17 - "renesas,r7s72101-ports", "renesas,r7s72100-ports": for RZ/A1M
18 - "renesas,r7s72102-ports": for RZ/A1L
20 - reg
22 hardware is mapped to.
[all …]
|
| H A D | renesas,rza1-ports.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/renesas,rza1-port
[all...] |
| /freebsd/lib/libpmc/pmu-events/arch/arm64/arm/cortex-a55/ |
| H A D | cache.json | 105 …hardware prefetcher which cause an allocation into the L3 cache. Note It might not be possible to …
108 …hardware prefetcher which cause an allocation into the L3 cache. Note It might not be possible to …
111 …configured with a per-core L2 cache: This event does not count. +//0 If the core is configured wit…
114 …configured with a per-core L2 cache: This event does not count. +//0 If the core is configured wit…
117 …This event counts any linefills from the prefetcher which cause an allocation into the L1 D-cache",
120 … This event counts any linefills from the prefetcher which cause an allocation into the L1 D-cache"
123 … streaming mode. This event counts for each cycle where the core is in write-streaming mode and no…
126 … streaming mode. This event counts for each cycle where the core is in write-streaming mode and no…
129 …ta cache entering write streaming mode.This event counts for each entry into write-streaming mode",
132 …ata cache entering write streaming mode.This event counts for each entry into write-streaming mode"
[all …]
|
| /freebsd/lib/libpmc/ |
| H A D | pmc.3 | 1 .\" Copyright (c) 2003-2008 Joseph Koshy. All rights reserved.
29 .Nd library for accessing hardware performance monitoring counters
38 hardware performance counters to gather performance data about
40 The library is implemented using the lower-level facilities offered by
50 .Bl -bullet
53 These PMCs measure events in a whole-system manner, i.e., independent
57 Non-privileged process are allowed to allocate system scope PMCs if the
61 is non-zero.
64 These PMCs only measure hardware events when the processes they are
72 .Bl -bullet
[all …]
|
| /freebsd/lib/libpmc/pmu-events/arch/arm64/arm/cortex-a65/ |
| H A D | cache.json | 111 … prefetch. Counts any linefills from the prefetcher which cause an allocation into the L1 D-cache",
114 …o prefetch. Counts any linefills from the prefetcher which cause an allocation into the L1 D-cache"
117 …configured with a per-core L2 cache: This event does not count. +//0 If the core is configured wit…
120 …configured with a per-core L2 cache: This event does not count. +//0 If the core is configured wit…
123 …hardware prefetcher which cause an allocation into the L3 cache. Note It might not be possible to …
126 …hardware prefetcher which cause an allocation into the L3 cache. Note It might not be possible to …
141 … streaming mode. This event counts for each cycle where the core is in write-streaming mode and no…
144 … streaming mode. This event counts for each cycle where the core is in write-streaming mode and no…
147 … streaming mode. This event counts for each cycle where the core is in write-streaming mode and no…
150 … streaming mode. This event counts for each cycle where the core is in write-streaming mode and no…
[all …]
|
| /freebsd/stand/forth/ |
| H A D | menu.4th.8 | 1 .\" Copyright (c) 2011-2013 Devin Teske
53 file, so it is not needed (and should not be re-issued) in a normal setup.
57 .Bl -tag -width disable-module_module -compact -offset indent
58 .It Ic menu-init
60 This should be called before any other menu-related functions.
61 .It Ic menu-display
62 Displays the menu (configured via the below documented environment variables)
64 .It Ic menu-erase
66 .It Ic menu-redraw
68 .Ic menu-erase
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/dma/xilinx/ |
| H A D | xilinx_dma.txt | 2 It can be configured to have one channel or two channels. If configured
7 target devices. It can be configured to have one channel or two channels.
8 If configured as two channels, one is to transmit to the device and another
11 Xilinx AXI CDMA engine, it does transfers between memory-mapped source
12 address and a memory-mapped destination address.
15 target devices. It can be configured to have up to 16 independent transmit
19 - compatible: Should be one of-
20 "xlnx,axi-vdm
[all...] |
| /freebsd/sys/sys/ |
| H A D | gpio.h | 3 /*-
4 * SPDX-License-Identifier: (BSD-2-Clause AND ISC)
68 #define GPIO_PIN_OPENDRAIN 0x00000004 /* open-drain output */
69 #define GPIO_PIN_PUSHPULL 0x00000008 /* push-pull output */
71 #define GPIO_PIN_PULLUP 0x00000020 /* internal pull-up enabled */
72 #define GPIO_PIN_PULLDOWN 0x00000040 /* internal pull-down enabled */
75 #define GPIO_PIN_PULSATE 0x00000200 /* pulsate in hardware */
93 char gp_name[GPIOMAXNAME]; /* human-readable name */
105 * Reporting gpio pin-change per-event details to userland.
107 * When configured for detail reporting, each call to read(2) will return one or
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/hwmon/ |
| H A D | ti,lm87.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Texas Instruments LM87 Hardware Monitor
11 - Javier Carrasco <javier.carrasco.cruz@gmail.com>
14 The LM87 is a serial interface system hardware monitor
27 has-temp3:
32 are configured as voltage input pins in0 and in5.
34 has-in6:
37 When set, pin 5 is configured to be used as voltage input
[all …]
|
| /freebsd/usr.sbin/pmcstat/ |
| H A D | pmcstat.8 | 1 .\" Copyright (c) 2003-2008 Joseph Koshy
31 .Nd "performance measurement with performance monitoring hardware"
45 .Op Fl P Ar event-spec
47 .Op Fl S Ar event-spec
52 .Op Fl c Ar cpu-spec
62 .Op Fl p Ar event-spec
65 .Op Fl s Ar event-spec
66 .Op Fl t Ar process-spec
67 .Op Fl u Ar event-spec
80 utility can measure both hardware events seen by the system as a
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/opp/ |
| H A D | opp-v2-base.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Viresh Kumar <viresh.kumar@linaro.org>
13 Devices work at voltage-current-frequency combinations and some implementations
25 pattern: '^opp-table(-[a-z0-9]+)?$'
27 opp-shared:
36 '^opp(-?[0-9]+)*$':
39 One or more OPP nodes describing voltage-current-frequency combinations.
[all …]
|
| /freebsd/contrib/wpa/src/ap/ |
| H A D | hw_features.c | 2 * hostapd / Hardware feature query and different modes
3 * Copyright 2002-2003, Instant802 Networks, Inc.
4 * Copyright 2005-2006, Devicescape Software, Inc.
5 * Copyright (c) 2008-2012, Jouni Malinen <j@w1.fi>
51 switch (chan->flag & HOSTAPD_CHAN_DFS_MASK) { in dfs_info()
68 info[sizeof(info) - 1] = '\0'; in dfs_info()
77 struct hostapd_data *hapd = iface->bss[0]; in hostapd_get_hw_features()
87 return -1; in hostapd_get_hw_features()
93 "Fetching hardware channel/rate support not " in hostapd_get_hw_features()
95 return -1; in hostapd_get_hw_features()
[all …]
|
| /freebsd/share/man/man4/man4.arm/ |
| H A D | imx_wdog.4 | 36 .Bd -ragged -offset indent
43 .Bd -literal -offset indent
52 The i.MX watchdog hardware supports programmable timeouts ranging from
53 0.5 to 128 seconds, in half-second increments.
54 Once activated, the watchdog hardware cannot be deactivated, but the
55 timeout period can be changed to any valid non-zero value.
57 At power-on, a special 16-second
58 .Sq power-down timer
59 mode is automatically enabled by the hardware.
61 external hardware that causes the system to reset or power-down.
[all …]
|
| /freebsd/share/man/man9/ |
| H A D | watchdog.9 | 2 .\" Copyright (c) 2004 Poul-Henning Kamp <phk@FreeBSD.org>
30 .Nd "software and hardware watchdog facility"
38 To implement a watchdog in software or hardware, only a single
57 Else the watchdog should be reset and configured to a timeout of
63 If the watchdog cannot be configured to the proposed timeout, it
69 times out, but a hardware reset or similar
75 .An -nosplit
79 .An Poul-Henning Kamp Aq Mt phk@FreeBSD.org .
|
| /freebsd/sys/contrib/device-tree/Bindings/soc/fsl/ |
| H A D | bman.txt | 3 Copyright (C) 2008 - 2014 Freescale Semiconductor Inc.
7 - BMan Node
8 - BMan Private Memory Node
9 - Example
13 The Buffer Manager is part of the Data-Path Acceleration Architecture (DPAA).
14 BMan supports hardware allocation and deallocation of buffers belonging to pools
20 - compatible
24 May include "fsl,<SoC>-bman"
26 - reg
28 Value type: <prop-encoded-array>
[all …]
|
| H A D | fsl,qman-fqd.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/fsl/fsl,qman-fqd.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Frank Li <Frank.Li@nxp.com>
15 This memory is reserved/allocated as a node under the /reserved-memory node.
19 a node under the /reserved-memory node.
21 The QMan FQD memory node must be named "qman-fqd"
22 The QMan PFDR memory node must be named "qman-pfdr"
23 The BMan FBPR memory node must be named "bman-fbpr"
[all …]
|