Searched full:located (Results 1 – 25 of 804) sorted by relevance
12345678910>>...33
| /linux-5.10/drivers/net/ethernet/agere/ |
| D | et131x.h | 88 * located at address 0x0010
147 /* Loopback reg located at address 0x0034
153 * Located at address 0x0000
184 * located at address 0x1004
189 * located at address 0x1008
194 * map. Located at address 0x100C
237 * Located at address 0x1000
272 * Located at address 0x2000
301 * located at address 0x2004
306 * located at address 0x2008
[all …]
|
| /linux-5.10/drivers/net/ethernet/intel/ |
| D | Kconfig | 30 can be located at:
48 to the Adapter & Driver ID Guide that can be located at:
68 can be located at:
96 to the Adapter & Driver ID Guide that can be located at:
132 Driver ID Guide that can be located at:
149 to the Adapter & Driver ID Guide that can be located at:
168 to the Adapter & Driver ID Guide that can be located at:
220 adapter, go to the Adapter & Driver ID Guide that can be located at:
247 to the Adapter & Driver ID Guide that can be located at:
280 & Driver ID Guide that can be located at:
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/watchdog/ |
| D | mpc8xxx-wdt.txt | 17 On the 83xx, it is located at offset 0x910
18 On the 86xx, it is located at offset 0xe0094
19 On the 8xx, it is located at offset 0x288
|
| /linux-5.10/Documentation/devicetree/bindings/net/ |
| D | marvell-orion-net.txt | 43 - marvell,tx-sram-addr: address of transmit descriptor buffer located in SRAM.
44 - marvell,tx-sram-size: size of transmit descriptor buffer located in SRAM.
46 - marvell,rx-sram-addr: address of receive descriptor buffer located in SRAM.
47 - marvell,rx-sram-size: size of receive descriptor buffer located in SRAM.
|
| /linux-5.10/Documentation/hwmon/ |
| D | smsc47b397.rst | 40 pair is located at the HWM Base Address + 0 and the HWM Base Address + 1. The
46 The temperature information is located in the following registers:
70 The fan speed information is located in the following registers:
121 In configuration mode, the INDEX PORT is located at the CONFIG PORT address and
146 The following is an example of how to read the SIO Device ID located at 0x20:
173 The following is an example of how to read the HWM Base Address located in
|
| /linux-5.10/drivers/staging/media/omap4iss/ |
| D | iss.h | 159 * @res: memory resource in which the register is located
174 * @res: memory resource in which the register is located
188 * @res: memory resource in which the register is located
204 * @res: memory resource in which the register is located
220 * @res: memory resource in which the register is located
|
| /linux-5.10/tools/perf/arch/s390/util/ |
| D | machine.c | 30 * size located at the beginning of the module. in arch__fix_module_text_start()
38 /* On s390 kernel text segment start is located at very low memory addresses,
39 * for example 0x10000. Modules are located at very high memory addresses,
|
| /linux-5.10/drivers/net/dsa/mv88e6xxx/ |
| D | global1_vtu.c | 354 /* VTU DBNum[3:0] are located in VTU Operation 3:0 in mv88e6250_g1_vtu_getnext()
355 * VTU DBNum[5:4] are located in VTU Operation 9:8 in mv88e6250_g1_vtu_getnext()
387 /* VTU DBNum[3:0] are located in VTU Operation 3:0 in mv88e6185_g1_vtu_getnext()
388 * VTU DBNum[7:4] are located in VTU Operation 11:8 in mv88e6185_g1_vtu_getnext()
484 /* VTU DBNum[3:0] are located in VTU Operation 3:0 in mv88e6250_g1_vtu_loadpurge()
485 * VTU DBNum[5:4] are located in VTU Operation 9:8 in mv88e6250_g1_vtu_loadpurge()
513 /* VTU DBNum[3:0] are located in VTU Operation 3:0 in mv88e6185_g1_vtu_loadpurge()
514 * VTU DBNum[7:4] are located in VTU Operation 11:8 in mv88e6185_g1_vtu_loadpurge()
|
| /linux-5.10/Documentation/kbuild/ |
| D | modules.rst | 99 The directory where the kernel source is located.
107 located.
117 The default will build the module(s) located in the current
175 located in Documentation/kbuild/makefiles.rst.
328 of the kernel that are located in different directories, then
334 include/scsi; and architecture specific headers are located
340 To include a header file located under include/linux/, simply
352 include/ directory where their source is located, although this
397 As you can see, kbuild knows how to handle object files located
407 file is located.
|
| /linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-rf-tuner.rst | 68 signal path. It is located very close to tuner antenna input. Used
76 located inside mixer block, where RF signal is down-converted by the
82 located on output of RF tuner. It controls signal level of
|
| /linux-5.10/Documentation/admin-guide/ |
| D | binderfs.rst | 8 located in a new binderfs instance are independent of binder devices located in
62 binder device located under /dev/binderfs with the chosen name.
|
| /linux-5.10/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-plugins.txt | 26 The _tep_load_plugins()_ function loads all plugins, located in the plugin
36 - User's plugin directory, located at _~/.local/lib/traceevent/plugins_
43 _TEP_DISABLE_SYS_PLUGINS_ - do not load plugins, located in
|
| /linux-5.10/drivers/gpu/drm/i915/gt/shaders/ |
| D | README | 28 * IGT gpu tools source code is located on your home directory (~) as ~/igt
29 * Mesa source code is located on your home directory (~) as ~/mesa
|
| /linux-5.10/Documentation/devicetree/bindings/clock/ |
| D | exynos4-clock.txt | 46 subsystem. Registers for those clocks are located in the ISP power domain.
47 Because those registers are also located in a different memory region than
|
| /linux-5.10/Documentation/firmware-guide/acpi/ |
| D | aml-debugger.rst | 30 The resultant userspace tool binary is then located at::
55 The detailed debugger commands reference is located in Chapter 12 "ACPICA
|
| /linux-5.10/drivers/net/ethernet/intel/ice/ |
| D | ice_flow.h | 154 u16 val; /* Offset where the value is located */
155 u16 mask; /* Offset where the mask/prefix value is located */
156 u16 last; /* Length or offset where the upper value is located */
|
| /linux-5.10/drivers/scsi/qedf/ |
| D | qedf_hsi.h | 297 __le16 ox_id /* OX_ID that is located in the FCP_RSP FC header */;
298 __le16 rx_id /* RX_ID that is located in the FCP_RSP FC header */;
300 /* PARAM that is located in the FCP_RSP FC header */
|
| /linux-5.10/Documentation/power/ |
| D | swsusp-and-swap-files.rst | 22 header is located. For convenience, this offset is expressed in <PAGE_SIZE>
42 where <swap_file_partition> is the partition on which the swap file is located
|
| /linux-5.10/drivers/pcmcia/ |
| D | cardbus.c | 61 * @s: the pcmcia_socket where the CardBus device is located
101 * @s: the pcmcia_socket where the CardBus device was located
|
| /linux-5.10/Documentation/devicetree/bindings/cpufreq/ |
| D | cpufreq-st.txt | 16 Located in CPU's node:
38 Located in CPU's node:
|
| /linux-5.10/Documentation/devicetree/bindings/soc/fsl/ |
| D | bman.txt | 31 The BMan revision information is located in the BMAN_IP_REV_1/2 registers which
32 are located at offsets 0xbf8 and 0xbfc
|
| /linux-5.10/Documentation/scsi/ |
| D | cxgb3i.rst | 56 * in the case of recompiling the kernel, the cxgb3i selection is located at::
63 2. Create an interface file located under /etc/iscsi/ifaces/ for the new
|
| /linux-5.10/fs/crypto/ |
| D | crypto.c | 150 * it. In the bounce page, the ciphertext block(s) will be located at the same
151 * offsets at which the plaintext block(s) were located in the source page; any
215 * Encrypt a possibly-compressed filesystem block that is located in an
284 * Decrypt a possibly-compressed filesystem block that is located in an
|
| /linux-5.10/Documentation/arm/ |
| D | memory.rst | 49 by fix_to_virt() will be located here.
58 located here through iotable_init().
|
| D | porting.rst | 25 to be located in RAM, it can be in flash or other read-only or
89 it must be located at 32768 bytes into a 128MB region. Previous
|
12345678910>>...33