<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Bus (computing) - Page 36 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Bus_(computing)&amp;p=35">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Bus_%28computing%29&amp;p=37">3.Next</a>
</p>
<p>various peripheral devices on the other. A bus controller accepted data from the CPU side to be moved to the peripherals side, thus shifting the communications protocol burden from the CPU itself. This allowed the CPU and memory side to evolve separately from the peripheral bus. Devices on the bus could talk to each other with no CPU intervention. This led to much better performance but also required the cards to be much more complex. These buses also often addressed speed issues by being bigger in terms of the size of the data path, moving from</p><p>
<a accesskey="1" href="page.php?w=Bus_(computing)&amp;p=35">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Bus_%28computing%29&amp;p=37">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
