-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oddball wrote:
Jeff Mahoney schreef:
The kernel doesn't look for e.g. a new video card - it goes down the busses, enumerates what's there, and issues events to userspace to load the appropriate drivers for that hardware. The boot process only loads drivers for common hardware for which there isn't any autodiscovery, like cpufreq. If it travels the busses, it should find minipciewifi card, how exactly can it be 'un'-ignored?
I'm not sure what you mean here. Are you asking about your original wifi problem? If that's the case, there was nothing you could have done short of rebuilding your own kernel with CONFIG_STAGING=y, CONFIG_EXCLUDE_STAGING_FROM_BUILD=n, and enabling the wifi driver in there. That's the change I committed earlier today, so once the KOTD kernels are building again, it will automatically discover it on boot.
That said, for a truly minimal system like Jan mentioned with JeOS, that's not what you want either. There are core modules that will nearly always be used like TCP/IP, the SCSI layer, etc, but some of the more esoteric devices and protocol could probably be split out into smaller packages that can be uninstalled easily. why not?
Mostly just that there aren't enough hours in the day to get everything done. Hopefully the new kernel spec files are easier to work with than they have in the past. If you have an idea of how you'd like it to look, give it a try and post your results here. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAknWWSAACgkQLPWxlyuTD7IVWgCfe3eVKW3z83b3H/nObKkqsLrl H7MAni7RUEooflfo/D5Tg/vabSoc1CIT =DCiD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org