Searched full:systems (Results 1 – 25 of 4633) sorted by relevance
12345678910>>...186
| /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-5.10/Documentation/driver-api/ |
| D | dcdbas.rst | 2 Dell Systems Management Base Driver
8 The Dell Systems Management Base Driver provides a sysfs interface for
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
40 Systems management software must perform the following steps to execute
56 shutting down. On some Dell systems, this host control feature requires that
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | dcdbas.txt | 2 Dell Systems Management Base Driver
8 The Dell Systems Management Base Driver provides a sysfs interface for
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
40 Systems management software must perform the following steps to execute
56 shutting down. On some Dell systems, this host control feature requires that
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/ |
| D | vendor-prefixes.txt | 6 abilis Abilis Systems
21 alphascale AlphaScale Integrated Circuits Systems, Inc.
35 arasan Arasan Chip Systems
40 armadeus ARMadeus Systems SARL
69 cdns Cadence Design Systems Inc.
80 cnxt Conexant Systems, Inc.
82 cortina Cortina Systems, Inc.
135 focaltech FocalTech Systems Co.,Ltd
142 gef GE Fanuc Intelligent Platforms Embedded Systems, Inc.
143 GEFanuc GE Fanuc Intelligent Platforms Embedded Systems, Inc.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/i2c/busses/ |
| D | i2c-sis630 | 4 * Silicon Integrated Systems Corp (SiS)
22 faster, but freeze some systems (i.e. my Laptop).
34 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 630 Host (rev 31)
35 00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513
39 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 730 Host (rev 02)
40 00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513
44 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 760/M760 Host (rev 02)
45 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO]
|
| D | i2c-sis96x | 6 * Silicon Integrated Systems Corp (SiS)
26 00:00.0 Host bridge: Silicon Integrated Systems [SiS]: Unknown device 0645
27 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513
28 00:02.1 SMBus: Silicon Integrated Systems [SiS]: Unknown device 0016
32 00:00.0 Host bridge: Silicon Integrated Systems [SiS]: Unknown device 0645
33 00:02.0 ISA bridge: Silicon Integrated Systems [SiS]: Unknown device 0961
34 00:02.1 SMBus: Silicon Integrated Systems [SiS]: Unknown device 0016
|
| /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/i2c/busses/ |
| D | i2c-sis630.rst | 6 * Silicon Integrated Systems Corp (SiS)
27 faster, but freeze some systems (i.e. my Laptop).
40 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 630 Host (rev 31)
41 00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513
45 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 730 Host (rev 02)
46 00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513
50 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 760/M760 Host (rev 02)
51 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO]
|
| D | i2c-sis96x.rst | 9 * Silicon Integrated Systems Corp (SiS)
31 00:00.0 Host bridge: Silicon Integrated Systems [SiS]: Unknown device 0645
32 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513
33 00:02.1 SMBus: Silicon Integrated Systems [SiS]: Unknown device 0016
37 00:00.0 Host bridge: Silicon Integrated Systems [SiS]: Unknown device 0645
38 00:02.0 ISA bridge: Silicon Integrated Systems [SiS]: Unknown device 0961
39 00:02.1 SMBus: Silicon Integrated Systems [SiS]: Unknown device 0016
|
| /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/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/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-5.10/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
|
| /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
101 Enable any character sets you need in File Systems/Native Language
|
| /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
100 Enable any character sets you need in File Systems/Native Language
|
| /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/kernel/rcu/ |
| D | Kconfig | 14 smaller systems.
21 designed for very large SMP systems with hundreds or
24 smaller systems.
33 designed for UP systems from which real-time response
133 systems, but if you are stress-testing the RCU implementation
135 code paths on small(er) systems.
149 against lock contention. Systems that synchronize their
152 lock contention levels acceptably low. Very large systems
156 initialization. These systems tend to run CPU-bound, and thus
166 Select the maximum permissible value for large systems, but
|
| /kernel/linux/linux-4.19/net/mac80211/ |
| D | Kconfig | 143 on production systems as some of the messages are
154 should not be selected on production systems as some
175 It should not be selected on production systems as some
186 be selected on production systems as those messages
197 be selected on production systems as those messages
209 It should not be selected on production systems as those
222 It should not be selected on production systems as those
235 It should not be selected on production systems as those
248 It should not be selected on production systems as those
293 It should not be selected on production systems as those
|
| /kernel/linux/linux-4.19/arch/arm/mach-ep93xx/ |
| D | Kconfig | 134 bool "Support Bluewater Systems Snapper CL15 Module"
137 Systems Snapper CL15 Module.
140 bool "Support Technologic Systems TS-72xx SBC"
143 Technologic Systems TS-72xx board.
146 bool "Support Vision Engraving Systems EP9307 SoM"
149 Vision Engraving Systems EP9307 SoM.
|
| /kernel/linux/linux-5.10/arch/arm/mach-ep93xx/ |
| D | Kconfig | 135 bool "Support Bluewater Systems Snapper CL15 Module"
138 Systems Snapper CL15 Module.
141 bool "Support Technologic Systems TS-72xx SBC"
144 Technologic Systems TS-72xx board.
147 bool "Support Vision Engraving Systems EP9307 SoM"
150 Vision Engraving Systems EP9307 SoM.
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/mtd/ |
| D | diskonchip.txt | 1 M-Systems and Sandisk DiskOnChip devices
5 The Sandisk (formerly M-Systems) docg3 is a nand device of 64M to 256MB.
8 - compatible: should be "m-systems,diskonchip-g3"
13 compatible = "m-systems,diskonchip-g3";
|
12345678910>>...186