head	1.1;
access;
symbols
	perseant-exfatfs-base-20250801:1.1
	perseant-exfatfs-base-20240630:1.1
	perseant-exfatfs:1.1.0.8
	perseant-exfatfs-base:1.1
	cjep_sun2x:1.1.0.6
	cjep_sun2x-base:1.1
	cjep_staticlib_x-base1:1.1
	cjep_staticlib_x:1.1.0.4
	cjep_staticlib_x-base:1.1
	phil-wifi-20200421:1.1
	phil-wifi-20200411:1.1
	phil-wifi-20200406:1.1
	pgoyette-compat-merge-20190127:1.1.2.25
	pgoyette-compat-20190127:1.1
	pgoyette-compat-20190118:1.1
	pgoyette-compat-1226:1.1
	pgoyette-compat-1126:1.1
	pgoyette-compat-1020:1.1
	pgoyette-compat-0930:1.1
	pgoyette-compat-0906:1.1
	pgoyette-compat-0728:1.1
	pgoyette-compat-0625:1.1
	pgoyette-compat-0521:1.1
	pgoyette-compat-0502:1.1
	pgoyette-compat-0422:1.1
	pgoyette-compat-0415:1.1
	pgoyette-compat-0407:1.1
	pgoyette-compat-0330:1.1
	pgoyette-compat-0322:1.1
	pgoyette-compat-0315:1.1
	pgoyette-compat:1.1.0.2;
locks; strict;
comment	@# @;


1.1
date	2018.03.10.05.14.26;	author pgoyette;	state dead;
branches
	1.1.2.1;
next	;
commitid	hfnEcmdMTqTJ0StA;

1.1.2.1
date	2018.03.10.05.14.26;	author pgoyette;	state Exp;
branches;
next	1.1.2.2;
commitid	hfnEcmdMTqTJ0StA;

1.1.2.2
date	2018.03.11.09.34.59;	author pgoyette;	state Exp;
branches;
next	1.1.2.3;
commitid	icRZbO5Uhs36q1uA;

1.1.2.3
date	2018.03.12.01.59.31;	author pgoyette;	state Exp;
branches;
next	1.1.2.4;
commitid	uagabRYrUCftR6uA;

1.1.2.4
date	2018.03.12.02.03.20;	author pgoyette;	state Exp;
branches;
next	1.1.2.5;
commitid	ZQ3CL4RxsRq8T6uA;

1.1.2.5
date	2018.03.24.03.04.48;	author pgoyette;	state Exp;
branches;
next	1.1.2.6;
commitid	Km5KvZP9rfioQEvA;

1.1.2.6
date	2018.03.25.08.52.54;	author pgoyette;	state Exp;
branches;
next	1.1.2.7;
commitid	BeSbAqZvavgLJOvA;

1.1.2.7
date	2018.03.25.23.53.51;	author pgoyette;	state Exp;
branches;
next	1.1.2.8;
commitid	iGUYQFfzdBSGITvA;

1.1.2.8
date	2018.03.28.03.41.26;	author pgoyette;	state Exp;
branches;
next	1.1.2.9;
commitid	hI8J2kcz2oDXUawA;

1.1.2.9
date	2018.04.03.08.29.44;	author pgoyette;	state Exp;
branches;
next	1.1.2.10;
commitid	PAsB0fzd8Y7XiYwA;

1.1.2.10
date	2018.04.16.09.53.02;	author pgoyette;	state Exp;
branches;
next	1.1.2.11;
commitid	58toJcW49BIwmEyA;

1.1.2.11
date	2018.04.17.06.20.26;	author pgoyette;	state Exp;
branches;
next	1.1.2.12;
commitid	Wok12xnaFl3G9LyA;

1.1.2.12
date	2018.04.17.23.06.11;	author pgoyette;	state Exp;
branches;
next	1.1.2.13;
commitid	40p0l1cBuTKwIQyA;

1.1.2.13
date	2018.04.18.00.04.11;	author pgoyette;	state Exp;
branches;
next	1.1.2.14;
commitid	PqJ17du5fu2B2RyA;

1.1.2.14
date	2018.04.18.01.39.14;	author pgoyette;	state Exp;
branches;
next	1.1.2.15;
commitid	yt7vFnrr0Ci8zRyA;

1.1.2.15
date	2018.04.26.01.58.25;	author pgoyette;	state Exp;
branches;
next	1.1.2.16;
commitid	BzmrPSBAJtcBpTzA;

