• <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 閱讀(160) 評(píng)論(0)  編輯 收藏 引用 所屬分類: 拿來主義
            <2007年1月>
            31123456
            78910111213
            14151617181920
            21222324252627
            28293031123
            45678910

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

            常用鏈接

            留言簿(4)

            隨筆分類(70)

            隨筆檔案(71)

            charles推薦訪問

            搜索

            •  

            積分與排名

            • 積分 - 50447
            • 排名 - 449

            最新評(píng)論

            閱讀排行榜

            評(píng)論排行榜

            99久久国产热无码精品免费| 成人a毛片久久免费播放| 久久午夜综合久久| 思思久久99热只有频精品66| 亚洲午夜久久久影院| 久久国产精品-久久精品| 国产香蕉久久精品综合网| 久久综合88熟人妻| 久久国产香蕉一区精品| 国产成人精品三上悠亚久久| 丰满少妇高潮惨叫久久久| 国产一区二区精品久久岳| 亚洲AV乱码久久精品蜜桃| 国产成人精品久久亚洲| 无码精品久久久天天影视| 亚洲欧洲中文日韩久久AV乱码| 精品国产一区二区三区久久久狼| 亚洲国产精品无码久久久久久曰 | 久久无码AV一区二区三区| 久久精品中文无码资源站| 久久人人青草97香蕉| 国产精品成人99久久久久 | 久久亚洲私人国产精品vA| 国产99久久久国产精免费| 久久精品国产网红主播| 亚洲精品乱码久久久久久| 青青热久久国产久精品 | 无码国内精品久久综合88| 国产综合精品久久亚洲| 97久久久精品综合88久久| 日韩AV无码久久一区二区| 久久只这里是精品66| 尹人香蕉久久99天天拍| 一个色综合久久| 精品综合久久久久久97| 国内精品久久久久影院薰衣草 | 久久久噜噜噜久久熟女AA片| 久久棈精品久久久久久噜噜| 人妻无码αv中文字幕久久| 久久妇女高潮几次MBA| 午夜不卡久久精品无码免费|