Strange, that was exactly what I was planning for 2.5 :).
>that would put that string into separate section and making modules_install
<pedantic>
depmod, not modules_install, depmod is run at other times.
</pedantic>
>dump these sections, feed them through s/_NAME_/`basename $module`/ and
kbuild 2.5 does -DKBUILD_OBJECT=module_name for all objects linked into
a module. KBUILD_OBJECT defines the overall module, not the individual
files that make up the module. We have the technology!
>cat them into defaults file that would go into $INSTALL_MOD_PATH.
Just another modules.* file, probably modules.dynamic.conf.
BTW, INSTALL_MOD_PATH is dead in kbuild 2.5, it is a configuration
option and is held in .config.
>MODULES_BLKDEV(), MODULE_LDISC(), etc. would be trivial wrappers around that.
Everything is a device and can be handled by the hotplug project. It
is really a cunning plan by David Brownell and Greg Kroah-Hartman to
own the entire device subsystem ;).
>Looks like the thing you mentioned would make quite a few people happy.
>Might be worth doing in 2.4...
Please, no more 2.4 changes. Let Linus get 2.4 stable, fork 2.5 so we
can break it on a daily basis then backport to 2.4 when it works.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/