CVSROOT:/home/x-cvs
Module name:xc
Changes by: [EMAIL PROTECTED] 05/08/30 06:29:26
Log message:
132. Fix SEGV that can occur under certain builds of glibc 2.3.4 and up, when
linux/int10 attempts to determine kernel support for the vm86() system
call. This
CVSROOT:/home/x-cvs
Module name:xc
Changes by: [EMAIL PROTECTED] 05/08/30 08:17:11
Log message:
133. Fix problems with Xaw's Label widget when using XChar2b strings
(Bugzilla #1606, Alexander Pohoyda).
Modified files:
xc/lib/Xaw/:
Label.c
CVSROOT:/home/x-cvs
Module name:xc
Changes by: [EMAIL PROTECTED] 05/08/30 08:24:07
Log message:
134. Add a tooltip to xbiff that shows the number of messages in a mail
folder (Bugzilla #1607, Alexander Pohoyda).
Modified files:
On Thu, Aug 25, 2005 at 01:21:55PM -0400, Michael wrote:
Hello,
the attached patch adds DDC2/I2C support to the tdfx driver which has
the distinct advantage to work anywhere since it doesn't depend on the
vbe module. It will try DDC2 first and if that fails fall back to the
old vbe stuff when
Hello,
the attached patch adds DDC2/I2C support to the tdfx driver which has
the distinct advantage to work anywhere since it doesn't depend on
the vbe module. It will try DDC2 first and if that fails fall back to
the old vbe stuff when possible.
Moved mode validation and related stuff
On Tue, 30 Aug 2005, Michael wrote:
the attached patch adds DDC2/I2C support to the tdfx driver which has
the distinct advantage to work anywhere since it doesn't depend on
the vbe module. It will try DDC2 first and if that fails fall back to
the old vbe stuff when possible.
Moved mode
Michael wrote:
I don't see why they should be enabled - they're PC-specific and even
with x86 emulation they would be pretty much useless since you're not
too likely to encounter a graphics board with PC firmware in a Mac ( or
other PowerPC boxes )
Wrong. No hardware manufacturer in their
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Roberts wrote:
Michael wrote:
I don't see why they should be enabled - they're PC-specific and even
with x86 emulation they would be pretty much useless since you're not
too likely to encounter a graphics board with PC firmware in a Mac ( or
On Tue, 30 Aug 2005, Ian Romanick wrote:
Tim Roberts wrote:
Michael wrote:
I don't see why they should be enabled - they're PC-specific and even
with x86 emulation they would be pretty much useless since you're not
too likely to encounter a graphics board with PC firmware in a Mac ( or
other
Hello,
I don't see why they should be enabled - they're PC-specific and even
with x86 emulation they would be pretty much useless since you're not
too likely to encounter a graphics board with PC firmware in a Mac (
or other PowerPC boxes )
Wrong. No hardware manufacturer in their right
On Tue, Aug 30, 2005 at 06:01:42PM -0400, Michael wrote:
Hello,
I don't see why they should be enabled - they're PC-specific and even
with x86 emulation they would be pretty much useless since you're not
too likely to encounter a graphics board with PC firmware in a Mac (
or other PowerPC
Hello,
Not entirely true. What you say only matters for the primary head,
and only because most manufacturers package only one image (x86, EFI,
OpenFirmware, etc) in their PCI ROMs.
True, but in this case - tdfx - irrelevant. The driver uses vbe only for
monitor ID as far as I can tell, so
Hello,
Is the implication here that plugging a PC PCI graphics card into
a powerpc machine will never work (as a secondary display), even
if the software driving it knows how to initialise it in the absence
of OpenFirmware?
Of course not. All I said is that you're rather unlikely to find a
On Tue, Aug 30, 2005 at 07:06:22PM -0400, Michael wrote:
Hello,
Is the implication here that plugging a PC PCI graphics card into
a powerpc machine will never work (as a secondary display), even
if the software driving it knows how to initialise it in the absence
of OpenFirmware?
Of course
Hello,
Marc appears to have fixed various issues for int10/vbe on non-x86
platforms as part of his sparc work. Perhaps some of those same
issues prevented this stuff from working on powerpc in the past and
so these #ifdef's can be removed now. int10/vbe should fail-safe
on hardware that
On Tue, Aug 30, 2005 at 09:30:26PM -0400, Michael wrote:
Hello,
Marc appears to have fixed various issues for int10/vbe on non-x86
platforms as part of his sparc work. Perhaps some of those same
issues prevented this stuff from working on powerpc in the past and
so these #ifdef's can be
Hello,
Marc appears to have fixed various issues for int10/vbe on non-x86
platforms as part of his sparc work. Perhaps some of those same
issues prevented this stuff from working on powerpc in the past and
so these #ifdef's can be removed now. int10/vbe should fail-safe
on hardware
On Tue, 30 Aug 2005, Bang Jun-Young wrote:
On Mon, 29 Aug 2005 17:49:02 +0900, Bang Jun-Young [EMAIL PROTECTED]
wrote:
I got the following error when I ran XFree86 tagged xf-4_5_99_10 with vesa
driver on a VMware virtual machine running NetBSD/i386:
Fatal server error:
xf86MapVidMem: could
On Tue, 30 Aug 2005, Marc Aurele La France wrote:
On Tue, 30 Aug 2005, Bang Jun-Young wrote:
On Mon, 29 Aug 2005 17:49:02 +0900, Bang Jun-Young [EMAIL PROTECTED]
wrote:
I got the following error when I ran XFree86 tagged xf-4_5_99_10 with vesa
driver on a VMware virtual machine running
On Tue, 30 Aug 2005 23:38:28 +0900, Marc Aurele La France
[EMAIL PROTECTED] wrote:
The attached should work with the vmware driver. Please also try this
with
the vesa driver.
vmware driver has worked fine without the patch, only vesa driver was
problematic. Now the patch applied, vesa also
On Wed, 31 Aug 2005, Bang Jun-Young wrote:
On Tue, 30 Aug 2005 23:38:28 +0900, Marc Aurele La France [EMAIL PROTECTED]
wrote:
The attached should work with the vmware driver. Please also try this with
the vesa driver.
vmware driver has worked fine without the patch, only vesa driver was
On Mon, 29 Aug 2005, Carlos Alfaro wrote:
I have a system in which I just installed debian - the video card is
all-in-wonder radeon 7500
the x server will only allow me a resolution of 800*600 and the bit depth is
8
vesa compatible
every config I have tried to put with ATI specific setting
25% si te inscribes antes del Miercoles 31
de Agosto
Aprende a hacer el mas exquisito sushi de manera personalizada o en
grupos.
El curso incluye 4 clases con todos los materiales. (horarios
personalizados, ideal para quienes trabajan)
si eres de los 10 primeros en inscribirte, te damos
Make the American dream actually happen for you
and your family. Imagine owning a beautiful 3,4,5
bedroom hoome in your area, starting from $17,963
and with ^NO^MONEY^DOWN^!
We invite you to search these listings right now and for FREE!
F+ree Listings Here!
Hi,
I am running Mandrake 10.0 on a Medion laptop. After logging on
and issuing the startx command today, I got the following error messages:
Could not init font path element unix/:-1, removing from list!
...
XI0: fatal IO error 104 (Connection reset by peer)
I am getting errors when I run
XFree86 -autoconfig. They are causing the configuration to hang. I cannot find a
solution to this problem anywhere. Can anyone help? I installed using the
binaries and Xinstall.sh. Here are the errors and attached are is my log file .
Thanks.
XFree86 Version
On Tue, 30 Aug 2005, Cam Lawler wrote:
I am getting errors when I run XFree86 -autoconfig. They are causing the
configuration to hang. I cannot find a solution to this problem anywhere.
Can anyone help? I installed using the binaries and Xinstall.sh. Here are
the errors and attached are is my
27 matches
Mail list logo
