青青草原综合久久大伊人导航_色综合久久天天综合_日日噜噜夜夜狠狠久久丁香五月_热久久这里只有精品

posts - 297,  comments - 15,  trackbacks - 0

The DMA is another two chips on your motherboard (usually is an Intel 8237A-5 chips) that allow you (the programmer) to offload data transfers between I/O boards. DMA actually stands for 'Direct Memory Access'.

DMA can work: memory->I/O, I/O->memory. The memory->memory transfer doesn't work. It doesn't matter because ISA DMA is slow as hell and thus is unusable. Futhermore, using DMA for zeroing out memory would massacre the contents of memory caches.

What about caches and DMA? L1 and L2 caches work absolutely transparently. When DMA writes to memory, caches autmatically load or least invalidate the data that go into the memory. When DMA reads memory, caches supply the unwritten bytes so not old but new values are tranferred to the peripheral.

There are signals DACK, DRQ, and TC. When a peripheral wants to move a byte or 2 bytes into memory (is dependent on whether 8 bit or 16 bit DMA channel is in use -- 0,1,2,3 are 8-bit, 5,6,7 are 16-bit), it issues DRQ. DMA controller chats with CPU and after some time DMA controller issues DACK. Seeing DACK, the peripheral puts it's byte on data bus, DMA controller takes it and puts it in memory. If it was the last byte/word to move, DMA controller sets up also TC during the DACK. When peripheral sees TC, it is possible it will not want any more movements,

In the other direction, everything is the same, but first the byte/word is fetched from the memory and then DACK is generated and the peripheral takes the data.

DMA controller has only 8-bit address counter inside. There is external ALS573 counter for each chip so it makes programmer see it as DMA controller had 16 bits of address counter per channel inside. There are more 8 bits of address per channel of so called page register in LS612 that unfortunately do not increment as those in ALS573. All these 24 bits can address 16777216 of distict addresses.

Recapitulation: for each channel, independently, you see 16 bits of auto-incrementing counter, and 8 bits of page register which doesn't increment.

The difference between 16-bit DMA channels and 8-bit DMA channels is that the address bits for 16-bit channels are wired one bit left to the address bus so every address is 2 times bigger. The lowest bit is 0. The highest bit of page register would fit into bit 24 which is not on ISA so that it is left unconnected. The bus control logic is wired for 16-bit channels in a manner every single DMA transfer, a 16-bit cycle is generated, so ISA device puts 16 bits onto the bus at the time. I don't know what happens if you use 16-bit DMA channel with XT peripheral. I guess it could work but only be slower.

8-bit DMA: increments by 1, cycles inside 65536 bytes, addresses 16MB, moves 8 bits a time.

16-bit DMA: increments by 2, goes only over even addresses, cycles inside 131072 bytes, addresses 16MB, moves 16 bits a time. Uses 16-bit ISA I/O cycle so it takes less ticks to make one move that the 8-bit DMA.

An example of DMA usage would be the Sound Blaster's ability to play samples in the background. The CPU sets up the sound card and the DMA. When the DMA is told to 'go', it simply shovels the data from RAM to the card. Since this is done off-CPU, the CPU can do other things while the data is being transferred.

Enough basics. Here's how you program the DMA chip.


When you want to start a DMA transfer, you need to know several things:

  • Number of DMA channel you want to use
  • What page to use
  • The offset in the page
  • The length
  • How to tell you peripheral to ask for DMA

  • You cannot transfer more than 64K or 128K of data in one shot, and
  • You cannot cross a page boundary. If you cross it, the lower 16 or 17 bits of address will simply wrap and you only suddenly jump 65536 or 131072 bytes lower that where you expected. It will be absolutely OK and no screw up will be performed. If you will take it in account in your program you can use it.

Restriction #1 is rather easy to get around. Simply transfer the first block, and when the transfer is done, send the next block.

For those of you not familiar with pages, I'll try to explain.

Picture the first 16MB region of memory in your system. It is divided into 256 pages of 64K or 128 pages of 128K. Every page starts at a multiple of 65536 or 131072. They are numbered from 0 to 255 or from 0 to 127.

In plain English, the page is the highest 8 bits or 7 bits of the absolute 24 bit address of our memory location. The offset is the lower 16 or 17 bits of the absolute 24 bit address.

Now that we know where our data is, we need to find the length.

