Hi, On 08/27/2014 02:44 PM, jonsmirl@xxxxxxxxx wrote: <snip> >> 1) Serving as *the* fb until a kms driver is present > > Why can't we whip together a real device specific fbdev driver and > quit trying to run without a device specific driver in place? History > has shown that to be bad idea except during early boot when there > isn't a choice. Writing a kms driver and getting it upstream is not a simple task, and starting with a too limited implementation is dangerous as we need to get the devicetree binding first from the get go. IOW this is not really a realistic answer to problem 1. <snip> >> 2) Allowing for output of early kernel boot messages. > > For this to work the kernel needs to know two things - address of the > framebuffer and the x/y layout. Then just nuke this display when the > kernel finishes the boot process. Please read my earlier mails on how completely flawed it is to write "when the kernel finishes the boot process". The problem is that there is no way to really determine when this happens. Regards, Hans -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
