wireguard-openbsd/sys/dev/fdt/simplefb.c, branch jd/histogram WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/fdt/simplefb.c?h=jd%2Fhistogram 2020-05-28T20:24:26Z Enable scrollback in simplefb(4). 2020-05-28T20:24:26Z fcambus fcambus@openbsd.org 2020-05-28T20:24:26Z urn:sha1:ec4b3547fae2b28a4f81673d616ced568dccf6e9 OK kettenis@ change wsdisplay attribute type from long to uint32_t 2020-05-25T09:55:47Z jsg jsg@openbsd.org 2020-05-25T09:55:47Z urn:sha1:e0c3e5595cd64cda848d09b1c753f51bcbadd436 miod explained it was initially a long as it was thought drivers may need to allocate storage but in practice they don't need more than 32 bits for an attribute. suggested and reviewed by miod@ rename wsdisplay alloc_attr() to pack_attr() 2020-05-25T06:45:25Z jsg jsg@openbsd.org 2020-05-25T06:45:25Z urn:sha1:fc223b232cff7e51a9474209d53006b4ae5898e7 Suggested by John Carmack. miod agrees a rename would make sense and explained it was initially thought drivers may need to allocate storage but in practice they don't need more than 32 bits for an attribute. ok mpi@ The Pinebook Pro's u-boot seems to add a zero-length framebuffer 2020-01-22T05:25:05Z patrick patrick@openbsd.org 2020-01-22T05:25:05Z urn:sha1:67e2424d1a3563f823f4b132c34ce1fd28dbe0b1 node, which essentially means that there is none. Make sure we don't attach in that case, so that we don't panic while trying to map it. ok kettenis@ WSDISPLAYIO_GTYPE is u_int not int 2019-12-25T11:42:05Z jsg jsg@openbsd.org 2019-12-25T11:42:05Z urn:sha1:7321c2f606535f7455b76763877cc2785c4215a4 Add display brightness hooks. 2019-10-13T17:00:54Z kettenis kettenis@openbsd.org 2019-10-13T17:00:54Z urn:sha1:8cd7757ea6cae2cbc20c8db99177aa87c4123157 ok matthieu@, deraadt@, patrick@ Add an interface that allows drivers to claim a framebuffer and check 2018-08-27T09:30:07Z kettenis kettenis@openbsd.org 2018-08-27T09:30:07Z urn:sha1:2723123cafb705c78b5251329bdd932ca6b834d9 whether another driver has already claimed a framebuffer. Use this in radeondrm(4) and simplefb(4) to prevent the latter from attaching if radeondrm(4) is attached to the hardware that provides the framebuffer set up by the firmware. ok mlarkin@ Display color depth alongside resolution when attaching simplefb(4). 2018-07-31T17:25:55Z fcambus fcambus@openbsd.org 2018-07-31T17:25:55Z urn:sha1:f3d31b3e2e9e6d810d80ce71b8798fed7b3f1bf1 OK kettenis@, deraadt@ Map framebuffer into userland as non-cachable (but normal) memory. We still 2017-12-18T10:13:45Z kettenis kettenis@openbsd.org 2017-12-18T10:13:45Z urn:sha1:8186ecd8fbb8a8a2a9b7ecdfb31294d26a3db07e map the framebuffer as device memory in the kernel. Using mismatched memory attributes like this is discouraged (and we should probably fix this at some point) but this particular case is well-defined and the potential side-effects should not matter for thus use-case. ok patrick@ Add glass console support for arm64. This uses the "stdout-path" property 2017-08-27T12:42:22Z kettenis kettenis@openbsd.org 2017-08-27T12:42:22Z urn:sha1:62b18b30963e2a1b130a98ad6fda789270325de9 of the /chosen node in the device tree to decide whether the framebuffer should be used as the console device. Most, if not all, machines will have that set to use a serial console and there is no easy way yet to change that. ok jsg@