1.1.2.16
date	2018.05.26.03.12.34;	author pgoyette;	state Exp;
branches;
next	1.1.2.17;
commitid	eJj97FOBN6adRKDA;

1.1.2.17
date	2018.05.26.11.48.40;	author pgoyette;	state Exp;
branches;
next	1.1.2.18;
commitid	T2w9hyd2ixLvINDA;

1.1.2.18
date	2018.08.25.01.02.48;	author pgoyette;	state Exp;
branches;
next	1.1.2.19;
commitid	QU5bdab2lL1ldrPA;

1.1.2.19
date	2018.08.25.23.12.23;	author pgoyette;	state Exp;
branches;
next	1.1.2.20;
commitid	WsDNpW25JXoHzyPA;

1.1.2.20
date	2018.09.04.02.24.03;	author pgoyette;	state Exp;
branches;
next	1.1.2.21;
commitid	5YwQjAatPfbylJQA;

1.1.2.21
date	2018.09.04.11.36.06;	author pgoyette;	state Exp;
branches;
next	1.1.2.22;
commitid	bp62zD90oFaUoMQA;

1.1.2.22
date	2018.09.06.08.22.10;	author pgoyette;	state Exp;
branches;
next	1.1.2.23;
commitid	GXdzchBJWgolg1RA;

1.1.2.23
date	2018.09.07.23.32.29;	author pgoyette;	state Exp;
branches;
next	1.1.2.24;
commitid	J2oTAHVc1v7mgeRA;

1.1.2.24
date	2018.09.08.23.39.21;	author pgoyette;	state Exp;
branches;
next	1.1.2.25;
commitid	LrkAOeE7XJvXgmRA;

1.1.2.25
date	2018.09.09.02.20.17;	author pgoyette;	state dead;
branches;
next	;
commitid	iWaNTNKjDx0aanRA;


desc
@@


1.1
log
@file COMPAT-branch-notes was initially added on branch pgoyette-compat.
@
text
@@


1.1.2.1
log
@Add some notes on what has been done, and what remains
@
text
@a0 45
DONE
----
1. Removed linking of the kernel compat object library into all kernels;
   using the .o library caused some build breakage, and resulted in the
   bulk of the compat code being included in every kernel, but without
   any module linkage.  In turn, this caused failure when loading some
   modules due to symbols already being defined in the kernel.

2. Reverted some intentional breakage for loading the sysv_ipc module;
   the breakage was introduced as the fix for the above-mentioned build
   breakage.  

3. Split the sysv_ipc compat routines into their own compat_sysv module.

4. Resolved some inter-module dependencies.

5. Extracted some net/if.c compat routines into the compat module, and
   replaced the originals with indirect (vectored) function calls.


TODO
----
1. 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.

   (There are several instances of this in the net routing table code.)

2. Implement a mechanism for modules to include "aliases".  This would
   allow a single module file to contain multiple module table entries
   (for example, a single file for the compat module could include
   compat_80, compat_70, compat_60, ...).  Then, other modules could
   depend on individual names.  For example, module compat_xyz could
   depend on compat_70, and the dependency would be met by either the
   "everything" compat module (with all of its aliases) or by a 7.0-
   specific module.

   Note that in addition to updating the module code, this would also
   require changes to syscalls.master files to change the names of the
   modules associated with module-provided syscalls.

3. In addition to the single, all-encompassing compat module, provide a
   per-version compat_xx module, each with dependencies on all higher
   versions.  (Perhaps we would also do this for the sysv ipc module,
   although the gains are a lot smaller.)
@


1.1.2.2
log
@Don't forget about validating/correcting compat module dependencies
@
text
@a45 4

4. Reconfirm all compat-module dependencies, and update the files *
   def lines as needed, to insure that built-in dependencies get
   resolved.
@


