Home
last modified time | relevance | path

Searched refs:SCSI (Results 1 – 25 of 277) sorted by relevance

12345678910>>...12

/openbmc/linux/Documentation/scsi/
H A Dscsi-parameters.rst4 SCSI Kernel Parameters
19 advansys= [HW,SCSI]
22 aha152x= [HW,SCSI]
25 aha1542= [HW,SCSI]
28 aic7xxx= [HW,SCSI]
31 aic79xx= [HW,SCSI]
34 atascsi= [HW,SCSI]
41 gvp11= [HW,SCSI]
71 osst= [HW,SCSI] SCSI Tape Driver
79 [SCSI] SCSI default device flags
[all …]
H A Dscsi.rst4 SCSI subsystem documentation
8 the SCSI subsystem in the Linux kernel (lk) 2.4 series. See:
9 https://www.tldp.org/HOWTO/SCSI-2.4-HOWTO . The LDP has single
12 Notes on using modules in the SCSI subsystem
14 The SCSI support in the Linux kernel can be modularized in a number of
18 The scsi-core (also known as the "mid level") contains the core of SCSI
19 support. Without it you can do nothing with any of the other SCSI drivers.
20 The SCSI core support can be a module (scsi_mod.o), or it can be built into
21 the kernel. If the core is a module, it must be the first SCSI module
25 the SCSI subsystem.
[all …]
H A Dsym53c8xx_2.rst20 2. Supported chips and SCSI features
22 3.1 Optimized SCSI SCRIPTS
135 - SCSI parity checking
204 3.1 Optimized SCSI SCRIPTS
565 10.2.6 Check SCSI BUS
697 Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI
714 Most SCSI problems are due to a non conformant SCSI bus or too buggy
718 - SCSI bus cables
785 on the SCSI BUS that prevents the SCSI protocol from functioning
792 Generally SCSI targets do not reset the SCSI BUS, although any
[all …]
H A Dncr53c8xx.rst160 - SCSI parity checking
990 10.2.19 Check SCSI BUS
1216 Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI
1239 competing for the SCSI BUS. By the way, when the chip is using SCSI id 7,
1478 Most SCSI problems are due to a non conformant SCSI bus or to buggy
1482 - SCSI bus cables
1522 the SCSI Bus.
1581 Generally SCSI targets do not reset the SCSI BUS, although any
1589 encounters such error conditions, especially SCSI GROSS ERROR, then a SCSI
1627 SCSI-2 mode.
[all …]
H A DBusLogic.rst146 BusLogic SCSI Host Adapters directly implement SCSI-2 Tagged Queuing, and so
178 reset will force a full host adapter hard reset and SCSI bus reset. SCSI bus
239 BT-948 PCI Ultra SCSI-3
240 BT-958 PCI Wide Ultra SCSI-3
247 BT-946C PCI Fast SCSI-2
250 BT-445C VLB Fast SCSI-2
251 BT-747C EISA Fast SCSI-2
259 BT-445S VLB Fast SCSI-2
260 BT-747S EISA Fast SCSI-2
492 Adapter Hard Reset which initiates a SCSI Bus Reset and issuing any SCSI
[all …]
H A Dindex.rst4 SCSI Subsystem
18 SCSI driver APIs
27 SCSI driver parameters
36 SCSI host adapter drivers
H A Dscsi_mid_low_api.rst13 single SCSI initiator port on a SCSI transport. An "initiator" port
14 (SCSI terminology, see SAM-3 at http://www.t10.org) sends SCSI commands
37 The SCSI mid level isolates an LLD from other layers such as the SCSI
131 with the SCSI mid level.
196 attached to the HBA's SCSI transport. On newer SCSI transports the HBA
200 SCSI DEVICE hotplug
210 existing SCSI transports (e.g. SPI) may not become aware that a SCSI
849 * the 'cmd' then it is passed to the SCSI mid level. If the SCSI
1138 back to the mid level. The SCSI mid level will ensure that no more SCSI
1246 a) instructing the SCSI protocol (e.g. SCSI Parallel Interface (SPI))
[all …]
H A Dufs.rst19 3.4 SCSI Error handling
55 UFS has a layered communication architecture which is based on SCSI
65 protocol agnostic, however SCSI has been selected as a baseline
68 UFS supports a subset of SCSI commands defined by SPC-4 and SBC-3.
71 It handles SCSI commands supported by UFS specification.
115 The UFS host controller driver is based on the Linux SCSI Framework.
117 the SCSI Midlayer and PCIe-based UFS host controllers.
131 Transfer request handling module of UFSHCD receives SCSI commands
134 host controller in the form of UPIUs and intimates the SCSI Midlayer
143 3.4 SCSI Error handling
[all …]
H A DNinjaSCSI.rst21 :SCSI device: I-O data CDPS-PX24 (CD-ROM drive),
51 Because the NinjaSCSI driver requires some SCSI header files in Linux
107 version "KME ", "SCSI-CARD-001", "1"
110 version "KME ", "SCSI-CARD-002", "1"
113 version "KME ", "SCSI-CARD-003", "1"
116 version "KME ", "SCSI-CARD-004", "1"
136 If you eject card when doing some operation for your SCSI device or suspend
146 high level SCSI driver.
156 - your SCSI device name(hard drive, CD-ROM, etc...)
/openbmc/linux/arch/mips/pci/
H A Dfixup-sni.c22 #define SCSI PCIMT_IRQ_SCSI macro
46 { SCSI, SCSI, SCSI, SCSI, SCSI }, /* SCSI */
63 { SCSI, SCSI, SCSI, SCSI, SCSI }, /* SCSI */
75 { SCSI, SCSI, SCSI, SCSI, SCSI }, /* SCSI */
80 #undef SCSI
/openbmc/linux/drivers/scsi/arm/
H A DKconfig3 # SCSI driver configuration for Acorn
7 depends on ARCH_ACORN && SCSI
18 targets on the Acorn SCSI card.
24 tristate "ARXE SCSI support"
25 depends on ARCH_ACORN && SCSI
37 depends on ARCH_ACORN && SCSI
44 depends on ARCH_ACORN && SCSI
51 depends on ARCH_ACORN && SCSI
61 depends on ARCH_ACORN && SCSI
68 tristate "Oak SCSI support"
[all …]
/openbmc/linux/drivers/zorro/
H A Dzorro.ids16 0a00 [SCSI Host Adapter]
28 5400 A4091 [SCSI Host Adapter]
42 5400 A4091 [SCSI Host Adapter]
58 0c00 A1000 [SCSI Host Adapter]
59 0e00 Escort [SCSI Host Adapter]
104 0800 500 [SCSI Host Adapter]
140 0b40 A1291 [SCSI Host Adapter]
184 0300 ALF 3 [SCSI Host Adapter]
221 0200 Golem SCSI-II [SCSI Host Adapter]
251 2200 [SCSI Host Adapter]
[all …]
/openbmc/linux/drivers/scsi/
H A DKconfig2 menu "SCSI device support"
6 default y if SCSI=n || SCSI=y
7 default m if SCSI=m
21 config SCSI config
29 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
32 that "speaks" the SCSI protocol, also called SCSI controller),
71 depends on SCSI
75 depends on SCSI
97 depends on SCSI
125 depends on SCSI
[all …]
/openbmc/linux/Documentation/driver-api/
H A Dscsi.rst2 SCSI Interfaces Guide
54 SCSI upper layer
60 sd (SCSI Disk)
65 sr (SCSI CD-ROM)
70 st (SCSI Tape)
75 sg (SCSI Generic)
85 SCSI mid layer
108 `SCSI Common Access
143 SCSI queuing library.
305 SCSI lower layer
[all …]
/openbmc/linux/drivers/scsi/megaraid/
H A DKconfig.megaraid4 depends on PCI && HAS_IOPORT && SCSI
20 depends on PCI && SCSI && MEGARAID_MM
41 LSI MegaRAID SCSI 320-0 1000:1960:1000:A520
42 LSI MegaRAID SCSI 320-1 1000:1960:1000:0520
43 LSI MegaRAID SCSI 320-2 1000:1960:1000:0518
44 LSI MegaRAID SCSI 320-0X 1000:0407:1000:0530
45 LSI MegaRAID SCSI 320-2X 1000:0407:1000:0532
46 LSI MegaRAID SCSI 320-4X 1000:0407:1000:0531
47 LSI MegaRAID SCSI 320-1E 1000:0408:1000:0001
70 depends on PCI && HAS_IOPORT && SCSI
[all …]
/openbmc/linux/drivers/scsi/device_handler/
H A DKconfig3 # SCSI Device Handler configuration
7 bool "SCSI Device Handlers"
8 depends on SCSI
11 SCSI Device Handlers provide device specific support for
17 depends on SCSI_DH && SCSI
23 depends on SCSI_DH && SCSI
31 depends on SCSI_DH && SCSI
37 depends on SCSI_DH && SCSI
39 SCSI Device handler for generic SPC-3 Asymmetric Logical Unit
/openbmc/qemu/hw/scsi/
H A DKconfig1 config SCSI config
8 select SCSI
14 select SCSI
20 select SCSI
26 select SCSI
30 select SCSI
43 select SCSI
49 select SCSI
/openbmc/u-boot/drivers/scsi/
H A DKconfig1 config SCSI config
2 bool "Support SCSI controllers"
5 This enables support for SCSI (Small Computer System Interface),
7 hard drives and optical drives. The SCSI standards define physical
12 bool "Support SCSI controllers with driver model"
15 This option enables the SCSI (Small Computer System Interface) uclass
16 which supports SCSI and SATA HDDs. For every device configuration
/openbmc/linux/Documentation/admin-guide/nfs/
H A Dpnfs-scsi-server.rst3 pNFS SCSI layout server user guide
6 This document describes support for pNFS SCSI layouts in the Linux NFS server.
7 With pNFS SCSI layouts, the NFS server acts as Metadata Server (MDS) for pNFS,
10 underlying SCSI LUNs that are shared with the client.
12 To use pNFS SCSI layouts with the Linux NFS server, the exported file
13 system needs to support the pNFS SCSI layouts (currently just XFS), and the
14 file system must sit on a SCSI LUN that is accessible to the clients in
19 On a server built with CONFIG_NFSD_SCSI, the pNFS SCSI volume support is
21 option and the underlying SCSI device support persistent reservations.
/openbmc/linux/drivers/scsi/pcmcia/
H A DKconfig3 # PCMCIA SCSI adapter configuration
7 bool "PCMCIA SCSI adapter support"
8 depends on SCSI!=n && PCMCIA!=n
11 if SCSI_LOWLEVEL_PCMCIA && SCSI && PCMCIA && m
18 Say Y here if you intend to attach this type of PCMCIA SCSI host
29 Say Y here if you intend to attach this type of PCMCIA SCSI host
39 If you intend to attach this type of PCMCIA SCSI host adapter to
61 (version string: "KME ","SCSI-CARD-001","1")]
73 Say Y here if you intend to attach this type of PCMCIA SCSI host
84 SCSI adapter based on the Symbios 53c500 controller.
/openbmc/linux/drivers/target/loopback/
H A DKconfig3 tristate "TCM Virtual SAS target and Linux/SCSI LDD fabric loopback module"
4 depends on SCSI
6 Say Y here to enable the TCM Virtual SAS target and Linux/SCSI LLD
/openbmc/linux/drivers/eisa/
H A Deisa.ids51 ADP0000 "Adaptec AHA-1740 SCSI"
52 ADP0001 "Adaptec AHA-1740A SCSI"
53 ADP0002 "Adaptec AHA-1742A SCSI"
57 ADP0400 "Adaptec AHA-1744 SCSI"
61 ADP7771 "Adaptec AHA-274x SCSI"
75 AIR2001 "AIR SCSI-2E"
76 AIR2101 "AIR SCSI-2V"
94 AMI15C1 "AMI SCSI Host Adapter"
399 CPQFD17 "Compaq SCSI Tape Adapter"
665 ICU0560 "DTC3150 SCSI Controller"
[all …]
/openbmc/linux/drivers/infiniband/ulp/srp/
H A DKconfig3 tristate "InfiniBand SCSI RDMA Protocol"
4 depends on SCSI && INFINIBAND_ADDR_TRANS
7 Support for the SCSI RDMA Protocol over InfiniBand. This
/openbmc/qemu/docs/interop/
H A Dpr-helper.rst7 QEMU's SCSI passthrough devices, ``scsi-block`` and ``scsi-generic``,
13 For a more detailed reference please refer to the SCSI Primary
51 of a 16-byte SCSI CDB. A file descriptor must be passed to the helper
52 together with the SCSI CDB using ancillary data.
68 - 4 bytes for the SCSI status
71 and only if the SCSI status is 0x00, i.e. GOOD)
73 - 96 bytes for the SCSI sense data
78 it is only valid if the SCSI status is CHECK CONDITION (0x02).
/openbmc/linux/Documentation/arch/s390/
H A Dzfcpdump.rst2 The s390 SCSI dump tool (zfcpdump)
6 dumps on SCSI disks. The dump process is initiated by booting a dump tool, which
15 below 32 MB. zfcpdump is installed on a SCSI disk using zipl (as contained in
17 system can then trigger a SCSI dump by booting the SCSI disk, where zfcpdump
42 reads from /proc/vmcore or zcore/mem and writes the system dump to a SCSI disk.
45 initramfs with a user space application that writes the dump to a SCSI

12345678910>>...12