[src/trunk]: src/usr.bin/config Insert comment regarding PR/48571 so it doesn...

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

details:   https://anonhg.NetBSD.org/src/rev/fd28b730fade
branches:  trunk
changeset: 339979:fd28b730fade
user:      pgoyette <pgoyette%NetBSD.org@localhost>
date:      Wed Aug 19 03:39:45 2015 +0000

description:
Insert comment regarding PR/48571 so it doesn't get lost.

        config(1) ioconf is insufficient for pseudo-devices

config_{init,fini}_component

diffstat:

 usr.bin/config/TODO |  12 ++++++++++++
 1 files changed, 12 insertions(+), 0 deletions(-)

diffs (19 lines):

diff -r d53807ac120f -r fd28b730fade usr.bin/config/TODO
--- a/usr.bin/config/TODO       Wed Aug 19 03:23:34 2015 +0000
+++ b/usr.bin/config/TODO       Wed Aug 19 03:39:45 2015 +0000
@@ -304,3 +304,15 @@
   pseudo attach functions have no choice when to be called.  This could
   be solved by converting to kctors, where functions are called in order
   by dependency.
+
+o Enhance ioconf behavior for pseudo-devices
+
+  See "bin/48571: config(1) ioconf is insufficient for pseudo-devices" for
+  more details.  In a nutshell, it would be "useful" for config to emit
+  the necessary stuff in the generated ioconf.[ch] to enable use of
+  config_{init,fini}_component() for attaching and detaching pseudodev's.
+
+  Currently, you need to manually construct your own data structures, and
+  manually "attach" them, one at a time.  This leads to duplication of
+  code (where multiple drivers contain the same basic logic), and doesn't
+  necessarily handle all of the "frobbing" of the kernel lists.