[src/trunk]: src/doc/roadmaps Restore xhci support. It is not in a release yet.

[dholland <dholland%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/2945b2b5930b
branches:  trunk
changeset: 821059:2945b2b5930b
user:      dholland <dholland%NetBSD.org@localhost>
date:      Sun Jan 22 19:29:38 2017 +0000

description:
Restore xhci support. It is not in a release yet.

diffstat:

 doc/roadmaps/ports |  24 +++++++++++++++---------
 1 files changed, 15 insertions(+), 9 deletions(-)

diffs (70 lines):

diff -r d4473a86bdd0 -r 2945b2b5930b doc/roadmaps/ports
--- a/doc/roadmaps/ports        Sun Jan 22 19:24:51 2017 +0000
+++ b/doc/roadmaps/ports        Sun Jan 22 19:29:38 2017 +0000
@@ -1,4 +1,4 @@
-NetBSD: ports,v 1.3 2017/01/18 18:22:13 dholland Exp $
+$NetBSD: ports,v 1.5 2017/01/22 19:29:38 dholland Exp $
 
 NetBSD Ports Roadmap
 ====================
@@ -10,14 +10,15 @@
 priorities for the project:
 
  1. EFI boot for x86
- 2. Get arm64/aarch64 working
+ 2. xhci support (done and will be in -8)
+ 3. Get arm64/aarch64 working
 
 The following elements, projects, and goals are not strategic
 priorities but are still important undertakings worth doing:
 
- 3. USER_LDT for amd64
- 4. riscv and/or or1k ports
- 5. cheri port
+ 4. USER_LDT for amd64
+ 5. riscv and/or or1k ports
+ 6. cheri port
 
 The following elements, projects, and goals are perhaps less pressing;
 this doesn't mean one shouldn't work on them but the expected payoff
@@ -41,7 +42,12 @@
  - Contact agc for further information.
 
 
- 2. Get arm64/aarch64 working
+ 2. xhci support
+
+xhci is also critical for new x86 hardware. skrll@ says this is done;
+it will be -8.
+
+ 3. Get arm64/aarch64 working
 
 We have some arm64 code but apparently it doesn't really work yet.
 
@@ -50,7 +56,7 @@
  - Contact: ? (XXX)
 
 
- 3. USER_LDT for amd64
+ 4. USER_LDT for amd64
 
 The amd64 port is lacking the USER_LDT bits needed to be able to run
 Wine. Adding these bits does not seem to be a particularly large job
@@ -62,7 +68,7 @@
  - Contact ? (XXX) for further information.
 
 
- 4. riscv and/or or1k ports
+ 5. riscv and/or or1k ports
 
 We have some riscv code and a bit of or1k code, but neither is done.
 
@@ -71,7 +77,7 @@
  - Contact matt@ for further information.
 
 
- 5. cheri port
+ 6. cheri port
 
 http://cheri-cpu.org
 There are a number of reasons to tackle this; it will serve as a code