On 5/12/22 08:17, Christian König wrote: > Am 11.05.22 um 20:36 schrieb Alex Deucher: >> On Wed, May 11, 2022 at 2:20 PM Lyude Paul <lyude@xxxxxxxxxx> wrote: >>> Many DRM drivers feature a 'modeset' argument, which can be used to >>> enable/disable the entire driver (as opposed to passing nomodeset to the >>> kernel, which would disable modesetting globally and make it difficult to >>> load amdgpu afterwards). Apparently amdgpu is actually missing this >>> however, so let's add it! >> You can already do that by passing modprobe.blacklist=amdgpu on the >> kernel command line. I don't think we need another option to do that. > > Yeah, this already came up multiple times and so far we have always > rejected it. > > Stuffing that into drivers is not a good approach I think. If we want to > prevent some device from exposing it's display functionalities we should > rather push that into the drm layer. > Absolutely agree on this. I think what we want is a drm.modeset parameter that would have more precedence than "nomodeset". Because the latter is a built-in parameter and so it can't be disabled at runtime using sysfs. -- Best regards, Javier Martinez Canillas Linux Engineering Red Hat
