| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
based upon the old HP ngle X11 driver. Currently limited to CRX (720/735/750),
Timber (710, old 715), Artist (712, 715) and EG (B-series), however the
colormap isn't set up correctly on Timber and EG yet.
Joint work with Artem Falcon, now in good enough shape to be worked further
in the tree.
|
|
|
|
|
|
|
|
|
|
|
| |
information. This is preliminary work to help eventually supporting the
dual-head ELK model.
Also split the initialization code in several routines, this makes the
code easier to read, and makes it easier to release resources upon failure.
Finally, don't forget to clear the text planes on non-console displays
when initializing.
|
|
|
|
| |
resolutions to attach without disturbing each other.
|
|
|
|
|
|
|
|
| |
access to the sti rom, as this seems to be necessary for sti@pci; hide this
with macros so that platforms which do not have pci support (i.e. hp300)
do not get bloated from this.
ok mickey@
|
|
|
|
|
|
| |
sti_end_attach() if an error has occured.
ok mickey@
|
|
|
|
|
|
|
|
| |
instead of using the rom mapping for region #0 and the device mapping for
region #1. This will allow sti devices on which regions may be relative to
different origins to attach (to be used very soon).
ok mickey@
|
|
|
|
| |
with scribbles around; ok mickey@
|
|
|
|
|
|
| |
use it instead of duplicating the same logic in 3 places.
ok mickey@
|
|
|
|
|
|
|
|
|
|
|
| |
attachment and interface, one screen-attached for the real work.
The attachment code is now required to decide whether sti_end_attach() is
run immediately, or as a startuphook.
This allows hp300 to initialize sti early, and use it as a console; hppa
is functionally unchanged, as it uses the PROM console until the root device
is mounted.
|
|
|
|
|
|
|
|
| |
- specify which microcode bank (pa or m68k) to use at attachment time.
- compensate for broken 8.02 m68k code which reports wrong frame buffer
offset.
ok mickey@
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
memory, and use block move operations in putchar, rather than keeping a copy
of the prom font in memory and using memory to frame buffer transfers.
Recommended by the sti docs. No visible performance improvement though.
Tested on both kind of sti devices by mickey@ and myself.
|
|
|
|
| |
ok mickey@
|
|
|
|
|
| |
and myself.
wsdisplay at sti will be enabled as soon as byte-size rom font loading is done.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
attach point for wsdisplay.
a few problems may exist w/ certain prom versions.
tested in byte- and word-wide modes.
no support yet for multiple resolutions and fonts.
pci not tested (obviously).
|