Modernizing the OpenBSD Console
cambus.net
Modernizing the OpenBSD Console
1–10 of 62 posts
Re: Modernizing the OpenBSD Console
#2Re: Modernizing the OpenBSD Console
#3Will it support "true colors" (16M colors)[1][2]? [1] https://github.com/termstandard/colors [2] https://gist.github.com/XVilka/8346728
> In framebuffer however, to fill a 4K UHD-1 (3840x2160) screen in 32bpp mode we need to send 3840 * 2160 * 4 bytes of data, which is 33177600 bytes (approximately 33 MB).
but I don't know if that is in fact the definition a "framebuffer console" versus a terminal that uses character addressing.
That's a different issue that actually supporting 32-bit ANSI codes, but I think it's an indication of the scope of a an effort to update the console implementation.
Re: Modernizing the OpenBSD Console
#4Re: Modernizing the OpenBSD Console
#5Will it support "true colors" (16M colors)[1][2]? [1] https://github.com/termstandard/colors [2] https://gist.github.com/XVilka/8346728
The article uses 32 bits per pixel to illustrate the growth in performance requirements: > In framebuffer however, to fill a 4K UHD-1 (3840x2160) screen in 32bpp mode we need to send 3840 * 2160 * 4 bytes of data, which is 33177600 bytes (approximately 33 MB). but I don't know if that is in fact the definition a "framebuffer console" versus a terminal that uses character addressing. That's a different issue that actu…
The diffs that are attributed to Carmack seem to deal with this. scr->rs_bs[off].uc and scr->rs_bs[off].attr appear to represent the gylph and attributes/color respectively.
So I would expect that would severely limit the amount of colors available to the input buffer. OTOH I just found the declaration in the code and the attributes are 32 bits wide which is more than the 8 that VGA provides:
struct wsdisplay_charcell {
u_int uc;
uint32_t attr;
};
Note I would expect the 32 bits of attr to be divided between fg and bg color, and it seems like they carved out bits for things like underline.Edit: after reading some more it seems like the color values range from 0-7.
Re: Modernizing the OpenBSD Console
#6Just curious, but does anyone know a business using OpenBSD in production other than the Pushover App?
Armorlogic, Calyptix Security, GeNUA, RTMX, and .vantronix make network appliances based on the complete OS.
Re: Modernizing the OpenBSD Console
#7Just curious, but does anyone know a business using OpenBSD in production other than the Pushover App?
Virtually everyone uses bits of OpenBSD. Android uses a lot of its C standard library, LLVM uses its regular expression library, and Windows 10 uses OpenSSH with LibreSSL. Armorlogic, Calyptix Security, GeNUA, RTMX, and .vantronix make network appliances based on the complete OS.
Re: Modernizing the OpenBSD Console
#8While it's not quite related to consoles, I've noticed that the non-GUI interface to a lot of operating systems often don't get a lot of love. Linux has had a fairly nice boot scroll, but I think part of that is because it's become an icon and as such is part of the public face of the OS; but on macOS for example it's an tiny awful experience because the text doesn't scale to 2x (you'd think Apple would be the first one to fix this…) and the output isn't well formatted at all–it's just the various subsystems spewing text as they start up. And a lot of modern systems use kind of old fonts that in many cases seemed to be picked as an afterthought…
Re: Modernizing the OpenBSD Console
#9Just curious, but does anyone know a business using OpenBSD in production other than the Pushover App?
Virtually everyone uses bits of OpenBSD. Android uses a lot of its C standard library, LLVM uses its regular expression library, and Windows 10 uses OpenSSH with LibreSSL. Armorlogic, Calyptix Security, GeNUA, RTMX, and .vantronix make network appliances based on the complete OS.