• <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

            最新評論

            閱讀排行榜

            評論排行榜

            久久久精品午夜免费不卡| 欧美亚洲国产精品久久高清| 午夜天堂av天堂久久久| 一本一本久久a久久综合精品蜜桃| 亚洲欧洲中文日韩久久AV乱码| 合区精品久久久中文字幕一区| 一本色道久久99一综合| 97久久国产亚洲精品超碰热| 久久国产精品视频| 久久精品国产2020| 精品一区二区久久| 香蕉久久AⅤ一区二区三区| 久久精品亚洲日本波多野结衣| 精品无码久久久久久国产| 久久笫一福利免费导航| 久久久精品国产sm调教网站 | 男女久久久国产一区二区三区| 日韩乱码人妻无码中文字幕久久 | 久久亚洲AV无码精品色午夜 | 一本久久a久久精品综合夜夜| 久久天天躁狠狠躁夜夜av浪潮 | 中文字幕精品无码久久久久久3D日动漫| 久久精品国产免费观看| 久久久久久免费一区二区三区| 久久久久久国产a免费观看黄色大片| 久久天堂电影网| 久久天堂AV综合合色蜜桃网| 亚洲欧美日韩精品久久亚洲区 | 久久精品一区二区三区不卡| 亚洲国产小视频精品久久久三级| 中文字幕成人精品久久不卡| 久久久久亚洲av无码专区 | 国产成人久久精品二区三区| 久久夜色精品国产噜噜亚洲AV| 久久久久国产一区二区三区| 久久综合久久综合久久| 精品久久久久久无码专区| 色欲av伊人久久大香线蕉影院| 免费无码国产欧美久久18| 亚洲欧美成人久久综合中文网| 精品无码久久久久久久动漫|