欢迎访问ic37.com |
会员登录 免费注册
发布采购

326769-002 参数 Datasheet PDF下载

326769-002图片预览
型号: 326769-002
PDF下载: 下载PDF文件 查看货源
内容描述: 移动第三代英特尔®科雷亚?? ¢处理器家族 [Mobile 3rd Generation Intel® Core™ Processor Family]
分类和应用:
文件页数/大小: 342 页 / 2513 K
品牌: INTEL [ INTEL ]
 浏览型号326769-002的Datasheet PDF文件第222页浏览型号326769-002的Datasheet PDF文件第223页浏览型号326769-002的Datasheet PDF文件第224页浏览型号326769-002的Datasheet PDF文件第225页浏览型号326769-002的Datasheet PDF文件第227页浏览型号326769-002的Datasheet PDF文件第228页浏览型号326769-002的Datasheet PDF文件第229页浏览型号326769-002的Datasheet PDF文件第230页  
Processor Configuration Registers  
2.12.13 DMIVCPRSTS—DMI VCp Resource Status Register  
This register reports the Virtual Channel specific status.  
B/D/F/Type:  
Address Offset:  
Reset Value:  
Access:  
0/0/0/DMIBAR  
32–33h  
0002h  
RO-V  
Size:  
16 bits  
BIOS Optimal Default  
0000h  
Reset  
Value  
RST/  
PWR  
Bit  
Access  
Description  
15:2  
RO  
0h  
1b  
0h  
Reserved (RSVD)  
Virtual Channel private Negotiation Pending (VCPNP)  
0 = The VC negotiation is complete.  
1 = The VC resource is still in the process of negotiation  
(initialization or disabling).  
Software may use this bit when enabling or disabling the VC. This  
bit indicates the status of the process of Flow Control  
initialization. It is set by default on Reset, as well as whenever  
the corresponding Virtual Channel is Disabled or the Link is in the  
DL_Down state. It is cleared when the link successfully exits the  
FC_INIT2 state.  
Before using a Virtual Channel, software must check whether the  
VC Negotiation Pending fields for that Virtual Channel are cleared  
in both Components on a Link.  
1
0
RO-V  
Uncore  
RO  
Reserved (RSVD)  
2.12.14 DMIVCMRCAP—DMI VCm Resource Capability Register  
B/D/F/Type:  
Address Offset:  
Reset Value:  
Access:  
0/0/0/DMIBAR  
34–37h  
00008000h  
RO  
32 bits  
Size:  
BIOS Optimal Default  
00000000h  
Reset  
Value  
RST/  
PWR  
Bit  
Access  
Description  
31:16  
RO  
0h  
1b  
0h  
Reserved (RSVD)  
Reject Snoop Transactions (REJSNPT)  
0 = Transactions with or without the No Snoop bit set within the  
TLP header are allowed on the VC.  
1 = Any transaction for which the No Snoop attribute is  
applicable but is not set within the TLP Header will be  
rejected as an Unsupported Request  
15  
RO  
RO  
Uncore  
14:0  
Reserved (RSVD)  
226  
Datasheet, Volume 2