• <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 閱讀(160) 評(píng)論(0)  編輯 收藏 引用 所屬分類: 拿來主義
            <2006年11月>
            2930311234
            567891011
            12131415161718
            19202122232425
            262728293012
            3456789

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

            常用鏈接

            留言簿(4)

            隨筆分類(70)

            隨筆檔案(71)

            charles推薦訪問

            搜索

            •  

            積分與排名

            • 積分 - 50470
            • 排名 - 449

            最新評(píng)論

            閱讀排行榜

            評(píng)論排行榜

            精品久久久久久久国产潘金莲| 久久久久国产亚洲AV麻豆| 午夜不卡888久久| 久久久久99精品成人片直播| 色天使久久综合网天天| 久久影院午夜理论片无码| 久久se精品一区二区影院 | 久久五月精品中文字幕| 久久国产成人精品麻豆| 国产精品久久久久影院嫩草 | 久久er国产精品免费观看8| 99久久精品费精品国产| 久久久精品免费国产四虎| 久久亚洲国产欧洲精品一| 99国内精品久久久久久久 | 婷婷伊人久久大香线蕉AV | 亚洲国产精品久久久久| 精品国产一区二区三区久久蜜臀| 国产一区二区精品久久凹凸| 久久久WWW成人| 91久久精品电影| 婷婷久久综合| 午夜天堂av天堂久久久| 国产精品一久久香蕉产线看| 97超级碰碰碰碰久久久久| 欧美久久一区二区三区| 亚洲愉拍99热成人精品热久久 | 亚洲欧美成人久久综合中文网| 免费一级欧美大片久久网| 亚洲精品乱码久久久久久蜜桃图片| 久久综合噜噜激激的五月天| 9191精品国产免费久久| 久久无码中文字幕东京热| 久久91综合国产91久久精品| 伊人久久大香线蕉无码麻豆| www.久久热.com| 无码国内精品久久综合88| 一本大道加勒比久久综合| 久久精品国产亚洲AV蜜臀色欲| 久久精品国产精品青草app| 精品综合久久久久久98|