On Wed, Feb 24, 2016 at 1:13 PM, Pantelis Antoniou <pantelis.antoniou@xxxxxxxxxxxx> wrote: > IMHO DT+overlays handle all your cases just fine. > > As far as I see these are the cases which we need to handle: > > 1) The expansion board in question has some means of identification, whether it’s an > EEPROM or a GPIO keying combination etc. In that case it is the kernel’s job to match this > id value with a dtbo firmware file and apply it. The blob is located via means of request_firmware(). Since the dawn of time the x86 people used that console to display the early boot crawl and collect crash data. What you're suggesting is that we can't get the console up until after the filesystems and mounts are up so the kernel can read firmware files. This kills of early boot graphics and getting crash logs on the fbdev console until that has happened. It also means there is no way to get the console up without the right firmware files in the filesystem. I think that is really crap compared to what we have today where the display will always come up, and basically a regression. I understand the stance with respect to things like add-on hardware like a Bluetooth board or WLAN or whatnot. But the fbdev console is just too basic, like a serial port IMO. Sure in the ARM world we usually have a serial console, but this is seriously breaking current practice. Yours, Linus Walleij -- 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
