| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Rather than writing to the engine command register for every
operation, set quick start mode, and the operation executes
automatically when the width register is written.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
FBBase already take the register offset into account.
|
|
pSmi->FBOffset is the offset from the start of the framebuffer
pScrn->fbOffset is the aperture offset where the framebuffer
starts
|
|
|
|
|
|
Based on Dennis' code from bug 8721 with some minor
changes by me.
|
|
|
|
|
|
on the initial mode set the engine doesn't idle
for some users.
|
|
regsmi.h got lost? commit 9a58bc9adbc982680dd8df27caeb9a5819f2adad looks
like the culprit, but siliconmotion has built fine subsequent to that commit.
Not sure exactly what's going on.
|
|
limitations -- I'll improve it a bit at some point)
- small driver clean ups
|
|
|
|
redirected video.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
change "foo.h" to <X11/foo.h> for core headers, e.g. X.h, Xpoll.h;
change "foo.h", "extensions/foo.h" and "X11/foo.h" to
<X11/extensions/foo.h> for extension headers, e.g. Xv.h;
change "foo.[ch]" to <X11/Xtrans/foo.[ch]> for Xtrans files.
|
|
Delete xf24_32bpp, as s3virge was the last user. Fix up some comments
to refer to fb rather than cfb.
|
|
list, so the loader knows not to complain about unresolved symbols when
an optional module isn't loaded. This typically manifests as warnings
about fbdevHW symbols when the user isn't using the framebuffer
console.
|
|
COMPOSITE extension's new macro. These appear to only be used
internally.
|
|
*Weak() resolver functions.
|
|
framebuffer formats except cfb and the overlay modes should work, and
r128 and radeon need to be loaded from the ati driver (both issues to
be fixed soon). Tested on i740, s3virge, mach64, tdfx, vesa, and vga
drivers. elfloader users shouldn't be affected.
|
|
|
|
driver: Fixed setting of minimal clocks for HiQV chipsets. Neomagic
driver: improved support for lowres double scan modes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
