with reference to fig1 the various methods discussed herein may be implemented within a typical computer system 101 which may include one or more computers or workstations in various combinations . an exemplary hardware configuration of a computer system which may be used in conjunction with the present invention is illustrated and includes a processor device 103 , such as a conventional microprocessor , and a number of other units interconnected through a system bus 105 , which may be any host system bus . the system bus may have one or more additional processors connected to the bus such as processor 107 . it is noted that the processing methodology disclosed herein will apply to many different bus and / or network configurations . the bus 105 , as well as any of the other busses illustrated , may be extended as shown to include further connections to other computer systems , workstations or networks , and other peripherals and the like . the computer system shown in fig1 includes a local memory 109 . a local bus controller and dram system memory ( not shown ) are also typically connected to the system bus 105 . the system bus 105 is connected through a pci ( peripheral component interconnect ) host bridge a circuit 111 to a second bus 113 , which , in turn , is connected through an expansion bus interface 115 to a an expansion bus 117 in the present example . the expansion bus 117 may include connections to a keyboard / mouse adapter 119 and also to other peripheral device adapters such as peripheral device adapter 121 . the exemplary embodiment illustrated also includes a pci host bridge b 123 connecting the system bus 105 to a multi - speed or &# 34 ; d66 &# 34 ; bus 125 which is implemented in accordance with the disclosed multi - speed methodology . the multi - speed bus 125 is connected , in the present example , to a 66 mhz pci device 127 and also to a &# 34 ; d66 &# 34 ; pci device 129 . the &# 34 ; d66 &# 34 ; device in the present example , and the pci host bridge , are capable of operating at double the speed of the 66 mhz device , and devices with this capability shall be hereinafter referred to as &# 34 ; d66 &# 34 ; devices . the methodology herein disclosed provides a solution to the pci bus speed limitation as hereinbefore described by defining means to enhance and extend the current 66 mhz pci architecture definition , providing both 66 mhz and 133 mhz data rate capability . the d66 pci bus definition described herein includes all of the protocol capabilities of the pci standard , i . e . &# 34 ; pci local bus specification , production version , revision 2 . 1 , jun . 1 , 1995 , and updates , plus additional d66 capabilities . in accordance with the present disclosure , the data source device , i . e . the device which is providing information requested by a requesting device in the system , provides a data strobe signal with the requested data . the pci specification requires that each pci device receives its own individual clock signal which is not bussed . that is , the master is the source of data and provides the data strobe signal during a write operation , and the target is the source of data and provides the data strobe signal during a read operation . the data strobe signal is then derived by both the master and the target from its 66 mhz clock signal , or from its 133 mhz clock signal , ( whichever clock signal is utilized ), for d66 operations . for d66 operations , the data is clocked or strobed at 133 mhz by being triggered on both edges of a 66 mhz strobe signal instead of the pci implementation of only leading edge triggering . d66 - capable devices connected to the d66 bus 125 are able to dynamically support either the 66 mhz or 133 mhz operation at the beginning of the data phase of a data transaction , i . e . either a read or a write operation . d66 devices are able to identify that they are d66 - capable , i . e . capable of running at either 66 mhz or 133 mhz , in any of several ways such as by utilizing an un - architected configuration bit , although that particular method is not required . currently reserved pci bus pins are utilized for the data strobe line when both the controlling master and the selected target are d66 devices . such bus pins are treated as reserved by d66 devices when not operating in the d66 mode . as used in the present disclosure , a &# 34 ; master &# 34 ; is a device requesting a data transaction such as a read or a write transaction , and a &# 34 ; target &# 34 ; is a device responding to the request by providing the data requested in a read , or by receiving the data being written to it from the master . in the present example , the d66 operation must transfer a minimum of 8 bytes ( 32 bits ) or 16 bytes ( 64 bits ) since d66 data transfers are clocked on both edges of the system clock . both 133 mhz d66 operations and existing 66 mhz operations are dynamically supported on the same bus segment 125 . there are several methods which may be implemented to accomplish that requirement . a preferred method is illustrated in fig3 and fig4 with reference to the timing signals shown in fig2 a and fig2 b . in the timing chart of fig2 a , typical pci signals such as the pci 66 mhz clock signal clk , and the address signal ad , including a bus turnaround phase and a data phase , are illustrated . also shown are representations of the new master strobe signal mstb and the target strobe signal tstb during a read function of a d66 data transfer operation . similarly , fig2 b illustrates corresponding signals which are generated during a write function . as hereinbefore noted , two currently reserved pci bus signal lines or pins are utilized for two new strobe signals , i . e . a master strobe signal mstb and an target strobe signal tstb . as illustrated in fig3 a d66 read operation begins 301 by a master device outputting or pulsing 303 a predetermined first strobe signal or master strobe signal mstb to the new mstb line on the bus 125 during the address phase of a data transaction cycle . that signal mstb indicates that the master is capable of operating in a d66 mode , i . e . at a data frequency of 133 mhz by clocking data on both edges of the strobe signal . a target device connected to the bus 125 would then decode the mstb signal 305 and if the selected target is d66 capable 307 , the target would then provide a predetermined second strobe signal or target strobe signal tstb 309 to the appropriate bus line during a bus turn - around phase indicating that the target is capable of operating in the d66 mode , i . e . at 133 mhz data rate in the present example . if the target is not d66 capable 307 , the data transaction proceeds in accordance with the default pci 66 mhz speed 308 . when the target device outputs a tstb signal 309 during the turn - around cycle , the master decodes the tstb 310 determining that the target is d66 capable , and prepares to read data at the 133 mhz rate , and if the selected target is d66 capable , the target provides a source synchronous tstb signal with the &# 34 ; read &# 34 ; data at a data rate of 133 mhz . the data is read by the master device at the d66 frequency of 133 mhz 313 beginning with the first data phase of the transaction cycle , using tstb to clock data off the bus 314 , after which the particular read process is ended 315 . if the mstb is not decoded by the selected target device 311 , the process defaults to normal pci 66 mhz operation 308 . a d66 write operation sequence is illustrated in fig4 . as shown , when the process initiates 401 , the master device provides a master strobe signal mstb 403 to the new mstb line on the bus 125 during an address phase of a transaction cycle indicating that the master device is capable of d66 data transactions at 133 mhz in the present example . the d66 capable targets will then decode the mstb signal during the address phase 405 . if a d66 target device is selected 407 , the target inserts a wait state 409 into the data transaction cycle and also provides a target strobe signal tstb 411 during the wait state . the master then decodes the tstb signal during the wait state 413 and if the target is d66 capable 415 , the data is written or transferred from the master to the target at the d66 data rate of 133 mhz 417 beginning with the first data phase . the master then pulses the mstb during the data phase 418 , and the write process ends 419 . if either the master is not d66 capable 407 , or the target is not d66 capable 415 , selected 407 or the target is not d66 capable 415 , then the write operation reverts to the pci clocking at 66 mhz 408 . another technique would use a shared strobe signal and use configuration bits to restrict to either d66 operation or normal pci transfers on the bus 125 but not both . that approach is not preferred since it is not backward compatible to allow operation of mixed d66 and standard pci 66 mhz devices . another approach would use only one shared strobe line and multiplex master strobe and target strobe signals thereon . that approach would still allow system operation with mixed 66 mhz and d66 133 mhz devices , but is still not the preferred method since the shared strobe line would have to have turnaround clock cycles during the initial handshaking period , which , in turn , would require multiple wait states or starting with 66 mhz operation transfers and phasing over to d66 133 mhz transfers at a later time . although there may be other variations regarding the handling of the initial handshaking process , the use of two separate strobe lines mstb and tstb as illustrated in the disclosed embodiment is the preferred approach . during d66 133 mhz operations , pacing between data phases would not be implemented . transfers would be blocked into minimum 32 byte blocks , and transactions can only be delayed at the beginning of a transfer or between 32 byte blocks . peer - to - peer is supported for both 66 mhz and 133 mhz operations and configuration and i / o accesses are handled as standard 66 mhz operation . each pci device receives a separate clock signal as the standard 66 mhz pci bus does . the disclosed methodology supports pacing with irdy # and trdy # only between data blocks when utilizing data blocking . when utilizing optional data blocking , data transfers must begin on the beginning of the minimum block size , must transfer integer multiples of data blocks and must not pace except between 32 byte blocks . when the last block of data is less than 32 bytes , that transfer is handled in the normal non - blocking fashion . pacing with irdy # and trdy # signals is allowed between data transfers when performing normal 66 mhz operations . the disclosed methodology supports optional synchronization type commands when performing d66 133 mhz operations . the d66 133 mhz pci data transfer methodology disclosed herein provides a number of enhancements over standard pci 66 mhz processing in order to improve the data throughput achievable compared to the standard pci architecture . the method and apparatus of the present invention has been described in connection with a preferred embodiment as disclosed herein . although an embodiment of the present invention has been shown and described in detail herein , along with certain variants thereof , many other varied embodiments that incorporate the teachings of the invention may be easily constructed by those skilled in the art . accordingly , the present invention is not intended to be limited to the specific form set forth herein , but on the contrary , it is intended to cover such alternatives , modifications , and equivalents , as can be reasonably included within the spirit and scope of the invention .