-
Martin Dalecki authored
1. Kill the ide-probe-mod by merging it with ide-mod. There is *really* no reaons for having this stuff split up into two different modules unless you wan't to create artificial module dependancies and waste space of page boundaries during memmory allocation for the modules 2. Kill the ide_module_t - which is unnecessary and presents a "reimplementation" of module handling inside the ide driver. This is achieved by attaching the initialization routine ot the ide_driver_t, which will be gone next time, since there is no sane reason apparently, which this couldn't be done during the module-generic initialization of the corresponding driver module. 3. Kill unnecessary tagging of "subdriver" with IDE_SUBDRIVER_VERSION - we have plenty of other mechanisms for module consistency checking. And anyway the ide code didn't any consistence checks on this value at all. NOTE: The ide_(un)register_module() functions will be killed in next round.
69f0d4b0