IMHO, for x86, the kernel cannot assume that the bootloader loadedcertain modules, nor can the bootloader expect that kernel XYZ is in aspecific configuration. They should be agnostic from one another.I think that TRT here is that kernel tells bootloader what to load. This should be possible by allocating a static buffer shared by bootloader/kernel, and kernel does reboot (== calling bootloader).
There are, at least, two non trivial points to solve here:- as said, for x86, you are pushing for an interface that does not yet exist between kernel and bootloader. I highly doubt that Grub/Grub2, syslinux, or any other bootloader not under direct control of TNF, will follow such a model.
- you have to "configure", but also to "unconfigure" device upon each reboot. You have to teach the interface not only "what to load", but also, "what is the state" of a driver module. Module's loading can change the state of devices, and rebooting/calling bootloader will _not_ reset that state.
-- Jean-Yves Migeon jeanyves.migeon%free.fr@localhost