Mike A. Harris wrote:
On Fri, 7 Nov 2003, Mark Vojkovich wrote:
Everywhere
in the driver hex values are given premultiplied by 4 it seems,
and specified as VALUE/4.
The register pointers are dword pointers. The register offsets
are byte offsets. They are written as VALUE/4 so
Tim Roberts wrote:
On Thu, 2 Oct 2003 08:07:31 -0600 (MDT), Marc Aurele La France wrote:
On Wed, 1 Oct 2003, Marc Aurele La France wrote:
My goal is to disable this option by default in drivers which
correctly detect video memory on all supported cards, at least
for our shipped
Dr Andrew C Aitchison wrote:
On Wed, 1 Oct 2003, Mike A. Harris wrote:
If people (both other developers and end users) who _require_
the VideoRAM option in order for the proper amount of video
memory to be useable with their card, could send me privately
their: lspci -vvn or
I'm not sure how stopping the color key painting will help accomplish
your goal here. It may be possible to grab the background data from the
screen position, pre-blend it into your video image, and then display it
as part of the video stream. However that will take quiet a bit of
Havoc Pennington wrote:
On Sun, Aug 31, 2003 at 08:59:39PM +0200, Peter Poulsen wrote:
I'm playing around with xlib, and is trying to make a window manager
(just because I can ;-)). But the problem is that I need a little more
information. Is there some good resources anybody know of?
Kendall Bennett wrote:
Kevin Brosius [EMAIL PROTECTED] wrote:
Depends somewhat on how RH does X init. You can look through
startx and xinit setup and see what's being changed.
Isn't the installer supposed to not replace xinit.rc if the file already
exists? That is what the comment
Kendall Bennett wrote:
Hi Guys,
I have been mass compiling and installing multiple versions of XFree86
onto a machine for compatibility testing (Red Hat 7.3 based, so I can use
the GDB hacked up debugger ;-). However whenever I do a 'make install'
from a freshly built 4.2.0, 4.2.1 or
for
single child of root class InputOnly. Also do some null pointer
protection.
--
Kevin
Mark Vojkovich wrote:
On Wed, 26 Feb 2003, Kevin Brosius wrote:
The background reports Depth: 0 with xwininfo. That looks like a
problem.
The x,y,... to the GetImage seem good, 1103,302,64,64
. It looks like the checks in there are OK.
Can you check the x,y,width,height to that first XGetImage
in GetImageAndAttributes?
Mark.
On Tue, 25 Feb 2003, Kevin Brosius wrote:
Of course, that's not what causes the X_GetImage failure... That
happens here:
in DragEH
With CVS from yesterday:
XFree86 Version 4.2.99.902 (4.3.0 RC 2)
Release Date: 20 February 2003
I notice that their appears to be a cursor drawing bug during a mode
switch. If I use Ctr-Alt-+-, immediately after the switch the upper
left corner of the screen is inverse colored, almost like the
Alan Hourihane wrote:
Here's a list of items for the RELNOTES for 4.3.0, if anyone has anything
to add to this, please send it in.
I'd suggest the following s3virge driver note:
Doublescan modes (320x200) are supported and tested in depth 8 and 16 on
DX, but
disable XVideo. Doublescan
Mark Vojkovich wrote:
It's not there anymore.
Mark.
Seems to be there now, temporary problem?
http://cvsweb.xfree86.org/cvsweb/
--
Kevin
___
Devel mailing list
[EMAIL PROTECTED]
It seems that Xcursor.h is installed in
/usr/include/X11/Xcursor/Xcursor.h in 4.2.99.4. Is this intentional?
Why isn't it directly in X11?
--
Kevin
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Marc Aurele La France wrote:
On Wed, 29 Jan 2003, Kevin Brosius wrote:
Is there a known problem with accelerated fills on some ATI cards at
depth 24? Using an ATI Rage XL (depth 16 log available at
http://kevb.net/files/XFree86_ATI_16.log) at depth 24, I notice
corrupted
Meelis Roos wrote:
Do you know what physical memory the card has without looking at
xfree86? ViRGE cards can be 2M or 4M. You might try specifying 2M and
I googled a little and found that it's likely to be a 2M card. The card
is Formac GA6 (Formac Pro Media 20 Plus), it contains 4
David Dawes wrote:
On Mon, Jan 27, 2003 at 09:52:48PM -0500, Kevin Brosius wrote:
I'd like to be able to add/remove an XVideo interface on the fly during
mode switches. Is this possible with the existing interface? I don't
see anything in the DESIGN doc other than the xf86XVScreenInit
David Dawes wrote:
On Sun, Jan 26, 2003 at 03:06:36AM -0500, Kevin Brosius wrote:
Does the server work correctly other than the key sequence not
working? If it is stuck somewhere, it might explain both why
SIGTERM and SIGHUP didn't do anything and why the terminate key
sequence
Meelis Roos wrote:
Have you tried setting BIT_ORDER_IN_BYTE_LSBFIRST or
BIT_ORDER_IN_BYTE_MSBFIRST in the *ColorExpandFillFlags field of the
XAAInfoRec ?
Wow. Option NoAccel makes the reversion go away and fixes garbage in
Mozilla too.
Changing MSBFIRST to LSBFIRST fixed the
Michel Dänzer wrote:
On Mon, 2003-01-20 at 18:57, Meelis Roos wrote:
Colors are OK now but the bitmaps are broken. When fonts are drawn in
xterm, every 8 pixels are horizontally reversed (in 16bpp mode). Mozilla
window contets are mostly OK but some garbage remains inside frames.
David Dawes wrote:
On Sat, Jan 25, 2003 at 02:42:57PM -0500, Kevin Brosius wrote:
I've upgraded a machine from an early version of 4.2.99 (.1 I think) and
find a couple problems. I am unable to kill the server with
Ctr-Alt-BkSpc as mentioned in several earlier list emails, although
20 matches
Mail list logo
