| /openbmc/linux/Documentation/scsi/ |
| H A D | scsi-parameters.rst | 4 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]
37 BusLogic= [HW,SCSI]
41 gvp11= [HW,SCSI]
43 ips= [HW,SCSI] Adaptec / IBM ServeRAID controller
[all …]
|
| H A D | scsi.rst | 4 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 D | sym53c8xx_2.rst | 20 2. Supported chips and SCSI features
22 3.1 Optimized SCSI SCRIPTS
46 10.2.6 Check SCSI BUS
47 10.2.7 Suggest a default SCSI id for hosts
54 10.4 SCSI BUS checking boot option
55 11. SCSI problem troubleshooting
67 This driver supports the whole SYM53C8XX family of PCI-SCSI controllers.
68 It also support the subset of LSI53C10XX PCI-SCSI controllers that are based
115 SCSI standard documentations are available at T10 site:
119 Useful SCSI tools written by Eric Youngdale are part of most Linux
[all …]
|
| H A D | ncr53c8xx.rst | 18 2. Supported chips and SCSI features
20 3.1 Optimized SCSI SCRIPTS
21 3.2 New features of the SYM53C896 (64 bit PCI dual LVD SCSI controller)
45 10.2.5 Ultra SCSI support
59 10.2.19 Check SCSI BUS
61 10.2.21 Suggest a default SCSI id for hosts
66 10.6 SCSI BUS checking boot option
74 14.3 Using only 8 bit devices with a WIDE SCSI controller.
77 15. SCSI problem troubleshooting
81 16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers
[all …]
|
| H A D | BusLogic.rst | 4 BusLogic MultiMaster and FlashPoint SCSI Driver for Linux
27 BusLogic, Inc. designed and manufactured a variety of high performance SCSI
48 to achieve the full performance that BusLogic SCSI Host Adapters and modern
49 SCSI peripherals are capable of, and to provide a highly robust driver that can
55 The latest information on Linux support for BusLogic SCSI Host Adapters, as
62 driver and SCSI subsystem at startup, along with any subsequent system messages
63 relevant to SCSI operations, and a detailed description of your system's
69 the BT-948 PCI Ultra SCSI Host Adapter, and then again for the BT-958 PCI Wide
70 Ultra SCSI Host Adapter in January 1996. This was mutually beneficial since
86 "Mylex SCSI host adapters are compatible with all major operating systems
[all …]
|
| H A D | scsi_mid_low_api.rst | 4 SCSI mid_level - lower_level driver interface
9 This document outlines the interface between the Linux SCSI mid level and
10 SCSI lower level drivers. Lower level drivers (LLDs) are variously called
13 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
15 to "target" SCSI ports (e.g. disks). There can be many LLDs in a running
17 SCSI HBAs. Some HBAs contain multiple hosts.
19 In some cases the SCSI transport is an external bus that already has
21 SCSI subsystem LLD is a software bridge to the other driver subsystem.
26 For example, the aic7xxx LLD controls Adaptec SCSI parallel interface
[all …]
|
| H A D | index.rst | 4 SCSI Subsystem
18 SCSI driver APIs
27 SCSI driver parameters
36 SCSI host adapter drivers
|
| H A D | ufs.rst | 19 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
132 from the SCSI Midlayer, forms UPIUs and issues the UPIUs to the UFS Host
134 host controller in the form of UPIUs and intimates the SCSI Midlayer
[all …]
|
| H A D | NinjaSCSI.rst | 21 :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...)
|
| H A D | scsi_eh.rst | 4 SCSI EH
7 This document describes SCSI midlayer error handling infrastructure.
9 information regarding SCSI midlayer.
13 [1] How SCSI commands travel through the midlayer and to EH
19 [2] How SCSI EH works
25 [2-2-1] Pre transportt->eh_strategy_handler() SCSI midlayer conditions
26 [2-2-2] Post transportt->eh_strategy_handler() SCSI midlayer conditions
30 1. How SCSI commands travel through the midlayer and to EH
36 Each SCSI command is represented with struct scsi_cmnd (== scmd). A
138 4. Wakes up SCSI EH thread if shost->host_busy == shost->host_failed
[all …]
|
| /openbmc/linux/drivers/zorro/ |
| H A D | zorro.ids | 16 0a00 [SCSI Host Adapter]
22 1300 Warp Engine [Accelerator, SCSI Host Adapter and RAM Expansion]
28 5400 A4091 [SCSI Host Adapter]
31 0100 A2090/A2090A [SCSI Host Adapter]
32 0200 A590/A2091 [SCSI Host Adapter]
33 0300 A590/A2091 [SCSI Host Adapter]
34 0400 A2090B 2090 Autoboot [SCSI Host Adapter]
42 5400 A4091 [SCSI Host Adapter]
49 0300 A2090/A2090A Combitec/MacroSystem [SCSI Host Adapter]
57 0400 Kronos 2000 [SCSI Host Adapter]
[all …]
|
| /openbmc/linux/arch/mips/pci/ |
| H A D | fixup-sni.c | 22 #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 D | Kconfig | 3 # SCSI driver configuration for Acorn
6 tristate "Acorn SCSI card (aka30) support"
7 depends on ARCH_ACORN && SCSI
10 This enables support for the Acorn SCSI card (aka30). If you have an
14 bool "Support SCSI 2 Synchronous Transfers"
18 targets on the Acorn SCSI card.
20 In general, this improves performance; however some SCSI devices
24 tristate "ARXE SCSI support"
25 depends on ARCH_ACORN && SCSI
30 was either sold on its own or with an integral SCSI controller.
[all …]
|
| /openbmc/linux/drivers/scsi/ |
| H A D | Kconfig | 2 menu "SCSI device support"
6 default y if SCSI=n || SCSI=y
7 default m if SCSI=m
21 config SCSI config
22 tristate "SCSI device support"
29 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
30 any other SCSI device under Linux, say Y and make sure that you know
31 the name of your SCSI host adapter (the card inside your computer
32 that "speaks" the SCSI protocol, also called SCSI controller),
36 the SCSI protocol. Examples of this include the parallel port
[all …]
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | scsi.rst | 2 SCSI Interfaces Guide
19 Although the old parallel (fast/wide/ultra) SCSI bus has largely fallen
20 out of use, the SCSI command set is more widely used than ever to
23 The `SCSI protocol <http://www.t10.org/scsi-3.htm>`__ is a big-endian
24 peer-to-peer packet based protocol. SCSI commands are 6, 10, 12, or 16
27 SCSI commands can be transported over just about any kind of bus, and
29 Fibre Channel, FireWire, and ATAPI devices. SCSI packets are also
35 Design of the Linux SCSI subsystem
38 The SCSI subsystem uses a three layer design, with upper, mid, and low
39 layers. Every operation involving the SCSI subsystem (such as reading a
[all …]
|
| /openbmc/linux/drivers/scsi/megaraid/ |
| H A D | Kconfig.megaraid | 4 depends on PCI && HAS_IOPORT && SCSI
10 depends on PCI && HAS_IOPORT && SCSI && MEGARAID_NEWGEN
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
[all …]
|
| /openbmc/linux/drivers/scsi/device_handler/ |
| H A D | Kconfig | 3 # 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 D | Kconfig | 1 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 D | Kconfig | 1 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 D | pnfs-scsi-server.rst | 3 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 D | Kconfig | 3 # 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/eisa/ |
| H A D | eisa.ids | 10 ABP0510 "Advansys ABP-510 ISA SCSI Host Adapter"
11 ABP0540 "Advansys ABP-540/542 ISA SCSI Host Adapter"
12 ABP7401 "AdvanSys ABP-740/742 EISA Single Channel SCSI Host Adapter"
13 ABP7501 "AdvanSys ABP-750/752 EISA Dual Channel SCSI Host Adapter"
51 ADP0000 "Adaptec AHA-1740 SCSI"
52 ADP0001 "Adaptec AHA-1740A SCSI"
53 ADP0002 "Adaptec AHA-1742A SCSI"
54 ADP0100 "Adaptec AHA-1540/1542 ISA SCSI Host Adapter"
56 ADP0200 "Adaptec AHA-1520/1522 ISA SCSI Host Adapter"
57 ADP0400 "Adaptec AHA-1744 SCSI"
[all …]
|
| /openbmc/qemu/docs/interop/ |
| H A D | pr-helper.rst | 7 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 D | zfcpdump.rst | 2 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
|
| /openbmc/linux/drivers/target/loopback/ |
| H A D | Kconfig | 3 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
|