Return to BSD News archive
Xref: sserve comp.os.386bsd.development:1733 comp.unix.bsd:13335 Newsgroups: comp.os.386bsd.development,comp.unix.bsd Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!news.kei.com!eff!usenet.ins.cwru.edu!agate!apple.com!amd!netcomsv!netcomsv!netcom.com!jmonroy From: jmonroy@netcom.com (Jesus Monroy Jr) Subject: Re: Late comments on the DMA problem. Message-ID: <jmonroyCK6o70.4B5@netcom.com> Followup-To: comp.os.386bsd.development,comp.unix.bsd Organization: NETCOM On-line Communication Services (408 241-9760 guest) X-Newsreader: TIN [version 1.2 PL1] References: <jmonroyCJy610.HB7@netcom.com> <1994Jan21.095505.8375@cc.usu.edu> <jmonroyCK2t6n.1pM@netcom.com> <1994Jan24.103912.8591@cc.usu.edu> Date: Tue, 25 Jan 1994 11:35:24 GMT Lines: 26 ivie@cc.usu.edu wrote: : In article <jmonroyCK2t6n.1pM@netcom.com>, jmonroy@netcom.com (Jesus Monroy Jr) writes: : > ivie@cc.usu.edu wrote: : > : Since you can't get an interrupt to tell you that the DMA controller has : > : finished doing a page, you can't reload the DMA addresses when the end of : > : a page is reached. : > : : > please define page. : > your message is ambiguous. : Page = virtual memory page. I'm most familiar with the VAX, where a page : is 512 bytes; I don't know how big it is on these newfangled 386 thingies. : a memory page is not defined well, but I beleive (if memory serves) a memory page for MS-DOS is 512 bytes. As for an interrupt, the FDC does interrupt when the I/O transaction is complete. So maybe this negates your comments, which are still a bit ambiguous. Thanks for your input. -- Jesus Monroy Jr jmonroy@netcom.com Zebra Research /386BSD/device-drivers /fd /qic /clock /documentation ___________________________________________________________________________