Module alias and device table support.
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 5 lines · Kai Germaschewski
Alright. I think we're heading towards a generic postprocessor here, which takes the .o, extracts information as necessary and generates some .c file which contains e.g. checksums for the unresolved symbols (when MODVERSIONS is selected), a section to record which modules we depend on, an alias section etc. This .c is then compiled and linked into the final .ko
...
Quoted 5 lines
Yup, I think modversions should have a little time to settle first. There's really only one tricky point with modversions (and the other stuff above), i.e. we need a complete list of all modules. With people playing tricks with "make SUBDIRS=..." that needs some care to not go accidentally wrong.
Worse that "make SUBDIRS=...", what do you think can be done about third party modules? After all, I thought they are what modversions are about. I don't see how you can reliably find the list of required modules when you build a module outside of the kernel tree.
Arnd <><