• <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久久久精品免费观看国产| 久久免费视频一区| 91精品国产91久久久久久| 99久久成人18免费网站| 久久人人爽人人爽人人片av麻烦| 国产国产成人精品久久| 亚洲AⅤ优女AV综合久久久| 国产韩国精品一区二区三区久久| 2020国产成人久久精品| 青青青伊人色综合久久| 色综合久久综合中文综合网| 精品久久久无码中文字幕天天| 久久国产精品无码HDAV| 亚洲中文字幕无码久久2020| 亚洲国产成人久久精品99 | 97久久超碰成人精品网站| 久久亚洲电影| 久久久久久国产精品免费免费| 九九精品99久久久香蕉| 亚洲午夜久久久久久久久久| 亚洲国产视频久久| 亚洲国产日韩欧美综合久久| 久久久久久久综合综合狠狠| 99久久伊人精品综合观看| 日韩精品久久久久久| 天天爽天天爽天天片a久久网| 久久久久人妻精品一区| 久久久久亚洲AV无码网站| 无码超乳爆乳中文字幕久久| 久久久久亚洲AV无码永不| 精品久久人妻av中文字幕| 波多野结衣中文字幕久久| 国内精品久久久久| 久久精品国产亚洲麻豆| 精品久久久久中文字幕一区| 久久亚洲欧洲国产综合| 亚洲欧美久久久久9999| 色欲久久久天天天综合网| 97久久精品午夜一区二区| 国产精品va久久久久久久| 亚洲性久久久影院|