1.1.2.3
log
@Update dependencies for modules when they are built-in.  Now we don't
(or at least, shouldn't) need reminders in the GENERIC config files
about which module options require other options.

Update branch status doc accordingly.
@
text
@a19 10
6. Implemented a mechanism for modules to include "aliases", allowing
   a single module file to declare multiple names.  For example, a
   single "compat" module could declare compat_80, compat_70, etc, and
   other modules could depend on specific compat levels rather than on
   the entirety of compat.

7. Reconfirmed all compat-module dependencies, and update the files *
   def lines as needed, to insure that built-in dependencies get
   resolved.

d38 8
a45 5
2. Using the alias mechanism, split compat (and perhaps compat_sysv)
   into multiple version-specific modules.  Note that in addition to
   updating the module code, this would also require changes to
   syscalls.master files to change the names of the modules associated
   with module-provided syscalls.
d47 3
@


1.1.2.4
log
@Remove "alias" entry from the To-Do list - it's already in the Done pile.
@
text
@d39 9
@


1.1.2.5
log
@Reflect current status
@
text
@d26 3
a28 3
7. Reconfirmed existing compat-module dependencies, and update the
   defopt/defflag lines in the config files* as needed, to insure that
   built-in dependencies get resolved.
d37 2
a44 5
   Update:  These are being done simultaneously, with compat code being
   moved directly to a version-specific module.  All of COMPAT_80 and
   COMPAT_70, most of COMPAT_60, and much of COMPAT_50 are finished.
   Need to decide how to handle the COMPAT_BSDPTY stuff.

@


1.1.2.6
log
@Add reminder to deal with XEN for compat_60 cpu_ucode stuff
@
text
@a47 1
3. XXX The compat_60 module still needs some work for XEN systems.
@


1.1.2.7
log
@Another reminder, to update syscalls.master and other modules to refer
to specific compat_xx modules rather than the monolithic compat module.
@
text
@a48 4

4. Update syscalls.master to point the compat calls at the specific
   modules rather than the monolithic compat module.  Update the
   "required" lists of other modules, too.
@


1.1.2.8
log
@Add some reminders
@
text
@d46 1
a46 4
   Still need to decide how to handle the COMPAT_BSDPTY stuff.

   COMPAT_40 is also finished, except for some arch/sh3 MD code.  There
   is also some arch/m68k MD-specific code remaining for COMPAT_50.
@


1.1.2.9
log
@Remove fixed allocation of modules' "required" lists (previously
limited to MAXMODDEPS entries).  Update the modctl(MODCTL_STAT)
syscall to return the required data in a new format, and retain
the previous data format in MODCTL_OSTAT.  Update the compat_80
and compat_netbsd32 modules as needed.
@
text
@a29 5
8. Fixed limits on the number of module depedencies and maximum
   recursion level have been removed.  Previous code for reporting
   module status to userland has been versioned and moved to the
   compat_80 module.

@


1.1.2.10
log
@Update with notes from a recent status update e-mail sent to tech-kern
@
text
@d3 31
a33 31
1.  Removed linking of the kernel compat object library into all kernels;
    using the .o library caused some build breakage, and resulted in the
    bulk of the compat code being included in every kernel, but without
    any module linkage.  In turn, this caused failure when loading some
    modules due to symbols already being defined in the kernel.

2.  Reverted some intentional breakage for loading the sysv_ipc module;
    the breakage was introduced as the fix for the above-mentioned build
    breakage.  

3.  Split the sysv_ipc compat routines into their own compat_sysv module.

4.  Resolved some inter-module dependencies.

5.  Extracted some net/if.c compat routines into the compat module, and
    replaced the originals with indirect (vectored) function calls.

6.  Implemented a mechanism for modules to include "aliases", allowing
    a single module file to declare multiple names.  For example, a
    single "compat" module could declare compat_80, compat_70, etc, and
    other modules could depend on specific compat levels rather than on
    the entirety of compat.

7.  Reconfirmed existing compat-module dependencies, and update the
    defopt/defflag lines in the config files* as needed, to insure that
    built-in dependencies get resolved.

8.  Fixed limits on the number of module depedencies and maximum
    recursion level have been removed.  Previous code for reporting
    module status to userland has been versioned and moved to the
    compat_80 module.
d38 23
a60 77
1.  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.

2.  Using the alias mechanism, split compat (and perhaps compat_sysv)
    into multiple version-specific modules.  Note that in addition to
    updating the module code, this would also require changes to
    syscalls.master files to change the names of the modules associated
    with module-provided syscalls.

    Update:  These are being done simultaneously, with compat code being
    moved directly to a version-specific module.  All of COMPAT_80 and
    COMPAT_70, most of COMPAT_60, and much of COMPAT_50 are finished.
    Still need to decide how to handle the COMPAT_BSDPTY stuff.

    COMPAT_40 is also finished, except for some arch/sh3 MD code.  There
    is also some arch/m68k MD-specific code remaining for COMPAT_50.

3.  XXX The compat_60 module still needs some work for XEN systems.

