Searched refs:systems (Results 1 – 25 of 1305) sorted by relevance
12345678910>>...53
| /kernel/linux/linux-4.19/fs/squashfs/ |
| D | Kconfig | 17 embedded systems where low overhead is needed. Further information
111 bool "Include support for ZLIB compressed file systems"
117 file systems. It offers a good trade-off between compression
124 bool "Include support for LZ4 compressed file systems"
128 Saying Y here includes support for reading Squashfs file systems
130 aimed at embedded systems with slower CPUs where the overheads
134 file systems will be readable without selecting this option.
139 bool "Include support for LZO compressed file systems"
143 Saying Y here includes support for reading Squashfs file systems
145 aimed at embedded systems with slower CPUs where the overheads
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/kernel/ |
| D | Kconfig.hz | 11 beneficial for servers and NUMA systems that do not need to have
22 100 Hz is a typical choice for servers, SMP and NUMA systems
31 on SMP and NUMA systems. If you are going to be using NTSC video
39 on SMP and NUMA systems and exactly dividing by both PAL and
45 1000 Hz is the preferred choice for desktop systems and other
46 systems requiring fast interactive responses to events.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | dcdbas.txt | 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
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-4.19/Documentation/power/ |
| D | video.txt | 21 methods work on different systems, and no known method suits all of
25 whitelist of systems, and automatically selects working method for a
32 systems. Unfortunately, vbetool only runs after userland is resumed,
39 There are a few types of systems where video works after S3 resume:
41 (1) systems where video state is preserved over S3.
43 (2) systems where it is possible to call the video BIOS during S3
48 (3) systems that initialize video card into vga text mode and where
52 (4) on some systems s3_bios kicks video into text mode, and
55 (5) radeon systems, where X can soft-boot your video card. You'll need
60 (6) other radeon systems, where vbetool is enough to bring system back
[all …]
|
| /kernel/linux/linux-4.19/arch/ia64/ |
| D | Kconfig | 144 DIG-compliant For DIG ("Developer's Interface Guide") compliant systems
145 DIG+Intel+IOMMU For DIG systems with Intel IOMMU
146 HP-zx1/sx1000 For HP systems
147 HP-zx1/sx1000+swiotlb For HP systems with (broken) DMA-constrained devices.
148 SGI-SN2 For SGI Altix systems
149 SGI-UV For SGI UV systems
166 Build a kernel that runs on HP zx1 and sx1000 systems. This adds
173 Build a kernel that runs on HP zx1 and sx1000 systems even when they
185 systems, but the resulting kernel binary will not run on other
186 types of ia64 systems. If you have an SGI Altix system, it's safe
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/cifs/ |
| D | introduction.rst | 9 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,
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-4.19/Documentation/filesystems/cifs/ |
| D | cifs.txt | 5 PC operating systems. New and improved versions of CIFS are now
10 server support for Linux and many other operating systems), Apple
11 systems, as well as most Network Attached Storage vendors, so
24 cluster file systems for fileserving in some Linux to Linux environments,
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/fs/sysv/ |
| D | Kconfig | 5 SCO, Xenix and Coherent are commercial Unix systems for Intel
11 that they contain binaries from those other Unix systems; in order
17 NOTE: that will work only for binaries from Intel-based systems;
26 (and even other operating systems) is given by the tar program ("man
|
| /kernel/linux/linux-4.19/Documentation/i2c/ |
| D | summary | 8 I2C is widely used with embedded systems. Some systems use variants that
19 use its protocols on many I2C systems. However, there are systems that don't
|
| /kernel/linux/linux-5.10/sound/hda/ |
| D | Kconfig | 31 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.
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/mtd/ |
| D | diskonchip.txt | 8 - compatible: should be "m-systems,diskonchip-g3"
13 compatible = "m-systems,diskonchip-g3";
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/ |
| D | diskonchip.txt | 8 - compatible: should be "m-systems,diskonchip-g3"
13 compatible = "m-systems,diskonchip-g3";
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/fs/fat/ |
| D | Kconfig | 5 If you want to use one of the FAT-based file systems (the MS-DOS and
6 VFAT (Windows 95) file systems), then you must say Y or M here
8 diskettes with FAT-based file systems and transparently access the
13 the foundation for the other file systems. You will have to say Y or
32 cannot compile any of the FAT-based file systems into the kernel
64 This option provides support for normal Windows file systems with
65 long filenames. That includes non-compressed FAT-based file systems
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/ |
| D | cpus.txt | 13 with updates for 32-bit and 64-bit ARM systems provided in this document.
52 # On 32-bit ARM 11 MPcore, ARM v7 or later systems
55 # On ARM v8 64-bit systems value should be set to 2,
83 # On ARM 11 MPcore based systems this property is
91 # On 32-bit ARM v7 or later systems this property is
100 # On ARM v8 64-bit systems this property is required
198 # On ARM 32-bit systems this property is optional and
229 Usage: required for systems that have an "enable-method"
233 # On ARM v8 64-bit systems must be a two cell
238 Usage: required for systems that have an "enable-method"
[all …]
|
12345678910>>...53