ion> Hmm.. not much has changed in terms of dependencies, as far as I can tell.
ion> dev_table.h will make sound.o depend on the chipset-specific drivers which
ion> in turn depend on sound.o. Cyclic dependencies means the modules will
ion> never load.
Those big tables in dev_table.h are structured like this:
/* dev_table.c */
#define _DEV_TABLE_C_
/* dev_table.h */
#ifdef _DEV_TABLE_C_
... table table table table ...
#endif
All that fershlugginer text could be moved out of dev_table.h and into
dev_table.c. I don't see any benefit at all to having it in the .h file.
That would improve the CONFIG_* dependency graph a lot.
ion> More precisely, a sound.o which does not depend on anything and provides
ion> high-level functions only, so it can be loaded separately without causing
ion> any low-level driver to be loaded. It would also provide some sort of
ion> registration functions, so low-level drivers can register themselves
ion> for the specific devices they provide - dsp, midi, mixer.
Sounds reasonable to me.
Regards,
Michael Chastain
<mailto:mec@shout.net>
"love without fear"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu