ports revision 1.5 
1$NetBSD: ports,v 1.5 2017/01/22 19:29:38 dholland Exp $
2
3NetBSD Ports Roadmap
4====================
5
6This roadmap covers ports and port-specific issues, and also bus-level
7material even if it's not strictly port-specific.
8
9The following elements, projects, and goals are considered strategic
10priorities for the project:
11
12 1. EFI boot for x86
13 2. xhci support (done and will be in -8)
14 3. Get arm64/aarch64 working
15
16The following elements, projects, and goals are not strategic
17priorities but are still important undertakings worth doing:
18
19 4. USER_LDT for amd64
20 5. riscv and/or or1k ports
21 6. cheri port
22
23The following elements, projects, and goals are perhaps less pressing;
24this doesn't mean one shouldn't work on them but the expected payoff
25is perhaps less than for other things:
26
27 [none presently]
28
29
30Explanations
31============
32
33
34 1. EFI boot for x86
35
36EFI boot is now often required for new x86 hardware. This is
37effectively a mandatory item for -8. Fortunately, nonaka has most of
38it done, though it's not yet committed.
39
40 - As of January 2017 nobody is known to be working on this.
41 - There is currently no clear timeframe or release target.
42 - Contact agc for further information.
43
44
45 2. xhci support
46
47xhci is also critical for new x86 hardware. skrll@ says this is done;
48it will be -8.
49
50 3. Get arm64/aarch64 working
51
52We have some arm64 code but apparently it doesn't really work yet.
53
54 - As of January 2017 nobody is known to be actively working on this.
55 - There is currently no clear timeframe or release target.
56 - Contact: ? (XXX)
57
58
59 4. USER_LDT for amd64
60
61The amd64 port is lacking the USER_LDT bits needed to be able to run
62Wine. Adding these bits does not seem to be a particularly large job
63(and some of the bits are in place already) but it persistently
64doesn't get done. Money's been offered in the past, without result.
65
66 - As of January 2017 nobody is known to be working on this.
67 - There is currently no clear timeframe or release target.
68 - Contact ? (XXX) for further information.
69
70
71 5. riscv and/or or1k ports
72
73We have some riscv code and a bit of or1k code, but neither is done.
74
75 - As of January 2017 nobody is known to be working on this.
76 - There is currently no clear timeframe or release target.
77 - Contact matt@ for further information.
78
79
80 6. cheri port
81
82http://cheri-cpu.org
83There are a number of reasons to tackle this; it will serve as a code
84quality lever. Also there's already a FreeBSD port to steal from.
85