How to keep splash bmp retained during boot up (A20-OLinuXino-buster-base)?

[-peter-]

Hello,

I've an image displayed within u-boot like this:

---boot.scr----
...
load mmc 0:1 0x40000000 /splash.bmp
bmp display 0x40000000
...
----------------

is works so far, but then the kernel comes up the screen is cleared and remains black until xorg comes up.
What can I do to prevent linux kernel from cleaning the framebuffer?

I know from earlier projects there is a possibility to put an own splash into the kernel.
I wonder where can i download the kernel source which has been used for the current a20 olinuxino image (kernel 5.8.18)?

Or even is there maybe simplier way to get the splash pic remained?

with best Regards,
Peter

[-peter-]

I've downloaded and configured the linux-olimex kernel (from https://github.com/OLIMEX/linux-olimex) by using the appropriate config file and changing the following option:

Device Drivers
  -> Graphics Support
     -> Console display driver support
        -> Framebuffer Console Deferred Takeover

which results in defined CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER

and now the kernel doesn't clear the console any more, so far.
But now, later on, the udev seems to do it :-(

Any ideas?

with best regards
Peter

[DannyGilbert]

Yes, but to bind my framebuffer on console I get this warning
'Redundant State change in glBindFramebuffer call, FBO 1 already bound '

[ullrich]

Yes, but to bind my framebuffer on console I get this warning
'Redundant State change in glBindFramebuffer call, FBO 1 already bound '

The diagnostic message tells you that you're making a redundant state change. But querying the current state to compare it with your new value is most likely much worse