/openbmc/qemu/tests/qemu-iotests/ |
H A D | 124 | 95 self.drives = list() 122 self.drives.append({ 127 return self.drives[-1] 182 drive = self.drives[-1] 260 self.add_bitmap('bitmap0', self.drives[0], **kwargs) 266 self.hmp_io_writes(self.drives[0]['id'], (('0xab', 0, 512), 271 self.hmp_io_writes(self.drives[0]['id'], (('0x9a', 0, 512), 327 drive0 = self.drives[0] 383 drive0 = self.drives[0] 443 drive0 = self.drives[0] [all …]
|
/openbmc/docs/designs/ |
H A D | nvmemi-over-smbus.md | 13 monitor NVMe drives so appropriate action can be taken. 18 `NVM Express Basic Management Command` that can read the NVMe drives information 22 For our purpose is retrieve NVMe drives information, therefore, using NVM 24 communicate with NVMe drives. According to different platforms, temperature 36 - Provide a daemon to monitor NVMe drives. Parameters to be monitored are Status 40 - Capability of communication over hardware channel I2C to NVMe drives. 119 | StatusFlags | string | Indicates the status of the drives | 122 | BackupdrivesFault | bool | If warning type about backup drives happened | 161 drive to get data. Data get from NVMe drives are "Status Flags", "SMART 166 This service will run automatically and look up NVMe drives every second. [all …]
|
/openbmc/linux/Documentation/hwmon/ |
H A D | drivetemp.rst | 24 drives with temperature sensors. 36 Reading the drive temperature may reset the spin down timer on some drives. 37 This has been observed with WD120EFAX drives, but may be seen with other 38 drives as well. The same behavior is observed if the 'hdtemp' or 'smartd' 44 drives experience similar behavior. 46 A known workaround for WD120EFAX drives is to read the drive temperature at 47 intervals larger than twice the spin-down time. Otherwise affected drives
|
/openbmc/linux/Documentation/admin-guide/blockdev/ |
H A D | paride.rst | 13 CD-ROM, LS-120 and tape drives use the parallel port to connect to their 19 (The Iomega PPA-3 adapter used in the ZIP drives is an example of this 26 drives use the ISA replicator to interface a floppy disk controller, 38 drives or scanners. Many different devices are supported by the 43 - MicroSolutions backpack hard-drives 45 - SyQuest EZ-135, EZ-230 & SparQ drives 50 - Hewlett-Packard 5GB and 8GB tape drives 51 - Hewlett-Packard 7100 and 7200 CD-RW drives 191 3.3 Some drives need a printer reset 194 There appear to be a number of "noname" external drives on the market [all …]
|
/openbmc/linux/drivers/ata/pata_parport/ |
H A D | Kconfig | 19 parallel port Series 5 IDE protocol. (Most BACKPACK drives made 20 before 1999 were Series 5) Series 5 drives will NOT always have the 31 parallel port Series 6 IDE protocol. (Most BACKPACK drives made 32 after 1999 were Series 6) Series 6 drives will have the Series noted 59 (low speed) adapter that is used in some portable hard drives. 125 used in some 2.5" portable hard drives.
|
/openbmc/linux/fs/adfs/ |
H A D | Kconfig | 10 here, Linux will be able to read from ADFS partitions on hard drives 15 /dev/[hs]d?1) on each of your drives. Please read the file 28 hard drives and ADFS-formatted floppy disks. This is experimental
|
/openbmc/linux/Documentation/devicetree/bindings/spi/ |
H A D | sqi-pic32.txt | 7 - clocks: Should contain phandle of two clocks in sequence, one that drives 8 clock on SPI bus and other that drives SQI controller.
|
/openbmc/linux/Documentation/scsi/ |
H A D | hpsa.rst | 11 driver (for logical drives) AND a SCSI driver (for tape drives). This 57 (e.g. hot-plugged tape drives, or newly configured or deleted logical drives, 62 tape drives, or entire storage boxes containing pre-configured logical drives.
|
H A D | st.rst | 33 QIC-drives). The result is that any tape can be read, writing can be 123 The tape driver currently supports up to 2^17 drives if 4 modes for 167 The st driver maintains statistics for tape drives inside the sysfs filesystem. 290 this read command. Should be disabled for those drives that don't like 435 for SCSI-1 drives and SCSI-2 seek for SCSI-2 drives. The file and 453 SCSI mode page 15. Note that some drives other methods for 454 control of compression. Some drives (like the Exabytes) use 455 density codes for compression control. Some drives use another 457 driver. Some drives without compression capability will accept 471 drives and several early drives this is the physically first [all …]
|
/openbmc/u-boot/cmd/ |
H A D | fdc.c | 531 int i,drives,state; in fdc_check_drive() local 535 for(drives=0;drives<4;drives++) { in fdc_check_drive() 536 pCMD->drive=drives; in fdc_check_drive() 544 state|=(1<<drives); in fdc_check_drive() 554 state|=(0x10<<drives); in fdc_check_drive()
|
/openbmc/u-boot/drivers/scsi/ |
H A D | Kconfig | 7 hard drives and optical drives. The SCSI standards define physical
|
/openbmc/linux/drivers/md/ |
H A D | Kconfig | 101 A RAID-1 set consists of several disk drives which are exact copies 105 kernel. In a set with N drives, the available space is the capacity 107 drives. 148 A RAID-5 set of N drives with a capacity of C MB per drive provides 150 of a single drive. For a given sector (row) number, (N - 1) drives 153 while a RAID-5 set distributes the parity across the drives in one 156 A RAID-6 set of N drives with a capacity of C MB per drive 158 against a failure of any two drives. For a given sector 159 (row) number, (N - 2) drives contain data sectors, and two 160 drives contains two independent redundancy syndromes. Like [all …]
|
/openbmc/linux/Documentation/admin-guide/device-mapper/ |
H A D | dm-raid.rst | 124 2 drives 3 drives 4 drives 142 2 drives 3 drives 4 drives 158 2 drives 3 drives 4 drives 225 given for both the metadata and data drives for a given position. 233 # RAID4 - 4 data drives, 1 parity (no metadata devices) 242 # RAID4 - 4 data drives, 1 parity (with metadata devices)
|
/openbmc/openbmc/meta-security/recipes-security/ecryptfs-utils/files/ |
H A D | ecryptfs-utils-CVE-2016-6224.patch | 8 NVMe/MMC drives and resulted in the swap partition being used without 34 + NVMe/MMC drives and resulted in the swap partition being used without 52 + # Correctly handle NVMe/MMC drives, as well as any similar physical
|
/openbmc/qemu/tests/qtest/ |
H A D | hd-geo-test.c | 590 char **drives; member 603 args->drives = g_new0(char *, MAX_DRIVES); in create_args() 618 args->drives[args->n_drives] = img_file_name; in add_drive_with_mbr() 715 unlink(args->drives[i]); in test_override() 716 g_free(args->drives[i]); in test_override() 718 g_free(args->drives); in test_override() 932 unlink(args->drives[i]); in test_override_hot_unplug() 933 g_free(args->drives[i]); in test_override_hot_unplug() 935 g_free(args->drives); in test_override_hot_unplug()
|
/openbmc/libbej/test/ |
H A D | bej_encoder_test.cpp | 101 "@odata.id": "/redfish/v1/drives/1", 106 "target": "/redfish/v1/drives/1/Actions/Drive.Reset", 295 const char* drives[1] = {"/redfish/v1/Chassis/SomeChassis/Drives/SATA_0"}; in createChassisResource() local 333 redfishCreateArrayOfLinksJson(&links, "Drives", /*linkCount=*/1, drives, in createChassisResource()
|
/openbmc/qemu/hw/block/ |
H A D | swim.c | 184 drive = &bus->ctrl->drives[dev->unit]; in swim_drive_realize() 197 drive = &bus->ctrl->drives[dev->unit]; in swim_drive_realize() 485 fd_recalibrate(&ctrl->drives[i]); in sysbus_swim_reset() 539 VMSTATE_STRUCT_ARRAY(drives, SWIMCtrl, SWIM_MAX_FD, 1,
|
/openbmc/linux/Documentation/cdrom/ |
H A D | cdrom-standard.rst | 50 adapted their drives to one or more of the already existing electrical 57 drives are either IDE/ATAPI or SCSI, and it is very unlikely that any 58 manufacturer will create a new interface. Even finding drives for the 71 ejection. Undoubtedly, the capabilities of the different drives vary, 72 but even when two drives have the same capability their drivers' 93 Driver is simply to give people writing application programs for CD-ROM drives 103 the IDE/ATAPI drives and, of course, the SCSI drives, but as prices 106 that these drives behave in the same way. In December 1994, one of the 107 cheapest CD-ROM drives was a Philips cm206, a double-speed proprietary 109 proprietary drives became obsolete and IDE/ATAPI drives became the [all …]
|
/openbmc/qemu/block/ |
H A D | file-win32.c | 776 char drives[256], *pdrv = drives; in find_cdrom() local 779 memset(drives, 0, sizeof(drives)); in find_cdrom() 780 GetLogicalDriveStrings(sizeof(drives), drives); in find_cdrom()
|
/openbmc/linux/Documentation/devicetree/bindings/watchdog/ |
H A D | moxa,moxart-watchdog.txt | 7 - clocks : Should contain phandle for the clock that drives the counter
|
/openbmc/linux/fs/zonefs/ |
H A D | Kconfig | 9 device (e.g. host-managed or host-aware SMR disk drives) as files.
|
/openbmc/openbmc/meta-openembedded/meta-xfce/recipes-xfce/thunar-volman/ |
H A D | thunar-volman_4.20.0.bb | 1 SUMMARY = "Automatic management of removable drives and media for thunar"
|
/openbmc/qemu/docs/ |
H A D | throttle.txt | 166 performed on individual drives, but QEMU allows grouping drives so 191 I/O requests on several drives of the same group they will be 331 that we have three different drives and we want to set I/O limits for 333 of all three drives. 336 drives and one that would apply to all of them: 343 Now we can define the drives, and for each one of them we use two 357 In this example the individual drives have IOPS limits of 2000, 2500
|
/openbmc/linux/Documentation/devicetree/bindings/timer/ |
H A D | altr,timer-1.0.txt | 8 - clock-frequency : The frequency of the clock that drives the counter, in Hz.
|
/openbmc/estoraged/include/ |
H A D | meson.build | 5 # If the number of drives increases we plan to switch to a config file design
|