Endpoint Descriptor Description Sample Clauses

Endpoint Descriptor Description. Endpoint Descriptors (ED) are linked in lists that are processed by the HC. An ED is linked to a next ED when the NextED field is nonzero. When the Host Controller accesses an ED, it checks the sKip and the Halted bits to determine if any further processing of the ED is allowed. If either bit is set, then the Host Controller advances to the next ED on the list. If neither the sKip nor the Halted bit is set, then the Host Controller compares HeadP to TailP. If they are not the same, then the TD pointed to by HeadP defines a buffer to/from which the Host Controller will transfer a data packet. This linking convention assumes that the Host Controller Driver queues to the ‘tail’ of the TD queue. It does this by linking a new TD to the TD pointed to by TailP and then updating TailP to point to the TD just added. When processing of a TD is complete, the Host Controller ‘retires’ the TD by unlinking it from the ED and linking it to the Done Queue. When a TD is unlinked, NextTD of the TD is copied to HeadP of the ED. The sKip bit is set and cleared by the Host Controller Driver when it wants the Host Controller to skip processing of the endpoint. This may be necessary when the Host Controller Driver must modify the value of HeadP and the overhead of removing the ED from its list is prohibitive. The Halted bit is set by the Host Controller when it encounters an error in processing a TD. When the TD in error is moved to the Done Queue, the Host Controller updates HeadP and sets the Halted bit, causing the Host Controller to skip the ED until Halted is cleared. The Host Controller Driver clears the Halted bit when the error condition has been corrected and transfers to/from the endpoint should resume. The Host Controller Driver should not write to HeadP/toggleCarry/Halted unless Halted is set, sKip is set, or the ED has been removed from the list. When TDs are queued to an ED, the Host Controller processes the TDs asynchronously with respect to processing by the host processor. Therefore, if the Host Controller Driver needs to alter the TD queue other than appending to the queue, it must stop the Host Controller from processing the TD queue for the endpoint so that changes can be made. The nominal mechanisms for stopping TD processing are for the Host Controller Driver to remove the ED from the list or to set the sKip bit in the ED. When the D field of an ED is 10b (IN), the Host Controller may issue an IN token to the specified endpoint after it determines that Head...
Sample 1
AutoNDA by SimpleDocs

