Article View: comp.sys.next.misc
Article #4783Re: Info in Open Systems Today ( NeXTSTEP ports!! )
From: David George
Date: Thu, 07 Jan 1993 08:25
Date: Thu, 07 Jan 1993 08:25
20 lines
1369 bytes
1369 bytes
In article <Jan06.153100.46355@yuma.ACNS.ColoState.EDU>, randall@redfish.atmos.colostate.edu (Dave Randall) writes: |> |> > Let's take HP's chip, just for example. It seems to me that there are two |> > ways NeXT could go. (1) They could port Mach/NeXTstep to HP hardware, or |> > (2) they could incorporate an HP cpu into NeXT hardware. |> > |> > Which is more likely? What are the advantages and disadvantages of |> > each? |> > -- |> In order to do (2), you have to do (1). This is not really true. HP hardware is more than just a CPU. By just incorporating the HP chip into the existing NeXT hardware philosophy you save having to port the drivers. You're then left with such jobs as supporting (well) the HP's MMU with such things as its virtual address cache. Luckily Mach already runs on HP harware (I'm reading News with it) so some of the work is already done. David.
Technical Details
Message-ID:
<1993Jan7.082527.8148@osf.org>Path:
arc1-ca.pugleaf.net!sparky!uunet!think.com!paperboy.osf.org!davidReferences:
<C0Ft4n.5BK@hpuerca.atl.hp.com> <Jan06.153100.46355@yuma.ACNS.ColoState.EDU>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.misc Path: arc1-ca.pugleaf.net!sparky!uunet!think.com!paperboy.osf.org!david From: david@postman.gr.osf.org (David George) Subject: Re: Info in Open Systems Today ( NeXTSTEP ports!! ) Message-ID: <1993Jan7.082527.8148@osf.org> Sender: news@osf.org (USENET News System) Organization: OSF RI Grenoble References: <C0Ft4n.5BK@hpuerca.atl.hp.com> <Jan06.153100.46355@yuma.ACNS.ColoState.EDU> Date: Thu, 7 Jan 1993 08:25:27 GMT Lines: 20