Xref: utzoo comp.arch:8709 comp.sys.intel:754 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!nic.MR.NET!thor.acc.stolaf.edu!mike From: mike@thor.acc.stolaf.edu (Mike Haertel) Newsgroups: comp.arch,comp.sys.intel Subject: Duff's Device? (Was: Re: i860 overview (long)) Message-ID: <1444@thor.acc.stolaf.edu> Date: 10 Mar 89 13:53:54 GMT References: <807@microsoft.UUCP> <92634@sun.uucp> <13322@steinmetz.ge.com> <1133@auspex.UUCP> <12000@haddock.ima.isc.com> Reply-To: mike@thor.UUCP (CP^ZAZPPPYPYXU zQYhBYPYoZO) Followup-To: comp.arch Organization: St. Olaf College; Northfield, MN Lines: 12 In article <12000@haddock.ima.isc.com> suitti@haddock.ima.isc.com (Stephen Uitti) writes: >The whole "duff's >device" bcopy & memcpy discussions of a few months ago are at >least partly based on this idea. I have heard of "Duff's device" in reference to graphics, etc. I am presently trying to write some fast bitblt routines; is Duff's device relevant to this? Can someone send me some information on Duff's device? Please mail, don't post. -- Mike Haertel In Hell they run VMS.