Return to BSD News archive
Xref: sserve comp.os.386bsd.development:1753 comp.unix.bsd:13355 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!uuspew.uu.net!uunet!decwrl!decwrl!netcomsv!netcom.com!jmonroy From: jmonroy@netcom.com (Jesus Monroy Jr) Subject: Re: Late comments on the DMA problem. Message-ID: <jmonroyCKLDAu.CK@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: <1994Jan24.103912.8591@cc.usu.edu> <940131281@rwsys.wimsey.bc.ca> Date: Wed, 2 Feb 1994 10:04:05 GMT Lines: 27 Randy Wright (rw@rwsys.wimsey.bc.ca) wrote: : ivie@cc.usu.edu () writes: : > 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. : > : 386 virtual memory paging deals in 4-kb pages. : Can you please define this 4-kb page a bit more with a qualifier? (i.e., most *BSD system work this way... may xyz machine with a zoofoo cache system has a great speed advantage with a 4-kb page.. etc....... is this clear? :-} ) -- Jesus Monroy Jr jmonroy@netcom.com Zebra Research /386BSD/device-drivers /fd /qic /clock /documentation ___________________________________________________________________________