Searched full:systems (Results 1 – 25 of 478) sorted by relevance
12345678910>>...20
| /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 …]
|
| /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
|
| D | i2c-piix4.rst | 85 If you own Force CPCI735 motherboard or other OSB4 based systems you may need 106 This driver will refuse to load on IBM systems with an Intel PIIX4 SMBus. 109 Thinkpad laptops, but desktop systems may also be affected. We have no list 110 of all affected systems, so the only safe solution was to prevent access to 111 the SMBus on all IBM systems (detected using DMI data.)
|
| /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";
|
| D | jedec,spi-nor.txt | 76 systems don't toggle the flash RESET# pin upon system reset 77 (if the pin even exists at all), there are systems which 79 state. This boolean flag can be used on such systems, to
|
| /Documentation/media/uapi/dvb/ |
| D | frontend.rst | 17 systems: Terrestrial, cable and Satellite. Currently, the following 18 delivery systems are supported: 20 - Terrestrial systems: DVB-T, DVB-T2, ATSC, ATSC M/H, ISDB-T, DVB-H, 23 - Cable systems: DVB-C Annex A/C, ClearQAM (DVB-C Annex B) 25 - Satellite systems: DVB-S, DVB-S2, DVB Turbo, ISDB-S, DSS 48 On Satellite systems, the API support for the Satellite Equipment
|
| D | dvbproperty.rst | 20 systems). The actual parameters are specific to each particular digital 25 ATSC delivery systems grouped there. The problem is that, as the second 39 with supports all digital TV delivery systems. 50 3. Nowadays, most frontends support multiple delivery systems. 52 the multiple delivery systems supported by a frontend. 130 frontend-property-terrestrial-systems 131 frontend-property-cable-systems 132 frontend-property-satellite-systems
|
| D | fe-type-t.rst | 87 used to contain ``fe_type_t`` field to indicate the delivery systems, 91 devices support multiple delivery systems. Please use 94 On devices that support multiple delivery systems, struct
|
| /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,
|
| /Documentation/networking/ |
| D | fore200e.txt | 2 FORE Systems PCA-200E/SBA-200E ATM NIC driver 5 This driver adds support for the FORE Systems 200E-series ATM adapters 30 The FORE Systems 200E-series driver is shipped with firmware data being 37 ForeThought CD-ROM supplied with your adapter by FORE Systems. 39 You can also get the latest firmware images from FORE Systems at
|
| /Documentation/i2c/ |
| D | summary.rst | 9 I2C is widely used with embedded systems. Some systems use variants that 20 use its protocols on many I2C systems. However, there are systems that don't
|
| /Documentation/hwmon/ |
| D | emc6w201.rst | 40 Known Systems With EMC6W201 43 The EMC6W201 is a rare device, only found on a few systems, made in 44 2005 and 2006. Known systems with this device:
|
| /Documentation/arm64/ |
| D | perf.txt | 59 performed differently on VHE and non-VHE systems. 61 For non-VHE systems we exclude EL2 for exclude_host - upon entering and 65 For VHE systems we exclude EL1 for exclude_guest and exclude both EL0,EL2 85 On VHE systems there are no blackout windows.
|
| /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 …]
|
| /Documentation/ABI/testing/ |
| 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
|
| /Documentation/RCU/ |
| D | UP.rst | 3 RCU on Uniprocessor Systems 6 A common misconception is that, on UP systems, the call_rcu() primitive 97 UP systems, including PREEMPT SMP builds running on UP systems. 100 Why can't synchronize_rcu() return immediately on UP systems running 136 Why can't synchronize_rcu() return immediately on UP systems
|
| /Documentation/devicetree/bindings/arm/ |
| D | renesas.yaml | 62 # iWave Systems RZ/G1M Qseven Development Platform (iW-RainboW-G20D-Qseven) 69 # iWave Systems RZ/G1M Qseven System On Module (iW-RainboW-G20M-Qseven) 77 # iWave Systems RZ/G1N Qseven Development Platform (iW-RainboW-G20D-Qseven) 84 # iWave Systems RZ/G1N Qseven System On Module (iW-RainboW-G20M-Qseven) 91 - iwave,g22m # iWave Systems RZ/G1E SODIMM System On Module (iW-RainboW-G22M-SM) 95 - description: iWave Systems RZ/G1E SODIMM SOM Development Platform (iW-RainboW-G22D) 104 - iwave,g23s #iWave Systems RZ/G1C Single Board Computer (iW-RainboW-G23S)
|
| /Documentation/media/uapi/v4l/ |
| D | biblio.rst | 61 …formation technology — Generic coding of moving pictures and associated audio information: Systems" 81 :title: ITU-R Recommendation BT.470-6 "Conventional Television Systems" 101 :title: ITU-R Recommendation BT.653-3 "Teletext systems" 221 :title: IEC 61966-2-1 ed1.0 "Multimedia systems and equipment - Colour measurement and manageme… 231 :title: IEC 61966-2-1-am1 ed1.0 "Amendment 1 - Multimedia systems and equipment - Colour measur… 241 :title: IEC 61966-2-4 ed1.0 "Multimedia systems and equipment - Colour measurement and manageme… 251 :title: IEC 61966-2-5 "Multimedia systems and equipment - Colour measurement and management - P… 261 …BT.2020 (08/2012) "Parameter values for ultra-high definition television systems for production an… 293 :author: National Radio Systems Committee (http://www.nrscstandards.org)
|
| /Documentation/watchdog/ |
| D | mlx-wdt.rst | 9 Ethernet and Infiniband switch systems. 27 Type 1 HW watchdog implementation exist in old systems and 28 all new systems have type 2 HW watchdog.
|
| /Documentation/devicetree/bindings/display/ |
| D | sm501fb.txt | 19 - little-endian: available on big endian systems, to 21 - big-endian: available on little endian systems, to
|
| /Documentation/devicetree/bindings/ |
| D | vendor-prefixes.yaml | 27 description: Abilis Systems 31 description: Acme Systems srl 61 description: AlphaScale Integrated Circuits Systems, Inc. 87 description: Anvo-Systems Dresden GmbH 93 description: Arasan Chip Systems 105 description: ARMadeus Systems SARL 171 description: Cadence Design Systems Inc. 197 description: Conexant Systems, Inc. 205 description: Cortina Systems, Inc. 305 description: Espressif Systems Co. Ltd. [all …]
|
| /Documentation/media/v4l-drivers/ |
| D | cafe_ccic.rst | 12 controller. This is the controller found in first-generation OLPC systems, 49 systems, however, it will work well with only two. 52 will consent to work with. Default is one, but, on slower systems,
|
| /Documentation/driver-api/usb/ |
| D | dma.rst | 40 the time, that can really burn up resources on systems which use an 62 systems where the I/O would otherwise thrash an IOMMU mapping. (See 69 On most systems the memory returned will be uncached, because the 72 has such bus-snooping, many other systems use software to flush cache 97 systems, this kicks in an IOMMU and turns the scatterlists into single
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | cortina,gemini-pinctrl.txt | 1 Cortina Systems Gemini pin controller 3 This pin controller is found in the Cortina Systems Gemini SoC family,
|
12345678910>>...20