what about saving the parameters for successfully loaded modules?
(like the IRQs and other stuff which gets autodetected.)
- and when those modules are loaded for the second time, the
saves values will be used, without the need to do
autoprobing (don't know how much time that will
save, but it should save quite some time for people
having all the drivers in the kernel, but no matching
hardware)
- this will only work if there are no static inits,
but everything's modularized (which should
be in the works?)
- also you need to have a parameter to reprobe the whole modules
- this would also give a nice template for building a customized kernel
(well again for people who are not really used to do things like that)
just my $0.02
tm
-- in some way i do, and in some way i don't.- 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/