Host Controller transport layer and AMPs
2017-07-23 08:50
239 查看
The logical Host Controller Interface does not consider multiplexing/routing over the Host Controller Transport Layer(s). The Host designer must consider this in deciding which of the multiple controller configurations it will
support. Each logical AMP HCI installation is particular to a single AMP Controller. The Host shall direct each HCI Command to a specific AMP, and be aware of the source of each HCI Event, and manage flow control separately for each HCI. The Host's Controller_ID
concept used for AMP enumeration may assist with this.
The logical HCI definition does not consider the initial discovery of what AMPs are present in the system.
The upper layers discover the AMP capabilities. As seen by the AMP Manager, each local AMP has a Controller_ID that is used to route the data and commands to the correct AMP Controller. This identifier is not used in AMP HCI.
The separate logical HCIswithin a system may be on the same physical HCI transport, on separate physical HCI transports, or any combination. This may require a layer of multiplexing, which isnot defined within this AMP HCI logical
specification.
The logical HCI is not affected by this topology. The logical HCI definition describes commands and events as seen by a single AMP.
support. Each logical AMP HCI installation is particular to a single AMP Controller. The Host shall direct each HCI Command to a specific AMP, and be aware of the source of each HCI Event, and manage flow control separately for each HCI. The Host's Controller_ID
concept used for AMP enumeration may assist with this.
The logical HCI definition does not consider the initial discovery of what AMPs are present in the system.
The upper layers discover the AMP capabilities. As seen by the AMP Manager, each local AMP has a Controller_ID that is used to route the data and commands to the correct AMP Controller. This identifier is not used in AMP HCI.
The separate logical HCIswithin a system may be on the same physical HCI transport, on separate physical HCI transports, or any combination. This may require a layer of multiplexing, which isnot defined within this AMP HCI logical
specification.
The logical HCI is not affected by this topology. The logical HCI definition describes commands and events as seen by a single AMP.
相关文章推荐
- Host Controller transport layer and AMPs
- 2-The Transport Layer: TCP, UDP, and SCTP
- Using a USB host controller security extension for controlling changes in and auditing USB topology
- Transport layer and Network layer
- Transmitting and Receiving RTP over Custom Transport Layer
- cocos2dX LAYER_CREATE_FUNC and SCENE_CREATE_FUNC ,LAYER_NODE_FUNC can be replace by one macro CREATE_FUNC
- VMPlayer Ubuntu 16.04 Copy and Paste with Host 主机与宿机之间的复制粘贴
- ScrollAndPageController
- Codeforces Round #206 (Div. 2) B. Vasya and Public Transport
- 在storyboard中的静态UITableView中拖入 UISearchBar and Search Display Controller出现的奇怪问题
- 详解Asp.Net MVC――控制器与动作(Controller And Action)
- IIS Express start introduction and applicationHost modification
- Setup SSH access between VirtualBox Host and Guest VMs
- Ruby on Rails(ROR) 小结(一) 绑定controller and view
- iOS:搜索栏控件UISearchBar and SearchDisplayController的使用
- Create Your Tab and LayerTabMenu In Katana
- Caffe学习系列(6):Blob,Layer and Net以及对应配置文件的编写
- USB host and OTG
- 关于kernel2.6中USB host controller driver 的问题
- Caffe学习系列(6):Blob,Layer and Net以及对应配置文件的编写