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

FW82443BX 参数 Datasheet PDF下载

FW82443BX图片预览
型号: FW82443BX
PDF下载: 下载PDF文件 查看货源
内容描述: 控制器杂项 - 数据表参考\n [Controller Miscellaneous - Datasheet Reference ]
分类和应用: 控制器
文件页数/大小: 132 页 / 642 K
品牌: ETC [ ETC ]
 浏览型号FW82443BX的Datasheet PDF文件第28页浏览型号FW82443BX的Datasheet PDF文件第29页浏览型号FW82443BX的Datasheet PDF文件第30页浏览型号FW82443BX的Datasheet PDF文件第31页浏览型号FW82443BX的Datasheet PDF文件第33页浏览型号FW82443BX的Datasheet PDF文件第34页浏览型号FW82443BX的Datasheet PDF文件第35页浏览型号FW82443BX的Datasheet PDF文件第36页  
Register Description  
3.2.3  
PCI Bus Configuration Mechanism Overview  
The PCI Bus defines a slot based "configuration space" that allows each device to contain up to 8  
functions with each function containing up to 256 8-bit configuration registers. The PCI  
specification defines two bus cycles to access the PCI configuration space: Configuration Read  
and Configuration Write. Memory and I/O spaces are supported directly by the CPU.  
Configuration space is supported by a mapping mechanism implemented within the chip-set. The  
PCI specification defines two mechanisms to access configuration space, Mechanism #1 and  
Mechanism #2. The 82443BX supports only Mechanism #1.  
The configuration access mechanism makes use of the CONFADD Register and CONFDATA  
Register. To reference a configuration register a Dword I/O write cycle is used to place a value into  
CONFADD that specifies the PCI bus, the device on that bus, the function within the device, and a  
specific configuration register of the device function being accessed. CONFADD[31] must be 1 to  
enable a configuration cycle. CONFDATA then becomes a window into the four bytes of  
configuration space specified by the contents of CONFADD. Any read or write to CONFDATA will  
result in the Host Bridge translating CONFADD into a PCI configuration cycle.  
3.2.3.1  
Type 0 Access  
If the Bus Number field of CONFADD is 0, a Type 0 Configuration cycle is performed on PCI (i.e.  
bus #0). CONFADD[10:2] is mapped directly to AD[10:2]. The Device Number field of  
CONFADD is decoded onto AD[31:11]. The Host-to-PCI Bridge entity within the 82443BX is  
accessed as Device #0 on the PCI bus segment. The Host- /AGP Bridge entity within the 82443BX  
is accessed as Device #1 on the PCI bus segment. To access Device #2, the 82443BX will assert  
AD13, for Device #3 will assert AD14, and so forth up to Device #20 for which will assert AD31.  
Only one AD line is asserted at a time. All device numbers higher than 20 cause a type 0  
configuration access with no IDSEL asserted, which will result in a Master Abort.  
3.2.3.2  
Type 1 Access  
If the Bus Number field of CONFADD is non-zero, then a Type 1 Configuration cycle is performed  
on PCI bus (i.e. bus #0). CONFADD[23:2] is mapped directly to AD[23:2]. AD[1:0] are driven to  
01 to indicate a Type 1 Configuration cycle. All other lines are driven to 0.  
3.2.4  
AGP Bus Configuration Mechanism Overview  
This mechanism is compatible with PCI mechanism #1 supported for the PCI bus as defined above.  
The configuration mechanism is the same for both accessing AGP or PCI-only devices attached to  
the AGP interface.  
3-6  
82443BX Host Bridge Datasheet  
 复制成功!