#
86dac4ab |
| 29-Dec-2008 |
miod <miod@openbsd.org> |
Move ifb identification to its own routine. We can not simply have the ifb probe win over vgafb, since one may configure a kernel with vgafb but without ifb (especially slackers who forget to rerun c
Move ifb identification to its own routine. We can not simply have the ifb probe win over vgafb, since one may configure a kernel with vgafb but without ifb (especially slackers who forget to rerun config).
show more ...
|
#
607827a8 |
| 27-Dec-2008 |
miod <miod@openbsd.org> |
Sync the sparc64 fb* api with the recent changes done on sparc.
|
#
ece7a61f |
| 12-Mar-2006 |
miod <miod@openbsd.org> |
Previous fix was half-done, move the wsscreen_list array into the softc as well.
|
#
cffcb173 |
| 12-Mar-2006 |
miod <miod@openbsd.org> |
When attaching a wsdisplay, the wsscreen_list structure can not be on the stack; found the hard way by Stefano <stefano@merlinobbs.net>.
|
#
aca70fa6 |
| 07-Mar-2005 |
miod <miod@openbsd.org> |
Do not bother passing the blanking routine to fbwscons_console_init(), as fbwscons_attach() can find it on its own.
|
#
de9ae89d |
| 29-Nov-2004 |
miod <miod@openbsd.org> |
Move the struct wsscreen_descr from a per-driver global to a per-instance field of the sunfb structure. This allows multiple instances of the same driver, but with different resolutions (such as a co
Move the struct wsscreen_descr from a per-driver global to a per-instance field of the sunfb structure. This allows multiple instances of the same driver, but with different resolutions (such as a couple of vigra or a TGX cgsix and a TGX+ cgsix) to use distinct wsscreen_descr structures featuring different resolution information.
Doing this allows more wsscreen_descr fiddling inside the sparc* fb api, and results in some code shrinkage (about 4KB on sparc GENERIC).
show more ...
|
#
2628683e |
| 17-Jun-2003 |
miod <miod@openbsd.org> |
Extend the sunfb structure to take care of the PROM cursor position pointers, and adapt creator to the fb api. ok jason@
|
#
70d3ea64 |
| 16-Jun-2003 |
miod <miod@openbsd.org> |
Provide the same fbxxx() api as on sparc, in order to factorize more code and eventually share some drivers. This also brings us screen unblanking upon entering ddb, which can be really useful at tim
Provide the same fbxxx() api as on sparc, in order to factorize more code and eventually share some drivers. This also brings us screen unblanking upon entering ddb, which can be really useful at times...
show more ...
|