1.3 ABOUT THIS MANUAL Firmware, images, and descriptions may vary slightly between this manual and the unit shipped. APPENDIX FORMATTING 3.2 UNMOUNTING DRIVES 3.3 TROUBLESHOOTING 3.4 ABOUT DATA BACKUP 3.5 ONLINE RESOURCES 3.6 TECHNICAL SUPPORT HOURS AND CONTACT INFORMATION TABLE OF CONTENTSģ 1.1.3 Supported Drives 3.5 SATA hard drives NOTE: Drives of identical model and capacity are required for RAID 0 and RAID PACKAGE CONTENTS INTRODUCTION 1.1 MINIMUM SYSTEM REQUIREMENTS Apple Mac Requirements PowerPC G4 CPU, 128MB RAM esata: Mac OS 9.2 or later FireWire 400: Mac OS 9.2 or later FireWire 800: Mac OS X 10.2 or later USB 2.0: Mac OS X 10.2 or later USB 3.0: Mac OS X 10.6 or later PC Requirements 500MHz Intel Pentium 3 CPU, 128MB RAM esata: Windows XP or later FireWire 400: Windows XP or later FireWire 800: Windows XP or later USB 2.0: Windows XP or later USB 3.0: Windows XP or later Guardian Maximus Power Supply and cable esata cable FireWire 800 (1394b) 9-9 pin cable FireWire 400 (1394a) 6-6 pin cable USB 3.0 (Standard-A to Standard-B) cable Not pictured: If the Guardian MAXimus was purchased as an empty enclosure, a packet of screws is included inside the Guardian MAXimus. INTRODUCTION MINIMUM SYSTEM REQUIREMENTS Apple Mac Requirements PC Requirements Supported Drives 1.2 PACKAGE CONTENTS 1.3 ABOUT THIS MANUAL 1.4 FRONT VIEW LED Indicators 1.5 REAR VIEW Rear Features QUICK START 2.2 ASSEMBLY 2.3 RAID SETTINGS Changing the RAID Mode RAID Modes 2.4 DRIVE FAILURE Drive Replacement and Rebuild 3. It also has Dequeue and Enqueue members, which are used to track where TRBs are being consumed by the hardware and where TRBs are being added by software.1 Guardian MAXimus ASSEMBLY MANUAL & USER GUIDEĢ TABLE OF CONTENTS 1. Endpoint ContextĪn Endpoint Context structure holds context information for a single endpoint. When the USB 3.0 core stack receives a transfer request from a USB client driver, it identifies the Endpoint Context for the transfer, and then breaks the transfer request into one or more Transfer Descriptors (TDs). Each TRB points to a block of contiguous data (up to 64 KB) that will be transferred between hardware and memory as a single unit. A Transfer Ring is an array of Transfer Request Blocks (TRBs). It shows additional data structures that represent a single endpoint.Įach endpoint has one or more Transfer Rings. The following diagram continues to the right of the preceding diagram. Software notifies the host controller that it has device-related or endpoint-related work to perform by writing context information into the doorbell register for the device. Element 0 indicates whether there is a pending command in the Command Ring. Elements 1 through 255 are doorbell registers. The Doorbell Register Array is an array of doorbell registers, one for each device connected to the host controller. That is, the Event Ring is a structure that the host controller uses to inform drivers that an action has completed. The Event Ring is used by the host controller to pass events to software. Some of these commands are directed at the host controller, and some are directed at particular devices connected to the host controller. ![]() The Command Ring is used by software to pass commands to the host controller. Element 0 points to a Slot Context structure, which holds context information for the device. Elements 1 through 31 point to Endpoint Context structures. There is one Endpoint Context structure for each endpoint on the device. Device Context and Slot ContextĪ Device Context structure holds an array of pointers to Endpoint Context structures. Element 0 points to a context structure for the host controller. Elements 1 through 255 point to Device Context structures. There is one Device Context structure for each device connected to the host controller. The Device Context Base Array is an array of pointers to Device Context structures. The following diagram shows some of the data structures that represent one host controller and the connected devices. For more information, see USB Driver Stack Architecture.Įach USB 3.0 host controller can have up to 255 devices, and each device can have up to 31 endpoints. The USB 3.0 host controller driver is part of the USB 3.0 core driver stack. Familiarity with the USB 3.0 specification will further enhance your ability to use the extension commands to debug USB 3.0 drivers. The data structures presented here have names that are consistent with the USB 3.0 specification. Understanding these data structures will help you use the USB 3.0 and RCDRKD debugger extension commands effectively. ![]() This topic describes the data structures used by the USB 3.0 host controller driver.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |