Home
last modified time | relevance | path

Searched refs:systems (Results 1 – 25 of 661) sorted by relevance

12345678910>>...27

/Linux-v5.10/fs/squashfs/
DKconfig18 embedded systems where low overhead is needed. Further information
112 bool "Include support for ZLIB compressed file systems"
118 file systems. It offers a good trade-off between compression
125 bool "Include support for LZ4 compressed file systems"
129 Saying Y here includes support for reading Squashfs file systems
131 aimed at embedded systems with slower CPUs where the overheads
135 file systems will be readable without selecting this option.
140 bool "Include support for LZO compressed file systems"
144 Saying Y here includes support for reading Squashfs file systems
146 aimed at embedded systems with slower CPUs where the overheads
[all …]
/Linux-v5.10/Documentation/userspace-api/media/dvb/
Dfrontend.rst10 systems: Terrestrial, cable and Satellite. Currently, the following
11 delivery systems are supported:
13 - Terrestrial systems: DVB-T, DVB-T2, ATSC, ATSC M/H, ISDB-T, DVB-H,
16 - Cable systems: DVB-C Annex A/C, ClearQAM (DVB-C Annex B)
18 - Satellite systems: DVB-S, DVB-S2, DVB Turbo, ISDB-S, DSS
41 On Satellite systems, the API support for the Satellite Equipment
Ddvbproperty.rst13 systems). The actual parameters are specific to each particular digital
18 ATSC delivery systems grouped there. The problem is that, as the second
32 with supports all digital TV delivery systems.
43 3. Nowadays, most frontends support multiple delivery systems.
45 the multiple delivery systems supported by a frontend.
123 frontend-property-terrestrial-systems
124 frontend-property-cable-systems
125 frontend-property-satellite-systems
Dfe-type-t.rst80 used to contain ``fe_type_t`` field to indicate the delivery systems,
84 devices support multiple delivery systems. Please use
87 On devices that support multiple delivery systems, struct
/Linux-v5.10/Documentation/driver-api/
Ddcdbas.rst9 systems management software such as Dell OpenManage to perform system
11 power off after OS shutdown) on certain Dell systems.
13 Dell OpenManage requires this driver on the following Dell PowerEdge systems:
17 driver on other Dell systems.
27 On some Dell systems, systems management software must access certain
32 The driver creates the following sysfs entries for systems management
56 shutting down. On some Dell systems, this host control feature requires that
59 The driver creates the following sysfs entries for systems management software
/Linux-v5.10/kernel/
DKconfig.hz12 beneficial for servers and NUMA systems that do not need to have
23 100 Hz is a typical choice for servers, SMP and NUMA systems
32 on SMP and NUMA systems. If you are going to be using NTSC video
40 on SMP and NUMA systems and exactly dividing by both PAL and
46 1000 Hz is the preferred choice for desktop systems and other
47 systems requiring fast interactive responses to events.
/Linux-v5.10/Documentation/admin-guide/cifs/
Dintroduction.rst9 PC operating systems. New and improved versions of CIFS are now
18 operating systems). Apple systems also support SMB3 well, as
20 filesystem client can mount to a wide variety of systems.
33 cluster file systems for fileserving in some Linux to Linux environments,
/Linux-v5.10/Documentation/power/
Dvideo.rst22 methods work on different systems, and no known method suits all of
26 whitelist of systems, and automatically selects working method for a
33 systems. Unfortunately, vbetool only runs after userland is resumed,
40 There are a few types of systems where video works after S3 resume:
42 (1) systems where video state is preserved over S3.
44 (2) systems where it is possible to call the video BIOS during S3
49 (3) systems that initialize video card into vga text mode and where
53 (4) on some systems s3_bios kicks video into text mode, and
56 (5) radeon systems, where X can soft-boot your video card. You'll need
61 (6) other radeon systems, where vbetool is enough to bring system back
[all …]
/Linux-v5.10/Documentation/watchdog/
Dmlx-wdt.rst9 Ethernet and Infiniband switch systems.
31 Type 1 HW watchdog implementation exist in old systems and
32 all new systems have type 2 HW watchdog.
35 Type 3 HW watchdog implementation can exist on all Mellanox systems
38 Old systems still have only one main watchdog.
/Linux-v5.10/fs/sysv/
DKconfig6 SCO, Xenix and Coherent are commercial Unix systems for Intel
12 that they contain binaries from those other Unix systems; in order
18 NOTE: that will work only for binaries from Intel-based systems;
27 (and even other operating systems) is given by the tar program ("man
/Linux-v5.10/sound/hda/
DKconfig31 for systems using PulseAudio. The default 64 is chosen just
33 On x86 systems, the default is 2048 as a reasonable value for
34 most of modern systems.
/Linux-v5.10/Documentation/devicetree/bindings/mtd/
Ddiskonchip.txt8 - compatible: should be "m-systems,diskonchip-g3"
13 compatible = "m-systems,diskonchip-g3";
/Linux-v5.10/fs/fat/
DKconfig6 If you want to use one of the FAT-based file systems (the MS-DOS and
7 VFAT (Windows 95) file systems), then you must say Y or M here
9 diskettes with FAT-based file systems and transparently access the
14 the foundation for the other file systems. You will have to say Y or
33 cannot compile any of the FAT-based file systems into the kernel
65 This option provides support for normal Windows file systems with
66 long filenames. That includes non-compressed FAT-based file systems
/Linux-v5.10/net/mac80211/
DKconfig128 on production systems as some of the messages are
139 should not be selected on production systems as some
160 It should not be selected on production systems as some
171 be selected on production systems as those messages
182 be selected on production systems as those messages
194 It should not be selected on production systems as those
207 It should not be selected on production systems as those
220 It should not be selected on production systems as those
233 It should not be selected on production systems as those
278 It should not be selected on production systems as those
/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-class-rc-nuvoton12 Note: Some systems reset the stored wakeup sequence to a
13 factory default on each boot. On such systems store the
/Linux-v5.10/Documentation/i2c/
Dsummary.rst10 systems. Some systems use variants that don't meet branding requirements,
26 use its protocols on many I2C systems. However, there are systems that don't
/Linux-v5.10/Documentation/arm64/
Dperf.rst62 performed differently on VHE and non-VHE systems.
64 For non-VHE systems we exclude EL2 for exclude_host - upon entering and
68 For VHE systems we exclude EL1 for exclude_guest and exclude both EL0,EL2
88 On VHE systems there are no blackout windows.
/Linux-v5.10/drivers/thermal/tegra/
DKconfig9 Tegra systems-on-chip. The driver supports four thermal zones
19 Tegra systems-on-chip with the BPMP coprocessor (Tegra186).
/Linux-v5.10/arch/ia64/
DKconfig131 This choice is safe for all IA-64 systems, but may not perform
132 optimally on systems with, say, Itanium 2 or newer processors.
152 size). For Itanium 2 or newer systems, a page size of 64KB can also
191 UV based systems. If you have an SGI UV system or are building a
200 sx1000 systems. If you're unsure, answer Y.
217 This enables support for systems with more than one CPU. If you have
222 systems, but will use only one CPU of a multiprocessor system. If
224 single processor systems. On a single processor system, the kernel
282 Tiger4 systems are capable of re-directing CPEI to any CPU other than BSP.
316 server systems. If in doubt, say N.
[all …]
/Linux-v5.10/fs/udf/
DKconfig8 file system is supported by multiple operating systems and is more
9 compatible with standard unix file systems, it is also suitable for
/Linux-v5.10/drivers/media/platform/marvell-ccic/
DKconfig13 generation OLPC systems.
29 in OLPC XO 1.75 systems.
/Linux-v5.10/arch/arm/mach-exynos/
DKconfig58 Samsung Exynos3 (Cortex-A7) SoC based systems
68 Samsung Exynos4 (Cortex-A9) SoC based systems
74 Samsung Exynos5 (Cortex-A15/A7) SoC based systems
/Linux-v5.10/Documentation/leds/
Dleds-mlxcpld.rst2 Kernel driver for Mellanox systems LEDs
5 Provide system LED support for the nex Mellanox systems:
11 Driver provides the following LEDs for the systems "msx6710", "msx6720",
/Linux-v5.10/Documentation/devicetree/bindings/display/
Dsm501fb.txt19 - little-endian: available on big endian systems, to
21 - big-endian: available on little endian systems, to
/Linux-v5.10/kernel/rcu/
DKconfig15 smaller systems.
23 designed for very large SMP systems with hundreds or
26 smaller systems.
35 designed for UP systems from which real-time response
129 systems, but if you are stress-testing the RCU implementation
131 code paths on small(er) systems.
150 lock contention levels acceptably low. Very large systems
154 initialization. These systems tend to run CPU-bound, and thus
164 Select the maximum permissible value for large systems, but

12345678910>>...27