Re: [RFC PATCH v2 03/13] bootsplash: Flush framebuffer after drawing
From: Ray Strode
Date: Wed Dec 20 2017 - 10:36:25 EST
> Actually, I don't want that :)
> This was a design decision that I've made to keep the code small and simple to audit.
> As it is, the simple bootsplash code will make 99% of people happy.
You think only 1% of linux users have more than one monitor or a 4k screen?
> I've made this decision from the point of view of someone who wants to ship a general
> purpose distribution. If you have a look around and compare this to e.g. the Windows or
> Mac OS X bootsplashes, the possibilities that my kernel code provides already
> surpasses them.
I haven't looked specifically, but I don't believe you :-) You're
telling me the apple boot
splash isn't scaled up on machines with retina displays? I don't use
OSX (or windows),
so I don't know, but I'd be really surprised.
> If you really want such sophisticated features, supplanting the initial bootsplash with
> Plymouth (or not using it at all) is a better solution. In my opinion, it is overengineering,
> at least for kernel code.
disagree..it's support for basic, commodity hardware these days.
> As for HiDPI, if you're working on an embedded device with a fixed screen size -
> say a phone - you can easily include a huge picture the size of the screen in the
I'm talking about a situation where you have a dell xps or whatever
with an external
monitor attached. Each monitor should be able to show the splash
it, and without making it huge or microscopic. pretty basic stuff...