NetBSD/riscpc is slightly ambiguous as NetBSD should be
	able to run on or be ported to the Shuttle RiscPC (the only
	mention of which I can find is in the WinNT compatability list)
	http://www.aspsys.com/files/hct/sep94hcl.txt

	However, we already have NetBSD/mipsco supporting early mipsco
	machines and NetBSD/arc supporting the later ones, so I'd
	definitely vote for NetBSD/riscpc :)

		David/absolute		-- www.netbsd.org: No hype required --


On Fri, 6 Apr 2001, Reinoud Zandijk wrote:

> Dear all,
>
> since we are on the virge of splitting off RiscPC/A7000/NC code from the
> now defunct arm32 I am proposing the following :
>  - we get a new name for the port :)
>  - I copy the current arm32 tree, rename it (i.e. make it compile again)
>  - I import/commit the new port name
>  - everyone STOPS working on the arm32 tree but starts working on the new
>    branch
>  - we delete stuff from DNARD etc
>  - we merge RiscPC/A7000/NC into *one* kernel using a machine discriptor
>    structure with #defines or preferable seperate files to allow small
>    kernels
>  - ...
>
> Ideas for the port name include `acorn', `acornriscpc', `armriscpc',
> `riscpcarm', `riscpc' , ....
>
> The name `arch/archimedes' and `arch/imedes' are allready reserved!! :)
>
> Cheers,
> Reinoud
>
>