• <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 閱讀(170) 評論(0)  編輯 收藏 引用 所屬分類: 拿來主義
            <2006年12月>
            262728293012
            3456789
            10111213141516
            17181920212223
            24252627282930
            31123456

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

            常用鏈接

            留言簿(4)

            隨筆分類(70)

            隨筆檔案(71)

            charles推薦訪問

            搜索

            •  

            積分與排名

            • 積分 - 51407
            • 排名 - 449

            最新評論

            閱讀排行榜

            評論排行榜

            久久青青草视频| 欧美午夜精品久久久久免费视 | 久久亚洲精品人成综合网| 久久精品中文騷妇女内射| 狠狠色丁香婷婷综合久久来来去 | 精品国产婷婷久久久| 国产精品亚洲综合久久| 久久国产高清字幕中文| 久久精品中文字幕一区| 精品无码久久久久久久动漫| 欧美牲交A欧牲交aⅴ久久| 蜜桃麻豆www久久国产精品| 国产精品18久久久久久vr| 久久精品国产99久久久古代| 无码8090精品久久一区| 久久精品嫩草影院| 久久精品国产亚洲av水果派| 久久久久久午夜精品| 午夜精品久久久久成人| 久久噜噜久久久精品66| 亚洲午夜久久久精品影院 | 久久久久精品国产亚洲AV无码| 2021久久国自产拍精品| 色欲久久久天天天综合网| 亚洲日本va午夜中文字幕久久 | 一本大道加勒比久久综合| 97r久久精品国产99国产精| 无遮挡粉嫩小泬久久久久久久 | 久久精品国产72国产精福利| 久久丫精品国产亚洲av| 久久精品国产亚洲Aⅴ香蕉 | 91精品国产高清久久久久久io | 色婷婷综合久久久久中文| 久久精品国产久精国产一老狼| 精品久久久久久久久久中文字幕| 99久久婷婷国产综合精品草原| 狠狠色丁香婷婷综合久久来来去| 久久99热这里只有精品国产| 久久精品国产第一区二区| 欧美精品丝袜久久久中文字幕 | 久久精品青青草原伊人|