[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PCI queries ( protocols + ASIC related )
The 2^25 has nothing to do with how long it takes you to load your boot
image over the network. All of the necessary code should already be in a
ROM on your board.
The code that is in your rom (which is immediately accessable upon
power-on) should execute and fetch the OS image over the network.
Your only concern for the 2^25 clock cycle limit is:
- Can you get the Vendor/Device+PCI configuration information from your
eeprom/rom (assuming that they aren't constant values).
See below for a couple more comments.
-- Neal Palmer
On Tue, 10 Oct 2000, Ajit Madhekar wrote:
> Hello pci-sig list members,
> I have following queries
> PCISIG section 18.104.22.168 says about target initial latency as 2^25 pci clocks
> In this period the device ( network controller card ) is supposed to get the
> boot image from the remote system.I have following doubts on this
> 1) How big is the OS image ? , because 2^25 clocks time comes to be 0.5 sec
> for 66 mhz PCI clock rate. Assuming the packet driver code in boot ROM is
> configuring a network controller ASIC for full duplex 100 Mbps mode then in
> 1/2 sec ,
> 6 Mega Bytes can be transferred on network.
> What is the os image size that needs to be put in the system area thru PCI
> cycles ?
> 2) If the device is not able to get the full image in the specified time ,
> can it still pretend as bridge and give the remaining data with the latency
> of 32 clocks after the frame assertion for each PCI cycle ?
> 3) My library supports following pads which are 5 Volt compatible
> PDBxDGZ(CMOS 3 state o/p pad with 5 v compatible where x stands for drive
> capacity in mA) is used for CBE and AD .
> Now, for AD lines and other PCI signals, what is the needed drive
> strength I have to keep ?
> Also library has some pads PCI66DGZ ( 3 state o/p 66 Mhz PCI buffer pad
> with i/p and limited slew rate 5 volt tolerant ) which we used for s/t/s
> I observed the slew rates for both the mentioned pads and it is same 0.1 ns
> Can I use the PDBxDGZ pad for all PCI bi-directional signals ?
> or , I have to use the PCI66DGZ pad for s/t/s signals ?
yep. But be carefule to look at ALL of the specification numbers,
especially the 5V PCI compliant number, and complain to the vendor when
you find the one that doesn't meet the PCI spec.
-- Neal Palmer
The Dini Group
1010 Pearl St #6
La Jolla, CA 92037
(858) 454-3419 x16
(858) 454-1728 (Fax)