4.  Update syscalls.master to point the compat calls at the specific
    modules rather than the monolithic compat module.  Update the
    "required" lists of other modules, too.

5.  The rtsock compatability code needs to be de-spaghetti'd and made
    separable into rtsock_70 and rtsock_50 pieces.

6.  Once rtsock is separated, compat_14 references to rtsock_50 routines
    needs to be verified.

7.  For compat_60, still need to figure out what to do with BSDPTY and
    tty_ptm

8.  Also for compat_60, need to fix the building of XEN (and, for i386,
    XEN-PAE) module variants so that the obj-dir symlinks and the -I
    include order match those present in a kernel build.  See PR/53130
    (Currently, this affects the compat_60 module and its implementation
    of microcode updates for AMD processors - i386 and amd64.)

9.  For compat_50, in addition to rtsock there are some things in dev/vnd,
    dev/gpio, and dev/wscons/wsmux that I haven't been able to cleanly
    separate.

10. In addition to the ttcompat code in compat_60, there is another
    ttcompat in compat_43.  The 60 code used to simply update the function
    pointer, but the 43 code uses a rw_lock to protect the pointer update.
    Additionally, the 43 code specifically checks to ensure that the
    initial value of the pointer in NULL before updating it, which would
    prevent the 43 code from working if the 60 code is already loaded.  (I
    have some XXX comment in my branch code for this.)

    I suspect that the right this to do here is probably to make _two_
    indirect function calls in the main tty code, use separate pointers
    for the 60 and 43 compat stuff, and remove the rw_lock stuff.

11. There's a vfs sysctl call that currently is build under COMPAT_09 ||
    COMPAT_43.  I don't understand enough of unix history to figure out if
    this really belongs to both compat_xx modules (which would require
    building a separate module, required by both) or if it belongs to a
    specific module.

    (This is based on a statement that mrg@@ made in IRC, which basically
    said that compat_43 is not as much about maintaining binary
    compatability  as it is about maintaining old interfaces.  Thus it
    does _not_ depend on any of the "newer" compat code.  So, compat_43
    would be able to be loaded on its own, or in combination with any of
    the other compat modules.)

12. 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,
    and perhaps define something to enable the MI modcmd code to call a
    compat_xx_MD_init() routine.



@


1.1.2.11
log
@More updates to match reality.
@
text
@a34 8
9.  The old monolithic compat module has been broken into multiple
    modules, one for each old NetBSD version.  The monolithic module
    is still available, and uses the alias mechanism to "advertise"
    that the component modules are available.

    There are still several areas which are not complete - see the
    TODO list below for more details.

d42 10
a51 2
2.  Similar to the monolithic netbsd module, split the compat_sysv
    module into multiple version-specific modules.
d53 2
a54 2
3.  Update syscalls.master to reflect that modular syscalls are now
    provided by version-specific modules.
d56 1
a56 9
4.  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.

5.  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
    as for building kernels.