Related to Endpoint Descriptor Description

  • Topic Description Licensee Responsibilities Licensee must:  Take appropriate steps to ensure the security, integrity, and confidentiality of Confidential Information and must comply with all relevant applicable laws and regulations, including laws protecting borrower privacy.  Not disclose Confidential Information to third parties, without Xxxxxx Mae’s prior written approval, except on a need‐to‐know basis to Licensee’s partners, Topic Description affiliates, officers, employees, directors, contractors, counsels, agents or representatives, provided they are subject to confidentiality obligations at least as stringent as those set forth in this Section A3.  Not use Confidential Information in any way that could be viewed as a conflict of interest, a breach of confidentiality or privacy, or the gaining of an unfair advantage from the relationship with Xxxxxx Xxx.  Implement commercially reasonable measures meeting or exceeding industry standards to ensure the security, integrity, and confidentiality of Confidential Information, including using industry‐standard encryption for data in transit and virus checking programs designed to prevent the transmission and receipt of viruses and other malicious code, implementing appropriate disaster recovery and back‐up procedures, implementing appropriate procedures to prevent disclosure of data and other materials to a party other than the intended recipient, and employing methods for securely disposing or destroying such information.  These measures must meet, at least, the same level of protection that the Receiving Party seeks for its own information of a similar nature.  Licensee must collaborate with Xxxxxx Mae in assessing the sufficiency of these measures and Licensee’s information security program, upon reasonable request.  Instruct its Related Parties who may receive Confidential Information about the requirements of this Section A3, and the processes and procedures necessary to comply with them.  Comply with all reasonable security policies and procedures required by Xxxxxx Xxx related to the access and use of Xxxxxx Mae’s systems or any Licensed Materials.  Not transmit to Xxxxxx Mae’s systems any materials that contain bugs, viruses, worms or other functions, routines, devices or instructions which may create any unauthorized access or damage to, or interruption in the functioning of, the Licensed Application or Xxxxxx Mae’s systems. Restrictive Legends  Licensee must abide by and reproduce and include any restrictive legend or proprietary rights notice that appears in or on any Confidential Information of Xxxxxx Xxx or any Third‐Party Licensor (or other third‐party owner) that it is authorized to reproduce.  Licensee also agrees that it will not remove, alter, cover or distort any trademark, trade name, copyright or other proprietary rights notices, legends, symbols or labels appearing on or in any Confidential Information of Xxxxxx Mae or any Third‐Party Licensor (or other third‐party owner). Required Actions in Case of Data Breach  Licensee must address any Data Breach with prompt and effective corrective action, including cooperation with Xxxxxx Xxx in the investigation and remediation of such Data Breach, as well as prompt disclosure and notification where legally required; and  Licensee must promptly notify Xxxxxx Mae of any Data Breach in writing ‐‐ at xxxxxxx_xxxxxxxxxxxx@xxxxxxxxx.xxx ‐‐ and must take all steps reasonably requested by Xxxxxx Xxx to mitigate the consequences of such Data Breach.

  • Project Description In two or three brief sentences, provide a concise description of your exhibition. Include the subject matter, type of objects to be included (paintings, sculpture, manuscripts, etc.), those responsible for organizing the exhibition, and catalogue author(s).

  • Task Description This task includes activities associated with permit-required monitoring conducted in accordance with the conditions specified by state or federal regulatory agencies. All monitoring tasks must be located within or adjacent to the Project area and follow the Department’s Regional Coastal Monitoring Program and FWC's marine turtle and shorebird monitoring programs. Guidance for monitoring of nearshore resources is available in the Department's Standard Operation Procedures For Nearshore Hardbottom Monitoring Of Beach Nourishment Projects. The Local Sponsor must submit work products directly to the appropriate state or federal regulatory agencies in accordance with permit conditions to be eligible for reimbursement under this task, unless otherwise directed.

  • Product Description The lead products covered by this Settlement Agreement is limited to following Amazon Identification Number (ASIN) B0BBMRLNV9, with the description, "Lesnow 63-37 Tin Lead Rosin Core Solder Wire for Electrical Soldering 0.8mm Soldering Wire Electronics Solder Content Solder Flux 1.8% (0.8mm, 50g)," which was offered for sale by the Settling Entity on xxxxxx.xxx, hereinafter the “Product” or “Products.”

  • Contract Description The Description and Location of the Contract and related project(s) are as follows.

  • Site Description 2.5.1 If reasonably requested by the A/E as necessary for the Project, the Owner shall furnish a legal description and a certified land survey of the Site, giving, as applicable, grades and lines of streets, alleys, pavements and adjoining property; rights-of-way, restrictions, easements, encroachments, zoning, deed restrictions, boundaries and contours of the Site; locations, dimensions, and complete data pertaining to existing buildings, other improvements, and trees; and full information concerning available service and utility lines, both public and private, above and below grade, including inverts and depths.

  • Work Description T-804 Opening Roads - Removal of closure devices, cleaning ditches, removing berms, and blading the traveled-way T-811 Closing Roads - Entrance treatment for 150' cross-rip; debris block (slash, earth, berm, rocks, etc.) + seed + water bar T-811 Closing Roads - Water bar frequency per BMPs for remainder of road T-811 Closing Roads - Engineering Rep. or Construction Inspector must be notified prior to performing closeout NFSR Road No. Lane Width & Maintenance Level Mile Marker Begin End 76L Single Lane / Level 2 76 0.00 Ending 0.48

  • System Description The DLCS is a network consisting of devices which are remotely controlled over RF transmission equipment by the PowerCAMPTM Software or equivalent. CL&P shall have access to the PowerCAMP™ LMS (as defined below) via the web interface. The PowerCAMPTM LMS shall include the software and hardware necessary to manage the Control Devices installed at the End-use Equipment at Participating Facilities. The PowerCAMPTM LMS includes AER’s PowerCAMPTM Server and PowerCAMPTM Suite, networking equipment, and third party software. PowerCAMPTM LMS Hardware

  • Service Descriptions Available services for Transitional and Enhanced Supervision Services a. One (1) one-to-one meeting with the Contractor per week for case management services.

  • Service Description The Parties will provide Common Channel Signaling (CCS) to one another via Signaling System 7 (SS7) network Interconnection, in accordance with prevailing industry standards. Use of a third party provider of SS7 trunks is permitted.

Time is Money Join Law Insider Premium to draft better contracts faster.