> See above that is *not* the proper interface for implementation choice,
> which is *user* policy anyway and can be handled fine by the
> existing generic module interface infrastructure.
> For the sake of modularization. I have already at home a version
> of ide-pci.c, where the signatures of chipset initialization
> source code modules match the singature of a normal pci device
> initialization hook. This should enable it to make them true modules
If you can, please send this to me - I'd like to take a look.
> The chipset drivers will register lists of PCI-id's they can handle
> instead of the single only global list found in ide-pci.c.
I think it'd be even better if the chipset drivers did the probing
themselves, and once they find the IDE device, they can register it with
the IDE core. Same as all the other subsystem do this.
-- Vojtech Pavlik SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/