On Sat, 7 Feb 2004 09:30 pm, Andrew C Aitchison wrote:
I see that the patch
http://cambuca.ldhs.cetuc.puc-rio.br/multiuser/XFree86-4.3.0-unified.patch
at
http://cambuca.ldhs.cetuc.puc-rio.br/multiuser/
was tidied up in September 2003, and may now be suitable for inclusion
in XFree86
--- Karl Oberjohn [EMAIL PROTECTED] wrote:
Hello,
I have a Mitsubishi AMiTY CN2 notebook with a NeoMagic NM2097
(MagicGraph
128ZV+) video chipset. I was excited to see that XVideo support was
added
for NeoMagic chipsets in XFree86 version 4.3, but for the life of me,
I could
not get
Hello,
With XFree 4.4, nv driver and GeForce2 Integrated (Chipset ID
0x01A0), XFree hangs.
The log shows that the video ram size value determinated is
wrong ( VideoRAM: 1120256 kBytes )
In file nv_setup.c, in function nv10GetConfig, the line :
if((pNv-Chipset 0x) == 0x01a0) {
should be
I'm trying to make v4l driver to work with chips (Chips and tech
69030) x11 driver. The frame grabber can only write directly to
offscreen video memory in YUV format. But the X11 v4l driver reports
RGB as the only offscreen image format available. Althoough the chips
does support both RGB and
Hi!
This is a general question on X client design. Please excuse me that
it is not directly related to the XFree86 Project.
Imagine there are two clients running the same code:
while (!done)
{
XWindowEvent(... | VisibilityChangeMask, theEvent);
switch (theEvent.type)
Thanks for finding that typo. I've committed the fix.
Mark.
On Sat, 7 Feb 2004, Law wrote:
Hello,
With XFree 4.4, nv driver and GeForce2 Integrated (Chipset ID
0x01A0), XFree hangs.
The log shows that the video ram size value determinated is
wrong ( VideoRAM:
On Sat, 7 Feb 2004, Suhaib Chishtie wrote:
I'm trying to make v4l driver to work with chips (Chips and tech
69030) x11 driver. The frame grabber can only write directly to
offscreen video memory in YUV format. But the X11 v4l driver reports
RGB as the only offscreen image format available.
i saw this get committed; seems serious after doing some research on this
bug.
how cum we don't have it?
mark.
--- Forwarded message ---
From: Kaleb Keithley [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Xorg-commit] xc/lib/font/fontfile dirfile.c,1.1.4.2,1.1.4.3
Date: Sat, 7 Feb
On Sat, Feb 07, 2004 at 07:56:58PM -0500, mark kandianis wrote:
i saw this get committed; seems serious after doing some research on this
bug.
how cum we don't have it?
The fix was being held to allow for a coordinated release of the
details and updated vendor packages. Since it is public
David Dawes wrote:
The fix was being held to allow for a coordinated release of the
Perhaps if someone from XFree86 had contacted the X.org security list
to notify the other X vendors that this issue was being coordinated,
it would have been handled properly. Who exactly does the coordinating
and
Andreas Stenglein wrote:
Am 2004.02.04 21:00:14 +0100 schrieb(en) Brian Paul:
Ian Romanick wrote:
Making that change and changing the server-side to not advertise a core
version that it can't take protocol for would fix the bug for 4.4.0. Do
you think anything should be done to preserve text
11 matches
Mail list logo
