> Date: Tue, 7 Jul 2020 17:55:32 +0200 > From: Frederic Cambus <f...@statdns.com> > > On Wed, Jul 08, 2020 at 12:06:27AM +1000, Jonathan Gray wrote: > > On Tue, Jul 07, 2020 at 03:16:33PM +0200, Frederic Cambus wrote: > > > Hi tech@, > > > > > > The recent spike of interest around framebuffer consoles has prompted > > > me to revisit a proposal I sent back in early 2017 [1]. > > > > > > Aesthetics considerations aside, kettenis@ raised the concern that colors > > > from the original rasops palette carefully matched what OpenFirmware > > > uses for the console on sparc64. > > > > > > Therefore, I propose to default on using the proper VGA text mode palette > > > RGB values, and to keep the original rasops color palette on sparc64. > > > > > > The differences between the two palettes can be seen here [2]. > > > > > > Comments? OK? > > > > Why is it important to match VGA colours? > > We don't try to match video modes or fonts. > > In case it wasn't obvious by comparing the two palettes, the main problem > with the rasops palette it that the NORMAL_RED, NORMAL_GREEN, NORMAL_BLUE, > NORMAL_MAGENTA and NORMAL_CYAN colors are too dark. > > NORMAL_BLUE is especially problematic as it's very difficult to read on > a black background.
But NORMAL_BLUE is used as the background color for kernel messages. So making it brighter reduces contrast there. Unless there is an overwhelming majority of users/developers who thing the colors should indeed be changed. If there is a significant minority that thinks the current colormap severely impacts the usability of the framebuffer console, then maybe an interface to change the colormap from userland is needed. Cheers, Mark
