• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>
            posts - 71,  comments - 41,  trackbacks - 0

            What's a Bus?

            ? 2003 by Charles C. Lin. All rights reserved.

            It's a Bunch of Wires

            One wire allows you to transmit a bit. However, most of the times, we need to transmit 32 bits. So, we want to have 32 wires. It's useful to think of these 32 wires as a group.

            To refer to the wires, we may write B31..0. Each wire is referred to by a subscript. Thus, Bi refers to wire i.

            Bmax..min refers to the wires from Bmax to Bmin, inclusive.

            Sometimes it's useful to talk about saying what values are on the bus. However, 32 bits is a lot to write, so it's convenient to write using 8 hex digits (which is equivalent to 32 bits).

            This can be written like B31..0 = 0x10001000. In this case B31 = 0, B30 = 0B29 = 0, B28 = 1 . Recall that every hex digit can be rewritten as 4 bits.

            As with the wire, we want at most one device writing a 32 bit value to the bus. However, any number of devices can read from the bus.

            We expect, over time, that different devices will take turn who writes to the bus, and that values will change.

            Realize that even though a device is writing to a bus, other devices don't have to read the value off the bus. Devices can choose to ignore the values on the bus.

            This makes it sound like the devices act independently of one another, but it's more like an orchestra. There are many parts, but they are being orchestrated to act together. An orchestra has many instruments, but their purpose is to play parts of a whole song. That's how you should view the parts of a computer.

            The role of the bus is to allow devices to communicate with another.

            Is a Bus a Good Idea?

            You may have noticed that the bus seems like a poor way for more than one device to communicate. Only one device can write to the bus at a time. Wouldn't it be more efficient to have a direct connection between any pair of devices?

            That may be true, but there are some problems. First, the number of direct connections is O(n2). In particular, it's [n X (n-1)]/ 2 connections.

            That's a lot of connections. If you have 4 devices, you have 6 connections. However, you could have just a single bus to connect all four devices.

            The bigger problem is that hardware is hardware. A device has some number of inputs and outputs, and those are fixed in number. Out of necessity, you have to use a bus or some device which does not require a device to need more inputs or outputs.

            posted on 2007-01-23 14:19 Charles 閱讀(164) 評論(0)  編輯 收藏 引用 所屬分類: 拿來主義
            <2007年1月>
            31123456
            78910111213
            14151617181920
            21222324252627
            28293031123
            45678910

            決定開始寫工作日記,記錄一下自己的軌跡...

            常用鏈接

            留言簿(4)

            隨筆分類(70)

            隨筆檔案(71)

            charles推薦訪問

            搜索

            •  

            積分與排名

            • 積分 - 50780
            • 排名 - 448

            最新評論

            閱讀排行榜

            評論排行榜

            成人国内精品久久久久一区| 欧美日韩精品久久久久| 色偷偷久久一区二区三区| 无码国内精品久久人妻| 天天爽天天狠久久久综合麻豆| 7777精品伊人久久久大香线蕉| 99久久夜色精品国产网站| 波多野结衣中文字幕久久| 国产成人久久精品麻豆一区 | 性做久久久久久免费观看| 狠狠色丁香久久婷婷综合_中| 久久综合给合久久国产免费| 久久精品国产一区| 人妻无码αv中文字幕久久琪琪布| 久久99精品国产自在现线小黄鸭| 狠狠人妻久久久久久综合蜜桃| 亚洲AV日韩AV天堂久久| 久久久久亚洲?V成人无码| 国产成人无码久久久精品一| 欧美一级久久久久久久大| 久久国产乱子伦精品免费强| 久久无码AV一区二区三区| 久久国产精品波多野结衣AV| 久久久一本精品99久久精品88| 伊人情人综合成人久久网小说| 夜夜亚洲天天久久| 久久精品国产亚洲AV电影| 97精品伊人久久大香线蕉| 欧美久久久久久精选9999| 久久精品国产福利国产秒| 久久久婷婷五月亚洲97号色| 久久精品国产久精国产果冻传媒| 国产免费福利体检区久久| 97r久久精品国产99国产精| 无码久久精品国产亚洲Av影片| 偷窥少妇久久久久久久久| 欧美精品丝袜久久久中文字幕| 国产三级观看久久| 久久精品国产一区二区| 久久久精品波多野结衣| 久久综合色区|