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

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

            常用鏈接

            留言簿(4)

            隨筆分類(70)

            隨筆檔案(71)

            charles推薦訪問

            搜索

            •  

            積分與排名

            • 積分 - 51411
            • 排名 - 449

            最新評(píng)論

            閱讀排行榜

            評(píng)論排行榜

            国产精品99久久久久久猫咪 | 久久WWW免费人成一看片| 欧美精品一本久久男人的天堂| 亚洲国产二区三区久久| 一本久久综合亚洲鲁鲁五月天| 国产成人久久精品一区二区三区| 久久精品国产半推半就| 99久久国产亚洲综合精品| 久久免费小视频| 久久久老熟女一区二区三区| 久久伊人中文无码| 国产精品免费福利久久| 欧美亚洲国产精品久久高清 | 狠狠久久亚洲欧美专区| 麻豆久久| 一级做a爰片久久毛片人呢| 日韩乱码人妻无码中文字幕久久| 亚洲v国产v天堂a无码久久| 免费观看成人久久网免费观看| 久久婷婷五月综合97色一本一本| 色婷婷综合久久久久中文字幕 | 国产成年无码久久久免费| 精品久久久久中文字幕一区| 伊人色综合久久天天| 国产亚州精品女人久久久久久| 久久亚洲AV成人无码| 2021久久国自产拍精品| 欧美亚洲日本久久精品| 久久综合久久综合久久| 中文字幕日本人妻久久久免费| 91精品国产91久久久久福利| 日韩十八禁一区二区久久| 精品久久久久久国产91| 久久久久亚洲av综合波多野结衣| 91久久精品国产免费直播| 久久久精品2019免费观看| 99精品国产在热久久无毒不卡| 少妇久久久久久被弄到高潮| 国产亚洲精午夜久久久久久| 日韩亚洲欧美久久久www综合网| 精品熟女少妇a∨免费久久|