Home
last modified time | relevance | path

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

12345678910>>...26

/linux/fs/squashfs/
H A DKconfig18 embedded systems where low overhead is needed. Further information
153 bool "Include support for ZLIB compressed file systems"
159 file systems. It offers a good trade-off between compression
166 bool "Include support for LZ4 compressed file systems"
170 Saying Y here includes support for reading Squashfs file systems
172 aimed at embedded systems with slower CPUs where the overheads
176 file systems will be readable without selecting this option.
181 bool "Include support for LZO compressed file systems"
185 Saying Y here includes support for reading Squashfs file systems
187 aimed at embedded systems wit
[all...]
/linux/Documentation/userspace-api/
H A 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/Documentation/userspace-api/media/dvb/
H A 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
H A 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
H A 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/Documentation/ABI/testing/
H A Dsysfs-kernel-mm-numa11 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
H A 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/kernel/
H A 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/tools/testing/selftests/rcutorture/bin/
H A Dkvm-remote.sh4 # Run a series of tests on remote systems under KVM.
6 # Usage: kvm-remote.sh "systems" [ <kvm.sh args> ]
7 # kvm-remote.sh "systems" /path/to/old/run [ <kvm-again.sh args> ]
28 systems="$1"
29 if test -z "$systems"
31 echo $scriptname: Empty list of systems will go nowhere good, giving up.
138 for i in $systems
156 # Download and expand the tarball on all systems.
158 for i in $systems
219 # Function to start batches on idle remote $systems
[all...]
/linux/drivers/hid/i2c-hid/
H A DKconfig17 This driver supports ACPI-based systems.
34 This driver supports Open Firmware (Device Tree)-based systems as
44 tristate "Driver for Elan hid-i2c based devices on OF systems"
51 systems.
60 tristate "Driver for Goodix hid-i2c based devices on OF systems"
67 systems.
/linux/sound/soc/qcom/
H A DKconfig65 APQ8016 SOC-based systems.
151 APQ8096 SoC-based systems.
166 SDM845 SoC-based systems.
178 SM8250 SoC-based systems.
190 SC8280XP SoC-based systems.
205 SC7180 SoC-based systems.
223 SC7280 SoC-based systems.
235 X1E80100 SoC-based systems.
/linux/Documentation/arch/arm64/
H A Dcpu-hotplug.rst15 CPU Hotplug on physical systems - CPUs not present at boot
18 Physical systems need to mark a CPU that is ``possible`` but not ``present`` as
25 There are no systems that support the physical addition (or removal) of CPUs
42 CPU Hotplug on virtual systems - CPUs not enabled at boot
45 Virtual systems have the advantage that all the properties the system will
49 CPU Hotplug on virtual systems is supported. It is distinct from physical
70 by the DSDT's Processor object's _STA method. On virtual systems the _STA method
/linux/Documentation/power/
H A 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/Documentation/admin-guide/cifs/
H A Dintroduction.rst9 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/Documentation/watchdog/
H A 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/fs/sysv/
H A DKconfig7 SCO, Xenix and Coherent are commercial Unix systems for Intel
13 that they contain binaries from those other Unix systems; in order
19 NOTE: that will work only for binaries from Intel-based systems;
28 (and even other operating systems) is given by the tar program ("man
/linux/net/mac80211/
H A DKconfig138 on production systems as some of the messages are
149 should not be selected on production systems as some
170 It should not be selected on production systems as some
181 be selected on production systems as those messages
192 be selected on production systems as those messages
204 It should not be selected on production systems as those
217 It should not be selected on production systems as those
230 It should not be selected on production systems as those
243 It should not be selected on production systems as those
288 It should not be selected on production systems as those
/linux/fs/fat/
H A DKconfig8 If you want to use one of the FAT-based file systems (the MS-DOS and
9 VFAT (Windows 95) file systems), then you must say Y or M here
11 diskettes with FAT-based file systems and transparently access the
16 the foundation for the other file systems. You will have to say Y or
35 cannot compile any of the FAT-based file systems into the kernel
67 This option provides support for normal Windows file systems with
68 long filenames. That includes non-compressed FAT-based file systems
/linux/Documentation/devicetree/bindings/mtd/
H A Ddiskonchip.txt8 - compatible: should be "m-systems,diskonchip-g3"
13 compatible = "m-systems,diskonchip-g3";
/linux/drivers/media/pci/intel/
H A DKconfig13 function on systems shipped with Windows.
17 Supported systems include:
/linux/arch/sh/mm/
H A DKconfig13 boot on these systems, this option must not be set.
15 On other systems (such as the SH-3 and 4) where an MMU exists,
26 On MMU-less systems, any of these page sizes can be selected
66 value on any of the known systems will only lead to disaster.
112 For systems with an MMU that can afford to give up a page,
121 Some SH systems have many various memories scattered around
/linux/include/linux/
H A Dtrace.h54 struct trace_array *trace_array_get_by_name(const char *name, const char *systems);
87 static inline struct trace_array *trace_array_get_by_name(const char *name, const char *systems) in trace_array_get_by_name() argument
/linux/arch/arm/mach-exynos/
H A DKconfig51 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/Documentation/leds/
H A 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/Documentation/hwmon/
H A Dhp-wmi-sensors.rst96 ``rate_units`` ``0`` (only exists on some systems)
116 and ``HPBIOS_PlatformEvents`` WMI objects, which vary between systems.
122 - If the existing hp-wmi driver for non-business-class HP systems is already
123 loaded, ``alarm`` attributes will be unavailable even on systems that
125 for ``alarm`` attributes is used on those systems for e.g. laptop hotkeys.

12345678910>>...26