Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Withdraw the 36-bit port item. While there's always interest in it

Browse Source 
when the idea comes up on the list, there's also a feeling that
quixotic and/or crazy projects shouldn't be on roadmaps. Which seems
reasonable.
This commit is contained in:
dholland 2017-01-18 18:22:13 +00:00
parent e733120912
commit 03b44d3b7e
1 changed files with 2 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/roadmaps/ports
View File

@ -1,4 +1,4 @@
$NetBSD: ports,v 1.2 2017/01/13 13:40:44 reinoud Exp $
$NetBSD: ports,v 1.3 2017/01/18 18:22:13 dholland Exp $
NetBSD Ports Roadmap
====================
@ -24,7 +24,7 @@ The following elements, projects, and goals are perhaps less pressing;
this doesn't mean one shouldn't work on them but the expected payoff
is perhaps less than for other things:
7. pdp10/risc36/odd-bitsize ports
[none presently]
Explanations
@ -88,19 +88,3 @@ We have some riscv code and a bit of or1k code, but neither is done.
http://cheri-cpu.org
There are a number of reasons to tackle this; it will serve as a code
quality lever. Also there's already a FreeBSD port to steal from.
7. pdp10/risc36/odd-bitsize ports
There's been a fair amount of loose talk over the years about doing a
port to a machine that's got 9-bit bytes, or is word-addressed, or
both. The PDP-10 is one such target; it's also been observed that a
more modern architecture would probably be more likely to allow a
vaguely performant FPGA implementation, and something tentatively
called "risc36" was conceived.
This is both a quixotic retrocomputing project and also a quixotic
code quality project: making the NetBSD code base work on either
word-addressed machines or 9-bit/36-bit machines or both would be good
for it. However, it's also a rather large undertaking.