| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
OK kettenis@
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
|
|
|
|
| |
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@
|
| |
|
|
|
|
| |
ok matthieu@, deraadt@, patrick@
|
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
| |
OK kettenis@, deraadt@
|
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
|
|
|
|
|
| |
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@
|
|
on some platforms that use device trees. Works on Allwinner (sunxi) and
should also work on Raspberry Pi (broadcom) armv7 platforms.
ok jsg@, visa@
|