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