Thread (31 messages) 31 messages, 2 authors, 2022-07-15

Re: [PATCH 02/11] fbdev/vga16fb: Create EGA/VGA devices in sysfb code

From: Javier Martinez Canillas <javierm@redhat.com>
Date: 2022-07-11 10:50:42
Also in: dri-devel, linux-staging

On 7/11/22 12:42, Thomas Zimmermann wrote:
Hi Javier
[...]
quoted
That's why I think that "vga-framebuffer" as driver name would be misleading.
Specially since it would also bind to the "ega-framebuffer" platform device.
I messed up device and driver name, such that misunderstood your remark.

As we use the id_table field for matching devices, the driver name 
doesn't matter. [1] So let's keep the driver name as vga16fb. The change 
above must have been left over from an earlier prototype patch, I guess.
Agreed. The driver name is used as the last resort to match a device
only if there isn't any device ID table (ACPI, OF, platform, etc) but
that's discouraged. Specially when the same driver supports different
devices as it's the case for this driver.

-- 
Best regards,

Javier Martinez Canillas
Linux Engineering
Red Hat
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help