d58 1
a58 1
6.  Update syscalls.master to point the compat calls at the specific
d62 1
a62 1
7.  The rtsock compatability code needs to be de-spaghetti'd and made
d65 1
a65 1
8.  Once rtsock is separated, compat_14 references to rtsock_50 routines
d68 1
a68 1
9.  For compat_60, still need to figure out what to do with BSDPTY and
d71 1
a71 1
10. Also for compat_60, need to fix the building of XEN (and, for i386,
d77 1
a77 1
11. For compat_50, in addition to rtsock there are some things in dev/vnd,
d81 25
d113 2
@


1.1.2.12
log
@Split the compat_sysv module into several version-specific modules,
similar to the compat module.
@
text
@a39 3
    Similarly, the compat_sysv module has also been split into several
    version-specific modules.

d50 4
a53 1
2.  Update syscalls.master to reflect that modular syscalls are now
d56 1
a56 1
3.  The rtsock compat code is a disaster, with rtsock_50.c #include-ing
d60 1
a60 1
4.  The compat_60 module still needs some work for XEN systems.  We
d66 1
a66 1
5.  Update syscalls.master to point the compat calls at the specific
d70 1
a70 1
6.  The rtsock compatability code needs to be de-spaghetti'd and made
d76 1
a76 1
8.  For compat_60, still need to figure out what to do with BSDPTY and
d79 1
a79 1
9.  Also for compat_60, need to fix the building of XEN (and, for i386,
d85 1
a85 1
10. For compat_50, in addition to rtsock there are some things in dev/vnd,
d89 1
a89 1
11. There seems to be quite a bit of MD compat_xx code, in the various
@


1.1.2.13
log
@Note changes to syscalls.master and friends
@
text
@a45 3
10. syscalls.master has been updated to autoload the version-specific
    compat modules rather than the monolithic modules.

d53 4
a56 1
2.  The rtsock compat code is a disaster, with rtsock_50.c #include-ing
d60 1
a60 1
3.  The compat_60 module still needs some work for XEN systems.  We
d66 1
a66 1
4.  Update syscalls.master to point the compat calls at the specific
d70 1
a70 1
5.  The rtsock compatability code needs to be de-spaghetti'd and made
d73 1
a73 1
6.  Once rtsock is separated, compat_14 references to rtsock_50 routines
d76 1
a76 1
7.  For compat_60, still need to figure out what to do with BSDPTY and
d79 1
a79 1
8.  Also for compat_60, need to fix the building of XEN (and, for i386,
d85 1
a85 1
9.  For compat_50, in addition to rtsock there are some things in dev/vnd,
d89 1
a89 1
10. There seems to be quite a bit of MD compat_xx code, in the various
@


1.1.2.14
log
@Note current lack of implementation for syscall #148 - pre-5.0 quotactl()
@
text
@a95 2
11. Note that pre-5.0 quotactl (syscall #148) is not currently available.
    Its entry in syscalls.master is XXXd out.
@


1.1.2.15
log
@Remove note about syscall #148 (old quotactl) - it was wrong.

Add comment about there being some few platforms with MD COMPAT_44
code in their machdep.c files.
@
text
@d96 2
a97 7
    Note also that there are a few bits of MD code that is COMPAT_44
    related.  The only bit of MI COMPAT_44 code is in the single module
    shared by COMPAT_43 and COMPAT_09.  This affects the cesfic, hp300,
    news68k, and x68k platforms, all in their respective machdep.c
    source file.  Additionally, the zaurus platform defines COMPAT_44 in
    its INSTALL kernel configuration - but no other configuration files!

@


1.1.2.16
log
@Remove a To-Do entry that is already done (re-pointing the MODULAR
sys-calls at their individual module).

Merge the multiple entries concerning rtsock compat code.  It really
is a mess, but we don't need to say so three times!
@
text
@d58 1
a58 2
    macro.  Once rtsock is separated, compat_14 references to rtsock_50
    routines needs to be verified.
d66 11
a76 1
4.  For compat_60, still need to figure out what to do with BSDPTY and
d79 1
a79 1
5.  Also for compat_60, need to fix the building of XEN (and, for i386,
d85 1
a85 1
6.  For compat_50, in addition to rtsock there are some things in dev/vnd,
d89 1
a89 1
7.  There seems to be quite a bit of MD compat_xx code, in the various
@


1.1.2.17
log
@Add a $NetBSD$ line to track revision/changes
@
text
@a0 2
/* $NetBSD$ */

@


1.1.2.18
log
@Separate the TODO list into two lists, required-for-merge vs not-required.

Expand a couple entries.
@
text
@d1 1
a1 1
/* $NetBSD: COMPAT-branch-notes,v 1.1.2.17 2018/05/26 11:48:40 pgoyette Exp $ */
d52 2
a53 17
TODO - Required for branch merge
--------------------------------
1.  For compat_60, still need to figure out what to do with BSDPTY and
    tty_ptm

2.  Also for compat_60, need to fix the building of XEN (and, for i386,
    XEN-PAE) module variants so that the obj-dir symlinks and the -I
    include order match those present in a kernel build.  See PR/53130
    (Currently, this affects the compat_60 module and its implementation
    of microcode updates for AMD processors - i386 and amd64.)

3.  For compat_50, in addition to rtsock there are some things in dev/vnd,
    dev/gpio, and dev/wscons/wsmux that I haven't been able to cleanly
    separate.

TODO - Not required for branch merge
------------------------------------
a62 3
    Currently, this entire code is built for the monolithic COMPAT
    module, but there's no way to reach the entry points.

d69 12
a80 1
    This currently affects cpu microcode loading for amd64 XEN systems.
d82 1
a82 1
4.  There seems to be quite a bit of MD compat_xx code, in the various
@


1.1.2.19
log
@Remove duplicate entry for XEN module build infrastructure.
@
text
@d1 1
a1 1
/* $NetBSD: COMPAT-branch-notes,v 1.1.2.18 2018/08/25 01:02:48 pgoyette Exp $ */
d57 7
a63 1
2.  For compat_50, in addition to rtsock there are some things in dev/vnd,
d85 3
a87 1
    as for building kernels. See PR port-xen/53130.
@


1.1.2.20
log
@Note that COMPAT_BSDPTY task is done.
@
text
@d1 1
a1 1
/* $NetBSD: COMPAT-branch-notes,v 1.1.2.19 2018/08/25 23:12:23 pgoyette Exp $ */
d54 4
a57 1
1.  For compat_50, in addition to rtsock there are some things in dev/vnd,
a94 3
5.  Separated COMPAT_BSDPTY stuff, allowing the COMPAT_60 module to be
    built regardless.

@


1.1.2.21
log
@Put the COMPAT_BSDPTY entry in the proper group (ie, the "done" group).
@
text
@d1 1
a1 1
/* $NetBSD: COMPAT-branch-notes,v 1.1.2.20 2018/09/04 02:24:03 pgoyette Exp $ */
a50 3
11. Separated COMPAT_BSDPTY stuff, allowing the COMPAT_60 module to be
    built regardless.

d92 3
@


1.1.2.22
log
@Update some entries to reflect why they're not needed before merging
the branch back to mainline.
@
text
@d1 1
a1 1
/* $NetBSD: COMPAT-branch-notes,v 1.1.2.21 2018/09/04 11:36:06 pgoyette Exp $ */
d43 4
a46 2
    version-specific modules.  (A mini-monolithic compat_sysv module
    is still provided.)
d57 3
a59 2
none

d73 1
a73 3
    module, but there's no way to reach the entry points, so none of
    the compat code can be executed, neither on the branch nor on
    HEAD.
d79 1
a79 3
    as for building kernels. See PR port-xen/53130.  This currently
    prevents loading of micro-code updates for amd64 processors running
    XEN kernels.  This limitation also exists on HEAD.
d89 2
a90 2
    related.  (The only bit of MI COMPAT_44 code is in the single module
    shared by COMPAT_43 and COMPAT_09.)  This affects the cesfic, hp300,
a94 10
    As far as I can tell, none of the MD compat code is currently built
    into the monolithic COMPAT module on HEAD.  Thus, its absence from
    any of the version-specific modules is not a regression.

5.  For compat_50, in addition to rtsock there are some things in dev/vnd,
    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.

@


1.1.2.23
log
@At the request of reviewers, remove the module alias functionality.

We will rely only on module names and duplicate-symbol detection to
detect module conflicts.
@
text
@d1 1
a1 1
/* $NetBSD: COMPAT-branch-notes,v 1.1.2.22 2018/09/06 08:22:10 pgoyette Exp $ */
d5 9
a13 10
1.  Returned the build to use a .a compat library rather than a .o
    library.  The original method used was .a but that was changed
    (fairly recently) as a work-around to address some support
    routines that were not being included when needed.  These support
    modules are now included in their own module, and the work-around
    is therefore no longer needed.

2.  Reverted some intentional auto-load breakage for loading the sysv_ipc
    module; the breakage was introduced as the fix for the above-mentioned
    build breakage.  
d22 7
a28 1
6.  Reconfirmed existing compat-module dependencies, and update the
d32 1
a32 1
7.  Fixed limits on the number of module depedencies and maximum
d37 1
a37 1
8.  The old monolithic compat module has been broken into multiple
d39 2
a40 1
    is still available.
d43 2
a44 2
    version-specific modules, and the mini-monolithic compat_sysv module
    is still provided.
d46 1
a46 1
9.  syscalls.master has been updated to autoload the version-specific
d49 1
a49 1
10. Separated COMPAT_BSDPTY stuff, allowing the COMPAT_60 module to be
@


1.1.2.24
log
@Add a note regarding possible future investigation of the .a vs .o
compat library mechanisms.
@
text
@d1 1
a1 1
/* $NetBSD: COMPAT-branch-notes,v 1.1.2.23 2018/09/07 23:32:29 pgoyette Exp $ */
a99 4
6.  Even though the build mechanism has been switched back to using a
    .a compat library, it might be useful to make it work with the .o
    library.

@


1.1.2.25
log
@Rename COMPAT-branch-notes to TODO.compat-module
@
text
@d1 1
a1 1
/* $NetBSD: COMPAT-branch-notes,v 1.1.2.24 2018/09/08 23:39:21 pgoyette Exp $ */
@