Correct, except for, where is this mythical list of all the modules that are needed?technosaurus wrote:If you need to load kernel modules during init, the kernel is configured wrong. Just change tne CONFIG_XXXX=M to =Y for everything referenced in init - there should be no modules in the initramfs/initrd.gyro wrote:One of the aims of the rewrite is to get the sfs files loaded so that the "initmodules" facility can "insmod" any keyboard required modules before the keyboard is needed.
My keyboard works with 666philb's kernels, but not with 01micko's. (not a big deal for me, since I then use "initmodules", with a 01micko kernel.)
666philb used to have a problem with a particular USB port, that required a module, (fixed in his kernels now.)
The end result is a kernel that conatins everything that looks slightly like it might be needed.
But stiil, at any time someone can start using new hardware that is only supported with a new kernel module, thus making all existing kernels obselete.
And until the new kernel's are available, the user has the "no keyboard during init" problem.
Edit:
Making the "huge-kernel" modules available during "init", we can do.
The remaining problem is; how do we sort out what is the minimal set of modules that need to be loaded to enable the keyboard?
The only current solution is "intmodules".
gyro