Searched refs:systems (Results 1 – 25 of 751) sorted by relevance
12345678910>>...31
| /linux-6.1.9/fs/squashfs/ |
| D | Kconfig | 18 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-6.1.9/Documentation/ABI/testing/ |
| D | sysfs-kernel-mm-numa | 11 Page migration during reclaim is intended for systems
12 with tiered memory configurations. These systems have
14 characteristics instead of plain NUMA systems where
17 systems to migrate pages from fast tiers to slow tiers
23 on systems which need strict cpuset location
|
| D | sysfs-class-rc-nuvoton | 12 Note: Some systems reset the stored wakeup sequence to a
13 factory default on each boot. On such systems store the
|
| /linux-6.1.9/Documentation/userspace-api/media/dvb/ |
| D | frontend.rst | 10 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
|
| D | dvbproperty.rst | 13 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
|
| D | fe-type-t.rst | 80 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-6.1.9/Documentation/driver-api/ |
| D | dcdbas.rst | 9 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-6.1.9/kernel/ |
| D | Kconfig.hz | 12 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-6.1.9/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-remote.sh | 28 systems="$1"
29 if test -z "$systems"
31 echo $scriptname: Empty list of systems will go nowhere good, giving up.
139 for i in $systems
153 for i in $systems
208 # Function to start batches on idle remote $systems
220 for i in $systems
263 for i in $systems
|
| /linux-6.1.9/drivers/hid/i2c-hid/ |
| D | Kconfig | 12 This driver supports ACPI-based systems.
27 This driver supports Open Firmware (Device Tree)-based systems.
36 tristate "Driver for Elan hid-i2c based devices on OF systems"
42 systems.
51 tristate "Driver for Goodix hid-i2c based devices on OF systems"
57 systems.
|
| /linux-6.1.9/Documentation/admin-guide/cifs/ |
| D | introduction.rst | 9 PC operating systems. New and improved versions of CIFS are now
17 support and tools for Linux and many other operating systems).
18 Apple systems also support SMB3 well, as do most Network Attached
20 wide variety of systems. It also supports mounting to the cloud
33 cluster file systems for fileserving in some Linux to Linux environments,
|
| /linux-6.1.9/Documentation/power/ |
| D | video.rst | 22 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-6.1.9/sound/soc/qcom/ |
| D | Kconfig | 65 APQ8016 SOC-based systems.
151 APQ8096 SoC-based systems.
165 SDM845 SoC-based systems.
177 SM8250 SoC-based systems.
189 SC8280XP SoC-based systems.
204 SC7180 SoC-based systems.
221 SC7280 SoC-based systems.
|
| /linux-6.1.9/Documentation/watchdog/ |
| D | mlx-wdt.rst | 9 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-6.1.9/fs/sysv/ |
| D | Kconfig | 6 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-6.1.9/Documentation/devicetree/bindings/mtd/ |
| D | diskonchip.txt | 8 - compatible: should be "m-systems,diskonchip-g3"
13 compatible = "m-systems,diskonchip-g3";
|
| /linux-6.1.9/net/mac80211/ |
| D | Kconfig | 128 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-6.1.9/fs/fat/ |
| D | Kconfig | 6 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-6.1.9/arch/ia64/ |
| D | Kconfig | 126 This choice is safe for all IA-64 systems, but may not perform
127 optimally on systems with, say, Itanium 2 or newer processors.
147 size). For Itanium 2 or newer systems, a page size of 64KB can also
186 UV based systems. If you have an SGI UV system or are building a
195 sx1000 systems. If you're unsure, answer Y.
212 This enables support for systems with more than one CPU. If you have
217 systems, but will use only one CPU of a multiprocessor system. If
219 single processor systems. On a single processor system, the kernel
271 Tiger4 systems are capable of re-directing CPEI to any CPU other than BSP.
297 server systems. If in doubt, say N.
[all …]
|
| /linux-6.1.9/arch/arm/mach-exynos/ |
| D | Kconfig | 51 Samsung Exynos3 (Cortex-A7) SoC based systems
61 Samsung Exynos4 (Cortex-A9) SoC based systems
67 Samsung Exynos5 (Cortex-A15/A7) SoC based systems
|
| /linux-6.1.9/arch/alpha/ |
| D | Kconfig | 129 For systems using the Digital ALCOR chipset: 5 chips (4, 64-bit data
139 XL-233 and XL-266-based Alpha systems.
152 Cabriolet AlphaPC64, AlphaPCI64 systems. Derived from EB64+ but now
160 Various 21264 systems with the tsunami core logic chipset.
202 of the first-generation Alpha systems. A number of these systems
218 AlphaServer 2100A-based systems.
235 AlphaServer 1000-based Alpha systems.
240 Alpha systems based on the AMD 751 & ALI 1543C chipsets.
250 systems.
282 Digital AlphaServer 2000 and 2100-based systems.
[all …]
|
| /linux-6.1.9/Documentation/i2c/ |
| D | summary.rst | 10 systems. Some systems use variants that don't meet branding requirements,
28 use its protocols on many I2C systems. However, there are systems that don't
|
| /linux-6.1.9/fs/udf/ |
| D | Kconfig | 8 file system is supported by multiple operating systems and is more
9 compatible with standard unix file systems, it is also suitable for
|
| /linux-6.1.9/Documentation/leds/ |
| D | leds-mlxcpld.rst | 2 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-6.1.9/drivers/media/platform/marvell/ |
| D | Kconfig | 17 generation OLPC systems.
34 in OLPC XO 1.75 systems.
|
12345678910>>...31