Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!netnews.upenn.edu!msuinfo!kira!dailey From: dailey@kira.uucp (Chris Dailey) Newsgroups: comp.sys.amiga Subject: Re: Idea -- '030 board for 3000 (No, I'm not as confused as I sound :-) Message-ID: <1990Aug16.163645.26072@msuinfo.cl.msu.edu> Date: 16 Aug 90 16:36:45 GMT References: <6812@vax1.acs.udel.EDU> <7727@gollum.twg.com> Sender: news@msuinfo.cl.msu.edu Organization: Michigan State University Lines: 27 In article <7727@gollum.twg.com> david@twg.com (David S. Herron) writes: >In article <6812@vax1.acs.udel.EDU> don@vax1.udel.edu () writes: >>the '030 that's already there to work in conjunction with whatever's on the >>accelerator, you could have a 33, 40, or 50 MHz '030 & optional '882 of similar >>speed running with the 25 MHz handling some of the menial i/o type tasks. >naaaaahh... >don't leave it to the menial i/o tasks ... >make Amiga DOS a fully multi-processing OS ... that is, let both processors >run processes ... >I mean, after all, that's probably the next `neat' thing that >the Apple people will try to invent. So therefore the Amiga >needs to Blaze This Trail! Multiple processors bring up many other problems. For one, what about memory access? If each processor eats up bandwidth, that would only allow each processor to access memory when the other can't. If you had two totally separate memory areas, then that would make graphics stuff hard. To sum up, HEADACHES! ><- David Herron, an MMDF weenie, ><- Formerly: David Herron -- NonResident E-Mail Hack ><- Sign me up for one "I survived Jaka's Story" T-shirt! -- /~\ Chris Dailey (CPS Undergrad, SOC Lab Coord, AMIG user group Secretary) C oo dailey@(cpsin1.cps|frith.egr).msu.edu (make WP5.1 for the Amiga) _( ^) "I am thankful for one leg. To limp is no disgrace -- / ~\ I may not be number one, but I can still run the race." -from B.C.