On Wed, Feb 02, 2022 at 12:39:29PM +0100, Javier Martinez Canillas wrote:

On 2/2/22 12:06, Andy Shevchenko wrote:

quoted

On Wed, Feb 02, 2022 at 09:38:51AM +0100, Javier Martinez Canillas wrote:

quoted

On 2/1/22 21:40, Sam Ravnborg wrote:

quoted

And how will distros choose "the right" option in this case?

It depends on the distro. In Fedora we are disabling *all* the fbdev drivers.

Yes, and Distro A will think about old driver (because they have customers and
don't want to have a bad user experience) and Distro F will choose a new one.

quoted

What to do when I wan to see a regression and I want to change drivers w/o
recompilation?

If you want to have the two drivers without recompilation (and same compatible
to match) then how would kmod / udev choose which one to load ? It becomes a
race condition between the two drivers which one probes first.

We have a long history in kernel where new drivers came and old faded.
When two or more drivers of the same feature is enabled in the kernel
we may use modprobe facilities to prioritize them (blacklisting).

quoted

NAK from me to that proposal.

What's your suggestion then to solve the issue mentioned above ? With my distro
maintainer hat I don't care that much, since the fbdev drivers will be disabled.

I think both of them can work together. If user doesn't care, the first one wins.

-- 
With Best Regards,
Andy Shevchenko