Hi,
I was too hurry reply to you. I'm may miss the point for part of your
reviews, Sorry.
On 2023/7/20 03:32, Bjorn Helgaas wrote:
CONFIG_DRM_AST is a tristate. We're talking about identifying the
boot-time console device.
Yes, my patch will only works *after* the module gets loaded successfully.
But generally, vgaarb will select a default boot device before my patch taking into effect.
I means that vgaarb will select a default boot device by calling vga_arbiter_add_pci_device() function.
In practice, I still not notice any obvious problems.
I'm lack the knowledge about the boot-time console,
what is the potential problems with such a condition?
So if CONFIG_DRM_AST=m, I guess we don't
get the benefit of the new callback unless the module gets loaded?
Yes, my approach will not works until the device driver kernel module
gets loaded successfully.
So what's the problem with such a situation, do you see something weird ?
