> There is an alternative: Only pick the first two commits (move framebuffer drivers into auto_add_modules) and then drop the framebuffer hook (Debian dropped that hook a long time ago)
There have been moments where I wondered if FRAMEBUFFER=y needs to exist, but I think it's good to keep because:
* It's simpler for consumers.
* It prevents other packages from accidentally pulling in more drivers than they need to (like Plymouth does right now).
* It prevents other packages from having to learn new syntax.
* I don't think there should be a "drm" class because it implies the full set of large DRM drivers that we _don't_ want.
> There is an alternative: Only pick the first two commits (move framebuffer drivers into auto_add_modules) and then drop the framebuffer hook (Debian dropped that hook a long time ago)
There have been moments where I wondered if FRAMEBUFFER=y needs to exist, but I think it's good to keep because:
* It's simpler for consumers.
* It prevents other packages from accidentally pulling in more drivers than they need to (like Plymouth does right now).
* It prevents other packages from having to learn new syntax.
* I don't think there should be a "drm" class because it implies the full set of large DRM drivers that we _don't_ want.