FW82801DB S L66K Intel, FW82801DB S L66K Datasheet - Page 68

• Manufacturer Part Number: FW82801DB S L66K
• Manufacturer: Intel

Specifications of FW82801DB S L66K

• Lead Free Status / RoHS Status: Supplier Unconfirmed

Functional Description
5.1.2
5.1.3
5.1.4
68
Note: If the processor issues a locked cycle to a resource that is too slow (e.g., PCI), the ICH4 will not
Note: Locked cycles are assumed to be rare. Locks by PCI targets are assumed to exist for a short
allow upstream requests to be performed until the cycle completion. This may be critical for
isochronous buses which assume certain timing for their data flow (e.g., AC ’97 or USB). Devices
on these buses may suffer from underrun if the asynchronous traffic is too heavy. Underrun means
that the same data is sent over the bus while ICH4 is not able to issue a request for the next data.
Snoop cycles are not permitted while the front side bus is locked.
duration (a few microseconds at most). If a system has a very large number of locked cycles and
some that are very long, then the system will definitely experience underruns and overruns. The
units most likely to have problems are the AC ’97 controller and the USB controllers. Other units
could get underruns/overruns, but are much less likely. The IDE controller (due to its stalling
capability on the cable) should not get any underruns or overruns.
PCI-to-PCI Bridge Model
From a software perspective, the ICH4 contains a PCI-to-PCI bridge. This bridge connects the hub
interface to the PCI bus. By using the PCI-to-PCI bridge software model, the ICH4 can have its
decode ranges programmed by existing plug-and-play software such that PCI ranges do not
conflict with AGP and graphics aperture ranges in the host controller.
IDSEL to Device Number Mapping
When addressing devices on the external PCI bus (with the PCI slots) the ICH4 will assert one
address signal as an IDSEL. When accessing device 0, the ICH4 will assert AD16. When accessing
Device 1, the ICH4 will assert AD17. This mapping continues all the way up to device 15 where
the ICH4 asserts AD31. Note that the ICH4’s internal functions (AC ’97, IDE, USB, and PCI
Bridge) are enumerated like they are on a separate PCI bus (the hub interface) from the external
PCI bus. The integrated LAN controller is Device 8 on the ICH4’s PCI bus, and hence it uses
AD24 for IDSEL
SERR# Functionality
There are several internal and external sources that can cause SERR#. The ICH4 can be
programmed to cause an NMI based on detecting that an SERR# condition has occurred. The NMI
can also be routed to instead cause an SMI#. Note that the ICH4 does not drive the external PCI bus
SERR# signal active onto the PCI bus. The external SERR# signal is an input into the ICH4 driven
only by external PCI devices. The conceptual logic diagrams in
all sources of SERR#, along with their respective enable and status bits.
ICH4 error reporting logic is configured for NMI# generation.
Figure 5-1
Intel
®
Figure 5-3
82801DB ICH4 Datasheet
and
Figure 5-2
shows how the
illustrate