![](https://seccdn.libravatar.org/avatar/dcaea5e8a6fad867936a40a9c21e8ff3.jpg?s=120&d=mm&r=g)
Hi Andrey, Le Wednesday 05 June 2013 à 20:41 +0400, Andrey Borzenkov a écrit :
В Wed, 05 Jun 2013 18:29:53 +0200 Jean Delvare <jdelvare@suse.de> пишет:
* The ACPI button and processor drivers could be built-in. Most x86 systems use ACPI and they supposedly all have at least one processor and one power button ;) And thermal_sys is selected by processor.
I agree for x86. I guess other platforms have different defconfigs anyway?
Only x86 and ia64 have ACPI to start with. I'd be fine leaving thermal_sys as a module on other architectures.
* I have no idea why/how sg is being loaded, it has no modalias and no other module depend on it. But /dev/sd* nodes are created so it is certainly useful. Hannes?
/usr/lib/udev/rules.d/80-drivers.rules:SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST!="[module/sg]", IMPORT{builtin}="kmod load sg"
Thanks for the pointer, that explains it. As I understand it, every system out there has at least one device which will present itself with SUBSYSTEM=="scsi", so the sg module will always be loaded. This normally leads to the driver being built in. Jeff, is that OK with you?
I do not think it is needed much; the practical problem is to make sure it is loaded *when* it is needed (like remote SCSI enclosure monitoring via SES or jukebox control).
If we can't know for sure and thus end up always loading the module, I say it's better built-in. Unless we have another reason not to. Hannes?
* No idea what the scsi_dh* modules are about either, no modalias and no dependencies either. Hannes?
they are related to device-mapper-multipath and not needed on normal end user systems. I wonder why they are loaded; do you have multipath enabled?
It's odd then because no, none of my systems use multipath, they are all dumb laptop/desktop hardware with basic SATA HDD or SSD in them.
* With DRM/KMS being the norm now, I believe drm and drm_kms_helper could be built-in, even though the former is quite large. drm selects i2c-algo-bit, most (all?) DRM/KMS drivers use it. Even servers have graphics chips.
Will it prevent proprietary drivers from working? There are quite a number of users with nVidia/ATI third party drivers. As much as I would like to not use them, nouveau still has fat too much usability issues for me.
This is a good point, I admit I had not considered it, as I have not been using a binary driver since... actually so long I can't even remember. But as I understand it these are really only helper modules, they don't bind to the hardware, so except for the wasted memory I don't think they will cause any problem with proprietary Nvidia or AMD drivers. -- Jean Delvare Suse L3 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org