The DMA has a little quirk on length. The true length sent to the DMA is actually length + 1. So if you send a zero length to the DMA, it actually transfers one byte or word, whereas if you send 0xFFFF, it transfers 64K or 128K. I guess they made it this way because it would be pretty senseless to program the DMA to do nothing (a length of zero), and in doing it this way, it allowed a full 64K or 128K span of data to be transferred.

Now that you know what to send to the DMA, how do you actually start it? This enters us into the different DMA channels.

The following chart will describe each channel and it's corresponding port number:

DMA ChannelPageAddressCount
087h0h1h
183h2h3h
281h4h5h
382h6h7h
48FhC0hC2h
58BhC4hC6h
689hC8hCAh
78AhCChCEh

DMA 4. Doesn't exist. DMA 4 is used to cascade the two 8237A chips. When first 8237A wants to DMA, it issues "HRQ" to second chip's DRQ 4. The second chip thinks DMA 4 is wanna be made so issues DRQ 4 to the first chip's HLDA. First chip makes it's own DMA 0-3, then sends to the second "OK second chip, my DMA 4 is complete" and second chip knows it's free on the bus. If this mechanism would not work, the two chips could peck each other on the BUS and the PC would screw up. :+)

from:
posted on 2010-11-14 19:23 chatler 閱讀(703) 評(píng)論(0)  編輯 收藏 引用 所屬分類: OS
<2010年11月>
31123456
78910111213
14151617181920
21222324252627
2829301234
567891011

常用鏈接

留言簿(10)

隨筆分類(307)

隨筆檔案(297)

algorithm

Books_Free_Online

C++

database

Linux

Linux shell

linux socket

misce

  • cloudward
  • 感覺這個(gè)博客還是不錯(cuò),雖然做的東西和我不大相關(guān),覺得看看還是有好處的

network

OSS

  • Google Android
  • Android is a software stack for mobile devices that includes an operating system, middleware and key applications. This early look at the Android SDK provides the tools and APIs necessary to begin developing applications on the Android platform using the Java programming language.
  • os161 file list

overall

搜索

  •  

最新評(píng)論

閱讀排行榜

評(píng)論排行榜

