[src/trunk]: src/usr.bin/config config(1): Note a little more about linkage

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

details:   https://anonhg.NetBSD.org/src/rev/fdd27abaa2ae
branches:  trunk
changeset: 333549:fdd27abaa2ae
user:      uebayasi <uebayasi%NetBSD.org@localhost>
date:      Sat Nov 08 05:57:41 2014 +0000

description:
config(1): Note a little more about linkage

diffstat:

 usr.bin/config/TODO |  14 +++++++++++---
 1 files changed, 11 insertions(+), 3 deletions(-)

diffs (28 lines):

diff -r 0b4fef709b83 -r fdd27abaa2ae usr.bin/config/TODO
--- a/usr.bin/config/TODO       Sat Nov 08 04:23:00 2014 +0000
+++ b/usr.bin/config/TODO       Sat Nov 08 05:57:41 2014 +0000
@@ -192,7 +192,8 @@
   cacheline_aligned) to load address specification for external boot loaders.
 
   Make this into multiple stages to make linkage more structural.  Especially,
-  reserve the final link for purely MD purpose.
+  reserve the final link for purely MD purpose.  Note that in modular build,
+  *.ko are shared between build of kernel and modular(9) modules (*.kmod).
 
        Monolithic build:
                     *.o  ---> netbsd.ko        Generic MI linkage
@@ -227,5 +228,12 @@
   (netbsd.ro) is linked into multiple final kernel image (netbsd) for diferent
   load addresses.
 
-  XXX Modular MI linkage 
-  XXX Modular MD linkage
+  Modular MI linkage is to prepare a module to be loadable as modular(9).  This
+  may add some extra sections and/or symbols.
+
+  Modular MD linkage is again for pure MD purposes like kernel MD linkage.
+  Adjustment and/or optimization may be done.
+
+  Kernel and modular MI linkages may change behavior depending on existence
+  of debug information.  In the future .symtab will be copied using linker
+  during this stage.