• <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)  編輯 收藏 引用 所屬分類: 拿來主義
            <2006年11月>
            2930311234
            567891011
            12131415161718
            19202122232425
            262728293012
            3456789

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

            常用鏈接

            留言簿(4)

            隨筆分類(70)

            隨筆檔案(71)

            charles推薦訪問

            搜索

            •  

            積分與排名

            • 積分 - 50764
            • 排名 - 448

            最新評論

            閱讀排行榜

            評論排行榜

            一本一道久久a久久精品综合| 色综合久久久久久久久五月| AAA级久久久精品无码片| 久久九九久精品国产免费直播| 国产精品嫩草影院久久| 91久久国产视频| 亚洲中文久久精品无码ww16| 久久香蕉超碰97国产精品| 精品国产综合区久久久久久| 一级做a爰片久久毛片毛片| 国产V亚洲V天堂无码久久久| 日本久久中文字幕| a高清免费毛片久久| 久久丫忘忧草产品| 久久久精品国产亚洲成人满18免费网站| 欧美久久精品一级c片片| 亚洲国产精品成人久久蜜臀| 99国产欧美精品久久久蜜芽| 思思久久99热只有频精品66| 国产精品久久久久久久 | 伊人久久综在合线亚洲2019| 久久久久一本毛久久久| 无码国内精品久久人妻蜜桃| 久久亚洲视频| 美女写真久久影院| 99精品国产在热久久无毒不卡 | 好久久免费视频高清| 伊人情人综合成人久久网小说 | 91精品国产色综合久久| 欧美性猛交xxxx免费看久久久| 久久综合噜噜激激的五月天| 天堂无码久久综合东京热| 国产 亚洲 欧美 另类 久久 | 性做久久久久久久久久久| 久久99热精品| 国内精品久久久久久99| 亚洲第一极品精品无码久久| 国产成年无码久久久免费| 国产精品久久久久久久久久影院 | 欧美久久亚洲精品| 久久国产欧美日韩精品|