Article View: comp.arch
Article #2221Re: Instruction (dis)continuation (
From: Allen J. Baum
Date: Thu, 14 Sep 1989 00:22
Date: Thu, 14 Sep 1989 00:22
16 lines
1091 bytes
1091 bytes
[]
>In article <261500010@S34.Prime.COM> BEAR@S34.Prime.COM writes:
>
>It would appear that what this thread is *really* discussing is whether or
>not MEMORY MAPPED I/O is a good thing. The concensus seems to be that it
>should be avoided (use I/O instructions instead). If it can't be avoided,
>be careful.
OK, I'll bite. What are the characteristics of memory mapped I/O that enable
it to avoid the problems we are talking about? Note that I am assuming that
memory mapped I/O is done with simple Load/Store instructions otherwise, and
not hairy mem-mem translate&test&stand-on-your-head instructions.
--
baum@apple.com (408)974-3385
{decwrl,hplabs}!amdahl!apple!baum
Technical Details
Message-ID:
<34701@apple.Apple.COM>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!sun-barr!apple!baumReferences:
<2353@oakhill.UUCP> <261500010@S34.Prime.COM>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!sun-barr!apple!baum From: baum@Apple.COM (Allen J. Baum) Newsgroups: comp.arch Subject: Re: Instruction (dis)continuation ( Message-ID: <34701@apple.Apple.COM> Date: 14 Sep 89 00:22:47 GMT References: <2353@oakhill.UUCP> <261500010@S34.Prime.COM> Reply-To: baum@apple.UUCP (Allen Baum) Organization: Apple Computer, Inc. Lines: 16