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 fix
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 fr
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 this
problem is listed as resolved. Are there changes required in XF86Config
or elsewhere to mak
For a previously working setup, mouse protocol auto no longer succeeds
in configuring the mouse, however it appears not to fail either, leaving
the server up with a non-working mouse pointer. I do not have
'AllowMouseOpenFail' set.
Log file: http://kevb.net/files/XFree86_nokill_nomouse.log
This
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 mentione
David Dawes wrote:
>
>
> On Sat, Jan 25, 2003 at 03:21:10PM -0500, Kevin Brosius wrote:
> >For a previously working setup, mouse protocol auto no longer succeeds
> >in configuring the mouse, however it appears not to fail either, leaving
> >the server up with a non-w
David Dawes wrote:
>
>
> On Sat, Jan 25, 2003 at 04:01:02PM -0500, Kevin Brosius wrote:
> >David Dawes wrote:
> >>
> >>
> >> On Sat, Jan 25, 2003 at 02:42:57PM -0500, Kevin Brosius wrote:
> >> >I've upgraded a machine from an early vers
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&
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()
function for setup. The ViRGE doesn't seem capable of XVideo during
doublescan modes (320x
I've put up an updated test driver with new 320x200 and doublescan mode
support at http://www.user1.netcarrier.com/~kbrosius/pages/virge.html .
Please report any problems here on the mailing list. Thanks to
"linuzappz" <[EMAIL PROTECTED]> and Eugene Grosbein
<[EMAIL PROTECTED]> for pointing out t
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 fill backgrounds on the text in xf86cfg. To reproduce, start
xf86cfg, open Expert mode (clicking
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 anyt
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
Meelis Roos wrote:
>
>
> > > Now the remanining problem is the garbage in lower part of the screen -
> > > any ideas about that? It's there even with NoAccel and changing too.
> >
> > If you have accel enabled, but then use 'sw_cursor' option, does the
> > noise still appear?
>
> Yes. Just movin
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 conta
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
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]
http://XFree86.Org/mailman/listinf
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
Is it expected that remote apps will use the theme setup on their host,
rather than the one on the server side? Here's why I ask:
Running 4.2.99.901 with whiteglass or a theme I'm making up works fine
for local applications. Now I remote log into a machine running
4.2.99.4 (which defaults to red
Keith Packard wrote:
>
>
> Around 19 o'clock on Feb 9, Kevin Brosius wrote:
>
> > Is it expected that remote apps will use the theme setup on their host,
> > rather than the one on the server side? Here's why I ask:
>
> Depends on how things are confi
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
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 s
I've noticed the following xmag segv with current CVS when trying to
view part of the background in the development version of e (e17). Is
this an xmag or a window manager problem? (Or both?)
(gdb) r
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed req
Marc Aurele La France wrote:
>
>
> On Sat, 22 Feb 2003, Kevin Brosius wrote:
>
> > 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
->xmotion.y_root),
event->xbutton.x_root,
event->xbutton.y_root,
srcWidth, srcHeight, data);
the GetImage call above generates the BadMatch. The embedded
FindWindow() calls seem to succeed.
Kevin Brosius wrote:
>
> Latest CVS xmag (ye
Maybe you can get a backtrace with a debug xmag?
>
> Maybe it has something to do with RandR?
>
> Mark.
>
> On Mon, 24 Feb 2003, Kevin Brosius wrote:
>
> > I've noticed the following xmag segv with current CVS when trying to
> > view part of the backgrou
e on the
> root window. 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 no
h during a X_GetImage 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
>
I don't have any terribly recent info, but s3graphics was still under
the Via umbrella last time I checked. They had docs available as long
as you were willing to sign an NDA. The NDA allows source code release,
so is compatible with XFree86 development.
--
Kevin
Alex Deucher wrote:
>
>
> w
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.
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
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 anybod
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
pre-processing.
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
> >
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 -v
Shawn Starr wrote:
>
>
> I have an IBM 300PL w/ an onboard Trio 3D Chip, the model does not appear to
> be supported (?)
>
> When X loads, it won't allow resolution beyond 640x480, it drops back to
> 640x480 regardless of how I configure.
>
> The chip information is as follows (from the chip):
"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 w
dave giffin wrote:
>
>
> I need to be able to tell which process a given window
> was created by. (Window ID=>Process ID)
>
> Apparently, X servers don't know which process a
> client is, they just get a socket (b/c of X's network
> transparency).
>
> It has been suggested that I could run a pr
38 matches
Mail list logo
