[src/pgoyette-compat]: src/doc We've already done the compat_80 module stuff, ...

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

details:   https://anonhg.NetBSD.org/src/rev/1c53c3384a9a
branches:  pgoyette-compat
changeset: 830797:1c53c3384a9a
user:      pgoyette <pgoyette%NetBSD.org@localhost>
date:      Thu Sep 27 02:27:05 2018 +0000

description:
We've already done the compat_80 module stuff, so remove it.

The coredump issue was a red-herring, replace it with an entry for
completing and "hooking up" the compat_netbsd32_machdep_13 and _16
stuff

diffstat:

 doc/TODO.compat-module |  22 ++++++++--------------
 1 files changed, 8 insertions(+), 14 deletions(-)

diffs (64 lines):

diff -r 5e1fe9d8a22f -r 1c53c3384a9a doc/TODO.compat-module
--- a/doc/TODO.compat-module    Thu Sep 27 01:35:41 2018 +0000
+++ b/doc/TODO.compat-module    Thu Sep 27 02:27:05 2018 +0000
@@ -1,4 +1,4 @@
-/* $NetBSD: TODO.compat-module,v 1.1.2.12 2018/09/25 21:44:30 pgoyette Exp $ */
+/* $NetBSD: TODO.compat-module,v 1.1.2.13 2018/09/27 02:27:05 pgoyette Exp $ */
 
 DONE
 ----
@@ -60,23 +60,17 @@
 16. The ieee_80211 compat code needs to be verified to make sure it is
     handling the if43_20 compat routine cvtcmd() correctly.
 
-17. There are a few function pointers in netbsd32 module that need to
-    be converted to the new MP-safe mechanism.  See files
-       netbsd32_mod.c
-       netbsd32_module.c
-       netbsd32_compat_80.[ch]
-       amd64's machdep.c and machdep_16.c
-
-18. Need to untangle the machdep COREDUMP stuff.
+17. Need to "hookup" the netbds32_machdep_13 and netbsd32_machdep_16 stuff
+    for amd64 and arm;  probably also need empty stubs for other arch's
 
 
 TODO - Not required for branch merge
 ------------------------------------
-19. Audit the entire code base for any remaining embedded #ifdef's for
+18. Audit the entire code base for any remaining embedded #ifdef's for
     COMPAT_xx.  When found, move the actual compat code into the compat
     hierarchy and replace originals with indirect (vectored) calls.
 
-20. The rtsock compat code is a disaster, with rtsock_50.c #include-ing
+19. The rtsock compat code is a disaster, with rtsock_50.c #include-ing
     the main rtsock.c code with various manipulations of the COMPAT_50
     macro.  Once rtsock is separated, compat_14 references to rtsock_50
     routines needs to be verified.
@@ -86,7 +80,7 @@
     the compat code can be executed, neither on the branch nor on
     HEAD.
 
-21. The compat_60 module still needs some work for XEN systems.  We
+20. The compat_60 module still needs some work for XEN systems.  We
     probably need some build infrastructure changes to ensure that
     XEN (and, for i386, XEN-PAE) modules are build with the correct
     macros defined and with -I directories specified in the same order
@@ -94,7 +88,7 @@
     prevents loading of micro-code updates for amd64 processors running
     XEN kernels.  This limitation also exists on HEAD.
 
-22. There seems to be quite a bit of MD compat_xx code, in the various
+21. There seems to be quite a bit of MD compat_xx code, in the various
     sys/arch/ directories.  I haven't yet looked at any of this.  But it
     seems to me that the MI compat build infrastructure should have some
     mechanism to "reach over" to the MD code, #include a Makefile.inc file,
@@ -112,7 +106,7 @@
     into the monolithic COMPAT module on HEAD.  Thus, its absence from
     any of the version-specific modules is not a regression.
 
-23. For compat_50, in addition to rtsock there are some things in dev/gpio
+22. For compat_50, in addition to rtsock there are some things in dev/gpio
     and dev/wscons/wsmux that I haven't been able to cleanly separate.
     These items are not currently included in the monolithic COMPAT module
     on HEAD, so lack of integration on the branch is not a regression.