| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
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@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
into wsdisplay(4). This code is now exposed through
wsdisplay_brightness_{step,zero,cycle} functions that can be called by
any driver that handles brightnes "hotkeys". These functions take
a wsdisplay(4) device pointer as their first argument, which should be
provided if a clear association between events and a particular display
exist. This is used in wskbd(4). Otherwise NULL can be passed and
the code will direct the request at the first wsdisplay(4) that
implements brightness adjustment.
Tested by many. Fixes brightness keys on x395 and other thinkpads with
AMD graphics.
ok patrick@
|
| |
|
|
| |
ok deraadt@, jsg@
|
| |
|
|
|
|
|
| |
Trivial conversion from ticks to milliseconds where macros already come in
milliseconds and timeout values only need reduction by hz to use the new API.
OK mpi
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
when we have a serial console by introducing the notion of a "primary"
graphics device. The primary graphics device is the one set up and
used by firmware (BIOS, UEFI).
The goal is to make sure that wsdisplay0 and drm0 reliably attach to
the primary graphics device such that X works out of the box even
if you have multiple cards or if you are using a serial console.
This also fixes the situation where inteldrm(4) or radeondrm(4) would
take over the console on UEFI systems even if the kernel was booted
with a serial console.
ok jsg@
|
| |
|
|
|
|
|
| |
the modeset lock when entering ddb. This avoids triggering various asserts
when the kernel panics while running X.
ok deraadt@
|
| | |
|
| |
|
|
|
|
| |
but burning still disabled by default. Setting display.screen_off to a nonzero
value with wsconsctl will be enough to enable screen blanking after the
given time.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
wsdisplay softc. Instead, since the knowledge about available fonts lies in
the parent driver itself, introduce a list_font wsdisplay_accessop which
queries a font index, suitable to use within the WSDISPLAYIO_LSFONT ioctl.
With this in place:
- there is no global wsdisplay limit on the number of fonts loaded. Such a
limit will be enforced by the display drivers themselves.
- built-in kernel fonts will now appear in the list of fonts.
Grow a list_font accesop for rasops, which relies upon wsfont_enum(), which
is turned into something useful (and abortable if you do not need to iterate
further). Not used by any rasops driver yet.
|
| |
|
|
|
|
|
| |
sparc/sparc64, white on black for everybody else), and use them to construct
a default color attribute in the rasops(4) code.
ok miod@
|
| | |
|
| |
|
|
| |
ok miod@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we hit suspend time, go through all wsdisplays on the system. if
they are in mode MAPPED, but not MODE_DUMBFB then if possible do a full
vt switch to a !mapped vt, and prevent switching back until resume time.
This has to be called from MD code because this involves userland
running so that X can run the vt switch signal handler. This way, any
case where we are using the "poke registers from userland" model, we
will not be on the hardware when we go down, so the kernel can actually
handle thing properly.
Tested on several acpi laptops (by kettenis@ and ian@), x40 (me and
beck@ at LEAST) and zaurus (me). Maybe others, but if so I forgot who at
this time..
Idea from deraadt somewhere over the Faroe Islands (I thought of a
similar thing myself a while ago). Much prompting from him. Ok and
comments miod@
|
| |
|
|
|
|
| |
return zero on success and nonzero on failure.
This commit only performs mechanical changes for the existing emulops to
always return zero.
|
| |
|
|
| |
different for sparc{,64} systems.
|
| |
|
|
|
|
|
|
|
|
| |
display-dependent value, but instead fill a structure with the chaarcter
and a valid attribute, suitable for use with unpack_attr.
Adapt the wsmoused code to these changes, and remove all knowledge of
the text-mode style pc video attributes in it.
This will eventually allow wsmoused to be used on non-pcdisplay devices.
|
| |
|
|
|
| |
existing alloc_attr function. This allows rasops_unpack_attr to be kept
private to rasops, yet available to the screen drivers.
|
| |
|
|
|
| |
driver to be able to tell how many wscons screens to attach to it,
instead of WSDISPLAY_DEFAULTSCREENS which is a global setting.
|
| |
|
|
|
|
|
|
| |
of needing different WSCOL_{BLACK,WHITE} values than 8bit frame buffers.
This allows us to not special case the alloc_attr() invocations depending
on the color depth, and to make WSCOL_{BLACK,WHITE} constants again in the
wsemul_sun land.
|
| |
|
|
|
| |
emulation, we can reuse the existing WSCOL_xxx codes, and WSCOL_BLACK and
WSCOL_WHITE will point to variables anyway.
|
| | |
|
| |
|
|
|
|
|
| |
and bugfixes (the kqueue code, /dev/wsmuxctl and screen border color changes
have not been picked), keeping local changes.
Tested by many on alpha/cats/hp300/i386/macppc/sparc/sparc64/zaurus if not more.
|
| |
|
|
|
|
|
| |
text mode colors.
This means black text on white background, even for the kernel messages.
Initially based on a patch from jason@, then some tinkering by me.
|
| |
|
|
|
| |
X-Window at the same time, removing the need to kill wsmoused(8) before
starting X-Window.
|
| | |
|
| | |
|
| |
|
|
|
| |
disabled by default, also supports vsync blanking, disabled by default.
aaron@ looked at it a while back and i fixed problems he had indicated.
|
| |
|
|
|
|
|
|
|
|
| |
the wsmoused daemon (replacement for moused which was used with PCVT). Adds
a "getchar" method to the display drivers which returns the value of the
character currently under the cursor (e.g., so it may be inversed). From jbm@.
Still needs a bit of cleanup and improvement, especially X cohabitation
features. The pointer moves to fast as well. These sorts of issues will be
corrected in-tree.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
the screen was only restored if a new character was actually displayed on the
screen); jcs@rt.fm. This brings us closer to the behavior of PCVT. Also, while
I'm here, add some #ifdef so wskbd does not depend on wsdisplay (pointed out
to me by fgsch@).
|
| | |
|
| | |
|
| |
|
|
|
|
| |
hooks into the lower-level display driver. The updated vga(4) driver I'm about
to commit has support for this. This is a fairly unobtrusive way to implement
scrollback while maintaining the abstraction of the wscons system.
|
| | |
|
|
|
art@ said it will make his life easier in alpha
rhands@ said it is not used in powerpc for now
bjc@ said that it would make vax port easier
mickey@ said other platforms can use it, and it's faster
|
fcambus
jsg
kettenis
kn
tedu
miod
oga
jbm
millert
mickey
aaron