Hi Seife, Le Wednesday 05 June 2013 à 22:26 +0200, Stefan Seyfried a écrit :
Am 05.06.2013 18:41, schrieb Andrey Borzenkov:
* 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.
And on servers it is very useful to be able to blacklist drm, so that KMS does not kick in. VGA-over-serial emulation and other textmode consoles do not work in graphics mode.
maybe there is some magic parameter to stop drm from kicking in, but "vga=0" no longer helps.
Well, how do you "blacklist drm" exactly? My understanding is that drm is only a common helper module for all drm drivers (radeon, i915 etc.) so a "blacklist drm" statement should have no effect, should it? Also KMS can be disabled with nomodeset=1 or whatever the exact boot command line syntax is these days. If vga=0 no longer works as it used to, maybe this should be reported as a bug.
* I suppose fuse is only used on desktop machines by default, for gvfs, so having it as a module seems OK.
You would not believe how many servers need to mount NTFS file systems :-) ntfs-3g is implemented with FUSE.
Well, if there is a consensus that almost all machines need fuse for one thing or another, I really have no problem having it built into the kernel, if there is no reason not to (KMP, blacklisting or anything else.) Miklos, can you think of any reason why having fuse built into the kernel would be a problem? -- Jean Delvare Suse L3 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org