On 25/02/16 15:43, Linus Walleij wrote: > 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. You can build firmware images into the kernel image. No, I don't like that either. The 2.2) option in Pantelis' mail can be used for 1) too, although then the bootloader needs to know which dtbos to add. Tomi
Attachment:
signature.asc
Description: OpenPGP digital signature