On Mon, Mar 03, 2003 at 09:46:40PM -0500, David Dawes wrote:
2) a way to tell the framebuffer/viewport sizes for each supported
resolution, something like :
SubSection Display
Mode 1024x768
Viewport 0 0 1024 768
Viewport 0 0 800 600
Viewport 0 0 640 480
Keith Packard writes:
Around 0 o'clock on Mar 4, Mark Vojkovich wrote:
This is the core SW cursor not the ARGB SW cursor, though I haven't tried
ARGB SW cursors (I forgot how to set one as the root cursor).
$ XCURSOR_THEME=redglass XCURSOR_SIZE=256 xsetroot -cursor_name shuttle
Balint Cristian wrote:
Regard to that one BUG with the mention that it persist in 4.3.0 too
and any CVS too:
By Rene:
http://marc.theaimsgroup.com/?l=xfree86m=104526841725691w=2
By mysef:
http://marc.theaimsgroup.com/?l=xfree86m=104385693307371w=2
I send more deBug:
On Mon, 2003-03-03 at 16:09, David Dawes wrote:
Is it safe these days to unconditionally use /lib/modules/`uname -r`/build
for $LINUX_SRC_DIR?
It's probably as good a _default_ as any. We shouldn't make it too hard
to change though.
Will a single Makefile.kernel work for all versions of the
Around 7 o'clock on Mar 4, Martin Gruber wrote:
Can anybody give me a hint, if there is already a switch/define to change
the bit-order in a byte for the kdrive Xfbdev XServer or tell me, where to
The easiest way is to implement this with a shadow frame buffer; the fb
code doesn't
So 4.3.0, as it is distributed, doesn't build on FreeBSD alpha (I run
-current, but I think the same problems would exist for -stable).
The following patch makes the build work for me - it runs ok with my
matrox millenium II card (though my virtual consoles are permanently blank
after X runs the
On Tue, 4 Mar 2003, Egbert Eich wrote:
Keith Packard writes:
Around 0 o'clock on Mar 4, Mark Vojkovich wrote:
This is the core SW cursor not the ARGB SW cursor, though I haven't tried
ARGB SW cursors (I forgot how to set one as the root cursor).
$ XCURSOR_THEME=redglass
On Mon, 3 Mar 2003, David Dawes wrote:
Did you change any build options from their defaults?
Try 'make WORLDOPTS= World' and see where it stops, or search your World
log file for the first error. By default 'make World' will continue
beyond errors. I've never liked that behaviour
I'm forgetting this stuff...
Is the caller of PushPixels supposed to add the drawable
origin onto the x,y arguments of PushPixels or is PushPixels
supposed to do that? It looks like the caller is supposed
to add the origin before calling PushPixels. If I haven't
misread this, then
Hi Guys,
I know I have asked this before, but I can't seem to find my emails and
the mailing list archive does not seem to be responding.
What sort of back/forward compatibility is there with the XFree86 driver
modules? From memory last time I tested this, if I compile a 4.2.0 module
it will
I needed to make the following changes in order to compile on Solaris 9
with an older version of the Sun C compilers (one without any C99 or
recent gcc-ish extensions). These changes should be compatible with all
compilers though.
1) Unneccessary use of C99/gcc varargs macros in makedepend.
Feigning erudition, Kendall Bennett wrote:
% Hi Guys,
%
% I know I have asked this before, but I can't seem to find my emails and
% the mailing list archive does not seem to be responding.
%
% What sort of back/forward compatibility is there with the XFree86 driver
% modules? From memory last
Kurt Wall [EMAIL PROTECTED] wrote:
Hmm. I installed 4.3.0 on a crash test dummy at work today. I had
the mga_hal.o module from Matrox for 4.2.mumble. Copied it into
place, started X, and it seemed to load without incident - no
untoward messages in the log files and neither the monitor nor the
13 matches
Mail list logo