青青草原综合久久大伊人导航_色综合久久天天综合_日日噜噜夜夜狠狠久久丁香五月_热久久这里只有精品
  • <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>
            欧美一级大片在线免费观看| 性欧美超级视频| 欧美国产日产韩国视频| 久久精品二区亚洲w码| 国产综合网站| 欧美成人免费观看| 欧美不卡一区| 亚洲男女毛片无遮挡| 亚洲欧美精品一区| 一区二区在线不卡| 亚洲精品免费网站| 欧美日韩一区二区三区四区在线观看 | 亚洲国产精品123| 亚洲日本精品国产第一区| 欧美三级资源在线| 欧美一区二区久久久| 久久精品视频免费| aa级大片欧美三级| 在线一区欧美| 亚洲第一在线综合在线| 亚洲毛片一区二区| 国产在线视频欧美| 亚洲精品美女91| 国模吧视频一区| 亚洲三级视频| 韩国v欧美v日本v亚洲v| 亚洲精品国产品国语在线app| 国产精品毛片| 亚洲国产高清高潮精品美女| 国产精品av免费在线观看| 久热国产精品视频| 国产精品久久久久秋霞鲁丝| 欧美激情第1页| 国产一区二区三区奇米久涩| 亚洲美女精品一区| 依依成人综合视频| 亚洲一区二区成人| 日韩午夜黄色| 久久久久成人精品| 午夜欧美视频| 欧美亚洲不卡| 亚洲老板91色精品久久| 在线观看国产精品淫| 午夜国产一区| 亚洲免费小视频| 欧美日韩和欧美的一区二区| 免费观看日韩av| 国产伊人精品| 亚洲欧美在线视频观看| 中文精品一区二区三区| 欧美成在线视频| 米奇777超碰欧美日韩亚洲| 国产精品免费在线| 在线一区亚洲| 亚洲欧美日韩一区| 欧美三级午夜理伦三级中视频| 亚洲高清视频一区二区| 尤物在线精品| 猛干欧美女孩| 你懂的亚洲视频| 亚洲第一偷拍| 另类天堂av| 亚洲黄色成人网| 亚洲美女毛片| 欧美日韩调教| 一区二区三区黄色| 亚洲影视中文字幕| 国产精品夜色7777狼人| 亚洲一级一区| 久久偷看各类wc女厕嘘嘘偷窃| 国产一区二区三区在线播放免费观看| 亚洲午夜精品17c| 欧美一级欧美一级在线播放| 国产精品丝袜xxxxxxx| 午夜精品久久久久久久久久久| 欧美一区二区女人| 极品av少妇一区二区| 久久视频在线看| 亚洲国产精品久久久久秋霞蜜臀| 亚洲欧洲精品一区二区三区波多野1战4 | 欧美激情一区二区三区高清视频 | 亚洲精品三级| 亚洲免费在线播放| 国产自产高清不卡| 开元免费观看欧美电视剧网站| 免费中文日韩| 一区二区三区国产在线| 国产精品久久久久久久7电影 | 久久免费观看视频| 亚洲国产日韩欧美| 亚洲午夜激情| 国产精品视频| 久久这里有精品15一区二区三区| 亚洲国产精彩中文乱码av在线播放| 一区二区欧美视频| 国产日韩欧美视频在线| 蜜臀av性久久久久蜜臀aⅴ四虎| 亚洲欧洲中文日韩久久av乱码| 亚洲午夜成aⅴ人片| 国产中文一区二区| 欧美经典一区二区| 午夜视频在线观看一区| 欧美黄在线观看| 香蕉亚洲视频| 亚洲人成在线播放| 国产无遮挡一区二区三区毛片日本| 久久综合九色综合欧美狠狠| 91久久嫩草影院一区二区| 翔田千里一区二区| 91久久午夜| 国产日韩在线看片| 欧美日韩午夜在线| 久久一区亚洲| 亚洲欧美在线播放| 一区二区三区www| 欧美成人精品一区| 欧美一级午夜免费电影| 亚洲全黄一级网站| 黄色成人91| 国产精品青草久久久久福利99| 欧美1区3d| 久久精品国产久精国产思思| 一区二区福利| 亚洲欧洲一区二区在线观看| 美国十次成人| 久久久中精品2020中文| 亚洲欧美日韩中文视频| 日韩视频在线免费观看| 亚洲第一在线视频| 国产亚洲人成a一在线v站| 国产精品久久久久久久久搜平片 | 亚洲激情成人在线| 国产一区二区日韩| 国产精品制服诱惑| 国产精品v日韩精品| 欧美日韩亚洲视频| 欧美日韩天堂| 国产精品激情偷乱一区二区∴| 欧美激情久久久久| 欧美激情免费观看| 欧美精品在线一区二区| 欧美成ee人免费视频| 老牛国产精品一区的观看方式| 久久精品日韩一区二区三区| 性欧美精品高清| 欧美在线视频一区二区| 欧美一级免费视频| 久久精品国产亚洲aⅴ| 久久福利视频导航| 久久都是精品| 美女爽到呻吟久久久久| 欧美成人一区二区| 欧美精品成人| 欧美日韩中文在线观看| 欧美日韩在线一区二区| 国产精品久久久久高潮| 国产伦精品一区二区三区高清版| 国产精品入口| 一区二区三区在线视频免费观看| 一区二区在线视频播放| 亚洲国产欧美一区二区三区久久 | 日韩天堂在线视频| 中日韩美女免费视频网站在线观看| 国产精品99久久久久久久女警| 午夜精品久久久久| 久久综合狠狠综合久久综合88 | 一本大道久久a久久综合婷婷| 中文av字幕一区| 欧美一区二区三区四区在线观看地址 | 欧美一区二区三区视频在线| 欧美专区第一页| 欧美a一区二区| 欧美三级视频| 曰韩精品一区二区| 亚洲视频999| 久久亚洲欧美| 日韩视频在线一区二区三区| 亚洲综合欧美日韩| 欧美成人a视频| 国产精品一区二区在线观看网站| 黑丝一区二区三区| 亚洲香蕉在线观看| 美女福利精品视频| 国产精品99久久久久久久久| 久久免费偷拍视频| 国产精品二区二区三区| 狠狠入ady亚洲精品| 亚洲一级黄色| 亚洲国产黄色| 欧美专区亚洲专区| 国产精品成人av性教育| 亚洲激情综合| 久久天天躁狠狠躁夜夜av| 在线一区欧美| 欧美片在线观看| 亚洲国产日韩在线| 久久天堂精品| 欧美一级久久久| 国产精品日本精品| 一卡二卡3卡四卡高清精品视频|